[Buildroot] depend or select in Config.in & Autotarget question

[Buildroot] depend or select in Config.in & Autotarget question

[Olaf Rempel]

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?
And when using "depend" should there be an info when A is not active
(like ipsec-tools => openssl)?

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?

Regards
Olaf

[Buildroot] depend or select in Config.in & Autotarget question

[Hans-Christian Egtvedt]

On Mon, 2 Mar 2009 12:40:19 +0100
Olaf Rempel <razzor@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.

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
depends.

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
distributions/new architectures.

If it's not needed for the package to compile, do not set it. It will
only slow down the build time.

-- 
Best regards,
Hans-Christian Egtvedt

[Buildroot] depend or select in Config.in & Autotarget question

[Peter Korsgaard]

>>>>> "Olaf" == Olaf Rempel <razzor@kopf-tisch.de> writes:

Hi,

 Olaf> what is the preferred method to resolve package dependencies in
 Olaf> Config.in?  eg. when package-B needs package-A to build, should
 Olaf> B "select" A or should B "depend" on A?

We normally use select for dependencies to libraries, and depends on
toolchain configuration settings (E.G. C++ support).

The reason for this is that it isn't always obvious what you need to
enable to be able to select a certain program, and people normally
think in terms of applications and not libraries.

Changes to the toolchain on the other hand has a lot bigger impact, so
that shouldn't be done behind the back of the user (E.G. with a
select).

 Olaf> And when using "depend" should there be an info when A is not
 Olaf> active (like ipsec-tools => openssl)?

ipsec-tools should select openssl instead - Will fix.

 Olaf> I've started with the Makefile.autotools.in conversion of some
 Olaf> packages that I use.  When should a AUTORECONF:=yes be used? So
 Olaf> far it had no affect in my tests?

Autoreconf is normally only used if you change the auto* source files
(configure.ac, Makefile.am, ..) and want to regenerate the derived files.

-- 
Bye, Peter Korsgaard