[Buildroot] I want to know how the buildroot works inside when build and install a new package

IaMaPlAyEr iamaplayer at gmail.com
Sat Feb 28 02:49:09 UTC 2009


Hi,
    Thanks for your warmhearted reply.
    I know your meaning, but it is not my question.
    Sorry for my ability that not express my question clearly.

I want to know how the foo.mk(the example in doc of buildroot) pass
parameter to the autotools or ./configure, or make.
Not only just use
FOO_INSTALL_TARGET = YES
FOO_AUTORECONF=YES
but how the parameter will be used in Makefile.autotools.in or something
else?

Of course I need to read the Makefile.autotools.in by myself, but I just
want to know the panorama how the parameter pass to ./configure or make.

And if i want to comprehend and improve the Makefile.autotools or the
mechanism of parameter transfer, the first step is to know how it works now.

btw, do you know the OpenWRT? It also based on buildroot, and it has his own
packages mechanism just like i2c-tools:
https://svn.openwrt.org/openwrt/packages/utils/i2c-tools/
https://svn.openwrt.org/openwrt/packages/utils/i2c-tools/Makefile

...
include $(TOPDIR)/rules.mk

PKG_NAME:=i2c-tools
PKG_VERSION:=3.0.1
PKG_RELEASE:=1
...





If i comprehend two things(makefile in OpenWrt and foo.mk in buildroot),
maybe we can added more and more packages in buildroot by the hands of
OpenWrt.






On Sat, Feb 28, 2009 at 5:30 AM, Thomas Petazzoni <
thomas.petazzoni at free-electrons.com> wrote:

> ....
>
>  ./configure
>  make
>  make install
>
>
> FOO_AUTORECONF=YES
>
> ....
>
> Sincerly,
>
> Thomas
> --
> Thomas Petazzoni, Free Electrons
> Kernel, drivers and embedded Linux development,
> consulting, training and support.
> http://free-electrons.com
> _____________________________________________<http://lists.busybox.net/mailman/listinfo/buildroot>




-- 
Sincerly,

HaveF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090228/bbb99d1e/attachment-0001.html>


More information about the buildroot mailing list