[Buildroot] development environment

[Buildroot] development environment

[Marcel]

Hi,

I'm trying to create a workable environment to work with buildroot for the 
following :

I use a stable buildroot (which I may regularly upgrade) and will be adding 
kernel modules, board configurations and packages for my own design.
The documentation is very clear how to add the packages, so that's no issue.

The issue I have is that I want to use CVS for my own developed files and need 
to set up a workable environment to work efficiently to create patches for 
buildroot. On the other hand, just creating patches is not a real option as I 
should be able to compile just one kernel module in order to efficiently test it 
without requiring a full rebuild of the kernel. Rebuilding the kernel module 
would require me to edit the patched files within buildroot, but it's very hard 
to use CVS from that environment because my files are all over the place in 
buildroot. I can copy files, but this isn't very good practice either.

I've been trying some things over the past few days but every idea I come up 
with is very inefficient.

Does anyone have some tips regarding an efficient workflow ?

Best regards,
Marcel


 

[Buildroot] development environment

[Peter Korsgaard]

>>>>> "Marcel" == Marcel  <korgull@home.nl> writes:

 Marcel> Hi,

 Marcel> I'm trying to create a workable environment to work with
 Marcel> buildroot for the following :

 Marcel> I use a stable buildroot (which I may regularly upgrade) and
 Marcel> will be adding kernel modules, board configurations and
 Marcel> packages for my own design.  The documentation is very clear
 Marcel> how to add the packages, so that's no issue.

 Marcel> The issue I have is that I want to use CVS for my own developed
 Marcel> files and need to set up a workable environment to work
 Marcel> efficiently to create patches for buildroot.

We're almost in 2010 - Are you really sure you want to do development
with CVS today?

I've been using a similar setup like your with subversion and git
without any big issues.

 Marcel> On the other hand, just creating patches is not a real option
 Marcel> as I should be able to compile just one kernel module in order
 Marcel> to efficiently test it without requiring a full rebuild of the
 Marcel> kernel. Rebuilding the kernel module would require me to edit
 Marcel> the patched files within buildroot, but it's very hard to use
 Marcel> CVS from that environment because my files are all over the
 Marcel> place in buildroot. I can copy files, but this isn't very good
 Marcel> practice either.

I would suggest that you do your basic kernel development by hand first
and only integrate it into buildroot. BR is very nice for automating
stuff, but for doing actual kernel development I prefer the flexibility
of building by hand.

Also the kernel is very simple to build yourself as there's no external
dependencies.

-- 
Bye, Peter Korsgaard

[Buildroot] development environment

[Daniel Mack]

On Thu, Dec 17, 2009 at 10:47:19PM +0100, Peter Korsgaard wrote:
>  Marcel> I'm trying to create a workable environment to work with
>  Marcel> buildroot for the following :
> 
>  Marcel> I use a stable buildroot (which I may regularly upgrade) and
>  Marcel> will be adding kernel modules, board configurations and
>  Marcel> packages for my own design.  The documentation is very clear
>  Marcel> how to add the packages, so that's no issue.
> 
>  Marcel> The issue I have is that I want to use CVS for my own developed
>  Marcel> files and need to set up a workable environment to work
>  Marcel> efficiently to create patches for buildroot.
> 
> We're almost in 2010 - Are you really sure you want to do development
> with CVS today?
> 
> I've been using a similar setup like your with subversion and git
> without any big issues.

I'd also suggest using git for this purpose. Clone the master branch,
fork off your own development branch and add your packages there. You
can then keep your master in sync with the upstream repository and
rebase your own branch, merge the master or cherry-pick selected
commits.

We do something similar for own projects, and it works wonderfully.

And once you got used to git, you'll never want to get back to CVS,
believe me ;)

Daniel

[Buildroot] development environment

[Marcel]

Hi Daniel,

Thanks for the reply. I already found yesterday that git was used mostly for 
this purpose and already started to use it. It does look like the right tool 
or at least far better than CVS for this purpose and explains why I had issues 
:-)

A small addition to the current document page about some basic workflow using 
git would be very nice I think.

> On Thu, Dec 17, 2009 at 10:47:19PM +0100, Peter Korsgaard wrote:
> >  Marcel> I'm trying to create a workable environment to work with
> >  Marcel> buildroot for the following :
> >
> >  Marcel> I use a stable buildroot (which I may regularly upgrade) and
> >  Marcel> will be adding kernel modules, board configurations and
> >  Marcel> packages for my own design.  The documentation is very clear
> >  Marcel> how to add the packages, so that's no issue.
> >
> >  Marcel> The issue I have is that I want to use CVS for my own developed
> >  Marcel> files and need to set up a workable environment to work
> >  Marcel> efficiently to create patches for buildroot.
> >
> > We're almost in 2010 - Are you really sure you want to do development
> > with CVS today?
> >
> > I've been using a similar setup like your with subversion and git
> > without any big issues.
> 
> I'd also suggest using git for this purpose. Clone the master branch,
> fork off your own development branch and add your packages there. You
> can then keep your master in sync with the upstream repository and
> rebase your own branch, merge the master or cherry-pick selected
> commits.
> 
> We do something similar for own projects, and it works wonderfully.
> 
> And once you got used to git, you'll never want to get back to CVS,
> believe me ;)
> 
> Daniel
> 

[Buildroot] development environment

[Aaron Hanson]

Hi All -

        I'm having great success creating a complete target image and booting it. Buildroot is wonderful. But I want development tools in the target system, and I'm getting a very basic error when I try to use gcc:

# gcc foo.c
/usr/bin/ld: cannot find -lgcc
collect2: ld returned 1 exit status

        I work around this with a symlink:

/usr/lib/libgcc.so -> libgcc_s.so.1

        But then I'm stuck:

# gcc foo.c
/usr/bin/ld: cannot find /usr/lib/uclibc_nonshared.a
collect2: ld returned 1 exit status

        It seems I've not built the toolchain correctly. I'm using buildroot and uclibc menu-config and throwing in all the development options I can find. Does this particular problem have an obvious meaning to anybody? Is there a static-lib setting that I'm missing?

        Thanks...

-Aaron