From: Jeff Sadowski <jeff.sadowski@gm...> - 2007-05-10 14:53:18
I would like to learn how to customize the build of certain apps in buildroot.
For instance I need to build links with ssl support. I have the ssl
lib built It autoselected it for ssh deamon. Can links be built
against its ssl lib? do I just need to add stuff to the config files
and or makefiles? I'll do a little more digging but I was wondering if
there is an easy way.
I want to press the easy button.
On May 10, 2007, at 7:53 AM, Jeff Sadowski wrote:
> I would like to learn how to customize the build of certain apps in
> For instance I need to build links with ssl support. I have the ssl
> lib built It autoselected it for ssh deamon. Can links be built
> against its ssl lib? do I just need to add stuff to the config files
> and or makefiles? I'll do a little more digging but I was wondering if
> there is an easy way.
> I want to press the easy button.
The configuration of each "package" built in the buildroot is
specified in the /package subdirectory of the buildroot. In there,
you'll see a sub-subdirectory for each package, and each of those
contains a *.mk file which is a meta makefile for that package. Its
job is to download a tarball, extract, configure, then run the
tarball's own make, and then finally extract the built pieces into
the gumstix rootfs image. If you want to add a particular feature to
a package, the quick/easy/hacky way is to just edit the "configure"
part of the .mk . The better way would be to add an option in the
Config.in for the package (so that it shows up as an option in
menuconfig etc) and then have the changes in the *.mk depend on the
config variables you create in Config.in
For an example of "sub-options" in a Config.in, you can look at the
mtd-utils package. You could do something similar for optionally
passing the openssl arg to the links configure script by using the
existing BR2_PACKAGE_OPENSSL variable from package/openssl/Config.in