I've searched quite a bit regarding how to utilize buildroot for
making beagleboard images but I did not found anything like a how-to
or step guide.
If anyone can assist I'd be thankful.
Christos
Most people use OpenEmbedded -- give that a try.
Cliff
Cliff,
Yes, I've tested it but I want specifically an environment that
assists development.
OE is just to make packaging and images/distributions not to assist
you
in the development cycles and fast testing iterations.
Anyway the buildroot is what I need now and any help is welcome..
Thanks,
Christos
Cliff,
Yes, I've tested it but I want specifically an environment that
assists development.
OE is just to make packaging and images/distributions not to assist
you
in the development cycles and fast testing iterations.Anyway the buildroot is what I need now and any help is welcome..
You can use the compilers and libraries created by OE by setting your
path into tmp/cross/.. and passing suitable options to configure. This
is not well documented, but is much easier than finding something
else.
Philip
Philip,
I'm trying to add a new ASoC codec driver to McBSP port so
as a real example with Buildroot I can
$ gedit sound/soc/omap/omap3beagle.c (edit in-place of the linux tree
or any package)
$ make ; make uImage
$ cp uImage /media/LABEL1 (copy the new uImage in SD)
check my work by rebooting from SD
Can I do this with such easyness as in buildroot also in OE?
There was a heated discussion in #beagle and recomended me better to
use buildroot if
I'm targeted to such development.
Christos
What about:
$ gedit sound/soc/omap/omap3beagle.c
$ make CROSS_COMPILE=${YOUR_OE_PATH}/build/tmp/cross/armv7a/bin/arm-angstrom-linux-gnueabi- uImage
$ cp uImage /media/LABEL1 (copy the new uImage in SD)
What you want to achieve has nothing to do with using buildroot or OE. Both build system provide you a toolchain and needed libraries. If all you need is a toolchain for compiling your kernel, then you don’t even need OE or buildroot.
The question is which system provides better target files system integration for BB. Is there anything provided by buildroot but not by OE? I don’t think so…Note that inverse is not true.
Regards,
Caglar
Caglar,
I would expect that sequence too, but the git sources are erased by
OE.
So there is no linux tree or any package in OE build environment after
the build in
order to continue your edit work.
Actually that exact sequence does not work for OE.
When I tried it with Angstrom, it builded the distro image ok
but no omap3beagle.c existed anywere.
I agree with you on file system integration, this is what I try to
find
with Buildroot, if there have been steps for this since it is what br
is lacking right now.
Christos
Caglar,
I would expect that sequence too, but the git sources are erased by
OE.
So there is no linux tree or any package in OE build environment after
the build in
order to continue your edit work.
Actually that exact sequence does not work for OE.
When I tried it with Angstrom, it builded the distro image ok
but no omap3beagle.c existed anywere.
Unless you added rm_work to local.conf the kernel sources will be
there, if you built the kernel.
Philip
only if you tell it to do that by inheriting rm_work
Philip,
I did not added anything since I do not have the knowledge on how
to do it, nor I've seen any screen configuration menu in OE and
touched it like
in buildroot.
I've just followed the command line howto http://wiki.openembedded.net/index.php/Getting_started
Anyway, I do not like to go into that debate again as previously in
irc, nor I want
to learn new cryptic things at my age, I just asked if there is
anyone that can give a pointer on buildroot and omap file system
integration.
Any help on this specific issue is welcome.
Christos
Philip,
I did not added anything since I do not have the knowledge on how
to do it, nor I've seen any screen configuration menu in OE and
touched it like
in buildroot.
I've just followed the command line howto Openembedded-Hotels, Villen, Unterkünfte in Leipzig
For other people reading this thread, this howto suggests using
rm_work, if you want the build to leave behind the compiled source
trees, remove or comment it out.
Philip