On 8/25/06, André Detsch <[EMAIL PROTECTED]> wrote:
On 8/25/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote:
> Log message:
> Removal of $cross_dependencies: it should be handled by
BuildDependencies
> instead. A series of patches is coming, based on Hisham's suggestion.
The plan is to populate overall recipes with build dependencies that
are only needed when cross-compiling? (E.g., adding Glib to
BuildDependencies of XYZ recipe even if it is not required to compile
XYZ natively).
Does not sounds a good approach to me if the answer is yes...
In practice, what happens when cross-compiling is that sometimes its
build process tries to invoke some program from the host, such as when
needing to generate headers on the fly. Common situations:
/bin/tricky_program_to_generate_headers foo.c foo.h
arm-linux-gcc foo.c -c
...
In this case, it is expected to have
tricky_program_to_generate_headers in the host anyway, so its package
should definetely be listed in BuildDependencies. This is the case for
any package that needs autotools, for example.
The cross-compiling process is not including extra packages in
BuildDependencies. It's just making these dependencies to be found
more quickly :-)
--
Lucas
powered by /dev/dsp
_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
