relocate working buildroot

Hi All,

Is anyone able to comment on how best to relocate and/or copy a working buildroot?

I have tried it (relocate to new location on same box) and did a "make
clean" followed by "make". Very soon I got failures due to not being
able to delete some files at the original location.

With a bit of grepping I discovered that the original configuration full path is in numerous (i.e. too many to fix manually) locations throughout buildroot related files.

Are there some specific (maybe hidden) buildroot files that could be deleted to force the configuration stage to pick up the new path?

Thanks in advance,

Mike Sander
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot

Quoted 39 lines · Mike Sander

Quoted 24 lines · Ulf Samuelsson

Quoted 9 lines · mike sander

Hi All,

Is anyone able to comment on how best to relocate and/or copy a working buildroot?

I have tried it (relocate to new location on same box) and did a
"make clean" followed by "make". Very soon I got failures due to
not being able to delete some files at the original location.

Quoted 9 lines

With a bit of grepping I discovered that the original configuration full path is in numerous (i.e. too many to fix manually) locations throughout buildroot related files.

Are there some specific (maybe hidden) buildroot files that could be deleted to force the configuration stage to pick up the new path?

I don't think you can.
I think you need to delete it all and rebuild

Quoted 11 lines

build_<arch>
project_build_<arch>
toolchain_build_<arch>

needs to go.

If you want to move to another machine, then you
could try symlinking.

Quoted 10 lines

Thank You Ulf,

"make clean" followed by deleting the 3 directories you indicated worked for relocating the buildroot on the same machine. The only casualty was the kernel which is under project_build_<arch>, but that was easy enough to back up prior deleting.

I'll try moving to another machine and report the results later.

Create a "local" directory outside the buildroot tree Have to set the BR2_LOCAL (or whatever the name was) environement variable in your shell.

Do

$ make saveconfig

Then your linux config file (and other config files) will be saved in the "local" directory.

The rest, assuming identical host installation is a finite statemachine which should generate the same result as the first build.

Quoted 3 lines

Regards,
Mike

Best Regards
Ulf Samuelsson

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org