From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] I want to know how the buildroot works inside when build and install a new package
Date: Fri, 27 Feb 2009 22:30:49 +0100 [thread overview]
Message-ID: <20090227223049.4cb8362a@surf> (raw)
In-Reply-To: <2ae8403e0902261945w682609fbwa4758e1bcf01f742@mail.gmail.com>
Hi,
Le Fri, 27 Feb 2009 11:45:55 +0800,
IaMaPlAyEr <iamaplayer@gmail.com> a ?crit :
> And how the buildroot works inside?
Most of the autotools-based packages are released with the configure
script and Makefile.in files already generated (i.e, aclocal, autoconf,
autoheader and automake have been run by the developer and integrated
inside the released tarball). So, the automagic thing available in
Buildroot to compile autotools-based packages will basically do :
./configure
make
make install
(passing of course the correct options and setting the appropriate
environment variables to get cross-compilation to work properly).
However, if for some reason you want the whole aclocal, autoconf,
autoheader and automake process to be run before compiling the package,
you can add :
FOO_AUTORECONF=YES
in your Buildroot Makefile. This is particularly useful if you patch
the configure.in file or the Makefile.am files.
Does that answer your question ? If not, don't hesitate to ask for
details.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-02-27 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 3:45 [Buildroot] I want to know how the buildroot works inside when build and install a new package IaMaPlAyEr
2009-02-27 21:30 ` Thomas Petazzoni [this message]
2009-02-28 2:49 ` IaMaPlAyEr
2009-02-28 8:51 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090227223049.4cb8362a@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox