[Buildroot] installing binaries
Igor Serebryany
igor47 at moomers.org
Wed Jul 29 01:33:05 UTC 2009
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: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.buildroot.org/pipermail/buildroot/attachments/20090728/b78dac9c/attachment.asc>
More information about the buildroot
mailing list