Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel <korgull@home.nl>
To: buildroot@busybox.net
Subject: [Buildroot] development environment
Date: Thu, 17 Dec 2009 21:31:19 +0100	[thread overview]
Message-ID: <200912172131.19962.korgull@home.nl> (raw)

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


 

             reply	other threads:[~2009-12-17 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 20:31 Marcel [this message]
2009-12-17 21:47 ` [Buildroot] development environment Peter Korsgaard
2009-12-18  1:10   ` Daniel Mack
2009-12-18 17:36     ` Marcel
  -- strict thread matches above, loose matches on Subject: below --
2009-01-06 20:08 Aaron Hanson

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=200912172131.19962.korgull@home.nl \
    --to=korgull@home.nl \
    --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