[oe] relative paths in Openembedded/bitbake

[Christopher Lang]

Hi Holger,

I looked up he bug (#1167). Too bad, relative paths would be nice to have. 
I'll try the symlink approach some time...

Chris



Am Dienstag, 12. September 2006 17:03 schrieb Holger Freyther:
> Am 12.09.2006 um 16:30 schrieb Christopher Lang:
> >> From what I can see all paths in OE/bitbake are absolute paths.
> >> This makes it
> >
> > difficult to move an OE build directory to another location.
> >
> > Questions:
> >
> > - which paths in which files do I need to change to move an entire
> > build
> > directory? (conf files of course, any other files?)
> >
> > - Is it possible to set up an OE build directory based on relative
> > paths?
> >
> > - If the 2nd question was answered with no, are there any plans to
> > enable
> > OE/bitbake to be able to handle an entire build directory with
> > relative
> > paths?
>
> Hi,
>
> take a look at bugs.openembedded.org as we have a bug for that
> already. Let us take a look at the first package we build:
> 	quilt-native
> 		Quilt runs autoconf and hardcodes absolute paths into its scripts.
>
> So after building the first package you may not move your tree
> anymore.  You could symlinks and see how far you get but I think I
> remember difficulties with that.
>
> I think we have three uses cases here:
> 	- Share one Build tree between multiple Operating Systems and Users
> 	- Move and avoid rebuilding
>
> Both have the same issues: One is the packages we have built require
> the absolute path e.g. hardcoded filenames (like quilt), hardcoded
> rpath to the native staging libdir. And one could be BitBake
> (unlikely though).
>
> h.
>
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel