[Buildroot] Help with forcing a rebuild of the target

[Buildroot] Help with forcing a rebuild of the target

[Jakob Cornell]

Hi all,

I've been working with Buildroot for a few weeks, and I occasionally find that I want to undo a change I've made to the 'output/target' tree. This is usually because I want to remove a file previously added using an overlay or because there are stale files leftover from a package that I've deselected.

So what I want to do, ideally, is run everything needed to fully populate the target filesystem, but also ensure that only what's needed is there. I've tried removing 'output/target' or individual files in it, but that often breaks the build. I've been resorting to doing a full clean and build, which is very wasteful. Is there any way to clean out the target tree and rebuild it without having to recompile anything?

Thanks,
Jakob

[Buildroot] Help with forcing a rebuild of the target

[John Faith]

On Sat, 2019-08-10 at 18:32 -0500, Jakob Cornell wrote:
Hi all,

Hi.


I've been working with Buildroot for a few weeks, and I occasionally find that I want to undo a change I've made to the 'output/target' tree. This is usually because I want to remove a file previously added using an overlay or because there are stale files leftover from a package that I've deselected.

So what I want to do, ideally, is run everything needed to fully populate the target filesystem, but also ensure that only what's needed is there. I've tried removing 'output/target' or individual files in it, but that often breaks the build. I've been resorting to doing a full clean and build, which is very wasteful. Is there any way to clean out the target tree and rebuild it without having to recompile anything?

In the output directory, I've done this:

rm -f build/*/.stamp_target_installed
rm -rf target
make

,
John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190813/c6068f3c/attachment.html>

[Buildroot] Help with forcing a rebuild of the target

[Vadim Kochan]

Hi Jakob,

On Sun, Aug 11, 2019 at 2:41 AM Jakob Cornell <jakob@jcornell.net> wrote:
>
> Hi all,
>
> I've been working with Buildroot for a few weeks, and I occasionally find that I want to undo a change I've made to the 'output/target' tree. This is usually because I want to remove a file previously added using an overlay or because there are stale files leftover from a package that I've deselected.
>
> So what I want to do, ideally, is run everything needed to fully populate the target filesystem, but also ensure that only what's needed is there. I've tried removing 'output/target' or individual files in it, but that often breaks the build. I've been resorting to doing a full clean and build, which is very wasteful. Is there any way to clean out the target tree and rebuild it without having to recompile anything?
>
> Thanks,
> Jakob
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Yes, Buildroot does not provide mechanism to un-install package from
the target/staging/host, I think the answer might be here:

    https://buildroot.org/downloads/manual/manual.html#faq-no-binary-packages

Regards,
Vadim Kochan

[Buildroot] Help with forcing a rebuild of the target

[Arnout Vandecappelle]

On 11/08/2019 01:32, Jakob Cornell wrote:
> Hi all,
> 
> I've been working with Buildroot for a few weeks, and I occasionally find that I
> want to undo a change I've made to the 'output/target' tree. This is usually
> because I want to remove a file previously added using an overlay or because
> there are stale files leftover from a package that I've deselected.

 This is exactly why we don't offer support for such a feature: if there are
stale files left over in target, there are also stale files left over in
staging. In that case, it's possible that some other package links with those
files, which will succeed. But at runtime, it won't work because the files
aren't there on target.

 Even if there were a solution for that, it's not sufficient. You need to
rebuild all the packages that depend on the package you just removed. However,
since you just removed the package, you can't now any more which packaged
depended on it.


 Regards,
 Arnout


> So what I want to do, ideally, is run everything needed to fully populate the
> target filesystem, but also ensure that only what's needed is there. I've tried
> removing 'output/target' or individual files in it, but that often breaks the
> build. I've been resorting to doing a full clean and build, which is very
> wasteful. Is there any way to clean out the target tree and rebuild it without
> having to recompile anything?
> 
> Thanks,
> Jakob
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot