Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Per package src+build directory
@ 2021-01-13  5:41 scdrj
  2021-01-13 21:33 ` Arnout Vandecappelle
  0 siblings, 1 reply; 2+ messages in thread
From: scdrj @ 2021-01-13  5:41 UTC (permalink / raw)
  To: buildroot

How do I set a custom src/build directory for a particular package?

I have tried OVERRIDE_SRCDIR, but it always performs rsync to the build
folder (makes an extra copy).

I want to perform the in-place build. 

Currently, I am doing it by creating a symbolic link in the build folder
from the original src directory and by manually creating various
downloaded/patched/extracted ".stamp_XXXXXX" files.



--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Buildroot] Per package src+build directory
  2021-01-13  5:41 [Buildroot] Per package src+build directory scdrj
@ 2021-01-13 21:33 ` Arnout Vandecappelle
  0 siblings, 0 replies; 2+ messages in thread
From: Arnout Vandecappelle @ 2021-01-13 21:33 UTC (permalink / raw)
  To: buildroot



On 13/01/2021 06:41, scdrj wrote:
> How do I set a custom src/build directory for a particular package?

 That is not possible, period. Only the source can be overriden, but as you say,
it's always rsync'ed to the build directory.


> I have tried OVERRIDE_SRCDIR, but it always performs rsync to the build
> folder (makes an extra copy).
> 
> I want to perform the in-place build. 

 Is there a specific reason to want this? Doing the build inside the source
directory is not a good idea for many reasons.

 If it's for the size or the build time - normally, the compilation itself
should take a lot more time and produce a much bigger output, so the overhead
should be negligible.

 If it's because there's a large subtree that isn't actually used, *that* can be
avoided by using package-specific excludes, with
_OVERRIDE_SRCDIR_RSYNC_EXCLUSIONS (which is just a list of rsync argument, so
you can actually put anything there).


 Regards,
 Arnout

> Currently, I am doing it by creating a symbolic link in the build folder
> from the original src directory and by manually creating various
> downloaded/patched/extracted ".stamp_XXXXXX" files.
> 
> 
> 
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-01-13 21:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-01-13  5:41 [Buildroot] Per package src+build directory scdrj
2021-01-13 21:33 ` Arnout Vandecappelle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox