From: Nathaniel Talbott <ntalbott@...>
Date: 2001-03-16T22:53:39+09:00
Subject: [ruby-talk:12743] Re: Library packaging

From: dave@thomases.com [mailto:dave@thomases.com]On Behalf Of Dave

> "Nathaniel Talbott" <ntalbott@rolemodelsoft.com> writes:
>
> > The problem comes in when you want don't want to install Lapidary as
> > a library, say to just look at it and run its internal unit
> > tests. Suddenly, Lapidary doesn't work anymore, because it can't
> > find itself! Aach! What to do? If it uses relative references, then
> > it can't find its parts when run as a library; if it uses library
> > references, then it can't find its parts when it's run standalone.
>
> What happens if you organize your source files into directories that
> mirror the final structure:
>
> Then, to run in development you could just have
> -I<path_to_devel/Lapidary>

Hmmm... that'll work. I already have my directories structured like that, I
just hadn't thought of using -I. It still seems weird to me , though, that
there's no way for a set of code to reference itself in such a way that it
can run self-contained AND others requiring it as a library can do so
without errors. Ah well, I don't know a good way to avoid it, either, so for
now I'll just use -I and be happy about it :-)

Thanks,


Nathaniel

<:((><
+ - -						+ - -
| RoleModel Software, Inc. &		| EQUIP VI
| The XP Software Studio(TM)		|