Hi,
Yes but it was fixed that way in the Pyro branch.
do_compile() {
${CC} ${LDFLAGS} helloworld.c -o helloworld
}
regards
--
Pierre FICHEUX -/- CTO Smile-ECS, France -\- pierre.fich...@smile.fr
http://www.smile.fr
Did you try compiling in text mode?
$ $CC -o test test.c
--
Pierre FICHEUX -/- CTO Smile-ECS, France -\- pierre.fich...@smile.fr
http://www.smile.fr
http://ingenierie.openwide.fr
I would love to change the world, but they w
On Sun, Jul 2, 2017 at 1:01 AM, Pierre FICHEUX wrote:
> Hi,
>
> Yes but it was fixed that way in the Pyro branch.
>
I thought this patch was being proposed for master. If yes then different
solution in pyro should not be a big problem. you can always backport
the new patch to pyro
> do_compile()
On Sat, Jul 1, 2017 at 6:07 PM, Paul D. DeRocco wrote:
>> From: Andrea Galbusera [mailto:giz...@gmail.com]
>>
>> Could you please post the exact source code of your test
>> program and the steps you take to (a) build the SDK and (b)
>> build your test executable? Is your running image a pretty
>>
Since we are parsing and building all the images in refkit-ci.inc,
there are some layers that are now required. This includes flatpak,
industrial, and ROS layers. Since we are building a dynamic set of
images based on this inc file, we should be adding these layers
dynamically as well at some point
Hi,
I am trying to make some changes in u-boot code and using bitbake u-boot to
build. But it doesn't build.
I also tried bitbake u-boot -c compile and bitbake u-boot deploy. This also
didn't work.
Can I Get some help on how to change and build u-boot.
Thanks,
Prasoon
--
___
Hej ho
my Workflow for adjusting uboot (u-boot-at91):
1.) build the original uboot
2.) apply changes
3.) create patch
3.1.) if you reconfigure it -> save/copy the config
3.2.) if you adding code -> use meld or something similar to create a
patch
4.) create u-boot-at91_%.bbappend
4.1) copy patch/
