Re: death to -{I,L}/our/{include,lib}!

On Wed, Jul 18, 2001 at 08:38:40PM +0100, Will Partain ([email protected]) wrote:
> It's wrong because we blithely pick up dependencies between
> packages (one uses another's includes/libs) and we end up
> with no knowledge or record.  Can you delete that libpng
> that you built three years ago? -- you don't have a clue.

Yup.. feeping creaturism in the form of unexpected dependencies.
It's been a tough problem to deal with in the source world forever.

> So: we need *not* to reveal include files and libraries into
> /our; and then we need to compile/link against the
> *deployed* stuff; thus, something like...
> 
>    gcc -I/.-ark-deploy/zlib--1.1.3/include \
>        -I/.-ark-deploy/libpng--1.0.9/include \
>        -L/.-ark-deploy/zlib--1.1.3/lib \
>        -L/.-ark-deploy/libpng--1.0.9/lib ...
> 
> Now the dependencies are there in black-and-white in your
> ARK bits...  (We can do this now and ugly-ly w/ current ARK
> engine; next message will muse upon a tidier way to do it...)
> 
> Any thoughts or warnings?

Beware of software packages that utilize broken logic.  The only
way to solve that problem in a general approach is to use a
clean-room a la Intel microprocessor labs.  :-)

-- 
wca