* [Buildroot] SVN guidance request
@ 2008-07-17 15:17 Robert B. Williams
0 siblings, 0 replies; only message in thread
From: Robert B. Williams @ 2008-07-17 15:17 UTC (permalink / raw)
To: buildroot
I am very new to buildroot. Nice work!
Anyway, I would like some advice on how to best version control
buildroot with my work.
I was hoping to put buildroot and the multiple projects I create with it
in an SVN repository. I'll need to be able to merge releases from
buildroot from time to time while maintaining my project related
changes. I am also considering saving the downloads, in case older
versions become unavailable.
The documentation indicates that any changes made to
project_build_ARCH/root/ will be lost during a toolchain build. Does
this mean I will need to build everything once (or kill the process
after the toolchain is built) and then update my
project_build_ARCH/root/ from my repository and then build the project
again? Or is there a better approach to storing project specific root
files? I know alot of the common files could simply be stored in the
target/generic/target_skeleton but what about the ones that differ
between projects?
If there is documentation, hints, faqs, wiki, or any experience in this
areas please let me know.
In the meantime I'll start experimenting.
Cheers!
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-17 15:17 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-17 15:17 [Buildroot] SVN guidance request Robert B. Williams
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.