[Buildroot] depend or select in Config.in & Autotarget question
hans-christian.egtvedt at atmel.com
Mon Mar 2 12:06:44 UTC 2009
On Mon, 2 Mar 2009 12:40:19 +0100
Olaf Rempel <razzor at kopf-tisch.de> wrote:
> Hi List,
> what is the preferred method to resolve package dependencies in
> Config.in? eg. when package-B needs package-A to build, should B
> "select" A or should B "depend" on A?
Packages can select other packages. For example if you application
depends on one or more libraries/software, then you should select these
Packages depends on toolchain options, so that you need to configure
your toolchain correct before you go out selecting packages.
Changing the toolchain after a first build will set you back all the
way to start.
> And when using "depend" should there be an info when A is not active
> (like ipsec-tools => openssl)?
Yes, but typically we make a comment which depends on the missing
I.e. "Qt - disabled (requires C++ support)", or I think something
similar is present in the kconfig menu.
> I've started with the Makefile.autotools.in conversion of some
> packages that I use. When should a AUTORECONF:=yes be used? So far it
> had no affect in my tests?
autoreconf may be needed for packages where mainline is shipping
outdated scripts which does not work anymore for up to date
If it's not needed for the package to compile, do not set it. It will
only slow down the build time.
More information about the buildroot