From: Igor Serebryany <igor47@moomers.org>
To: buildroot@busybox.net
Subject: [Buildroot] installing binaries
Date: Tue, 28 Jul 2009 20:33:05 -0500 [thread overview]
Message-ID: <20090729013305.GG7257@moomers.org> (raw)
Hi,
I've been having a hard time figuring out how buildroot decides to
install binaries. Using 2009.02 or 2009.05, I often find that the
binaries for the packages I've selected do not make it into
project_build_ARCH/myproject/root
Is there a way to tell buildroot to go through every selected
package and copy the binaries to the image? Even if I have to delete
some target file in each folder, it would be better then the other
two alternatives I've come up with:
1) copying all the binaries to the root by hand
2) modifying the prefix in the Makefiles for all packages and doing
'make install' for each one individually
I think I get all the packages if I make distclean and then make,
but many packages fail to compile the first time (like util-linux
which always requires a lot of hacking) and I hate to loose my
modifications via make distclean
Trying 'make clean' is futile, as most packages fail to clean and
make clean always errors out half-way through.
I've been working on this for a few days now, so I appreciate any
tips...
--Igor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090728/b78dac9c/attachment.pgp>
next reply other threads:[~2009-07-29 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 1:33 Igor Serebryany [this message]
2009-08-04 14:36 ` [Buildroot] installing binaries Thomas Petazzoni
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=20090729013305.GG7257@moomers.org \
--to=igor47@moomers.org \
--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