[uClinux-dev] [RFC] overhaul library handling with a staging directory

Mike Frysinger vapier at gentoo.org
Tue Jun 5 18:45:56 EDT 2007


On Tuesday 05 June 2007, David McCullough wrote:
> Jivin Mike Frysinger lays it down ...
> > i'm referring to the order given to
> > the compiler ... in other words, whether the -I/-L <staging header path>
> > appears that the beginning, middle, or end of the actual compiler command
> > ... it can make a difference with some applications and it seems that it
> > hasnt really come up the current uClinux-dist since nothing has broken
>
> Fair enough.  I must say that on my host system it's pretty rare that
> you need to mess with this as well.  If you do it's usually because of
> multiple versions or unknown install dirs for a package,

right, it's much more often the exception than the rule that the correct order 
of -I/-L with system paths cause a failure ... ive seen it from time to time 
which is why when i architectured the Blackfin stuff, i made sure to do it 
properly from the get go: staging dir is completely treated as a system path 
with the toolchain, not an additional user path

i dont think comparing the cross-compile scenario here to the uClinux-dist is 
appropriate ... when you compile/install a package on your host, you install 
it into the system paths that are hardcoded into your host toolchain ... that 
is not done with uClinux-dist as there is no way you can assume the person 
compiling uClinux-dist has (or wants) write permission to the cross-toolchain 
directories ... so you have to use additional compiler flags so the 
cross-toolchain knows to treat the staging directory as a search path

so back to the original idea ... can we meet in the middle and have libraries 
install into a top level directory ($(ROOTDIR)/staging) and cut out the 
include/library symlinking ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://mailman.uclinux.org/pipermail/uclinux-dev/attachments/20070605/865b1a27/attachment.pgp


More information about the uClinux-dev mailing list