From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12191] cmake BUILDDIR
Date: Sun, 08 Sep 2019 15:45:56 +0000 [thread overview]
Message-ID: <bug-12191-163-PkEju4eWhR@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12191-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12191
--- Comment #4 from Arnout Vandecappelle <arnout@mind.be> ---
> --- a/package/pkg-cmake.mk
> +++ b/package/pkg-cmake.mk
> @@ -66,9 +66,9 @@
>
>
> ifeq ($$($(3)_SUPPORTS_IN_SOURCE_BUILD),YES)
> -$(2)_BUILDDIR = $$($(2)_SRCDIR)
> -else
> -$(2)_BUILDDIR = $$($(2)_SRCDIR)/buildroot-build
> +$(2)_BUILDDIR ?= $$($(2)_SRCDIR)
> +else
> +$(2)_BUILDDIR ?= $$($(2)_SRCDIR)/buildroot-build
> endif
I am not at all happy with this approach.
First of all, it becomes unnecessary if/when the separate-source-and-build-dir
series finally gets merged.
Second, the approach taken by pkg-cmake is already kind of awkward IMO;
allowing individual packages to override BUILDDIR makes it worse.
Third, it breaks a couple of things, e.g. <pkg>-dirclean.
Finally, the problem is really with the package itself, there should be no
reason at all to reject output/build/$(PKG_NAME)-$(PKG_VERSION)/buildroot-build
as the build directory. So just patch the package and whatever check it does,
replace it with a check that CMAKE_SOURCE_DIR != CMAKE_BINARY_DIR.
Failing that, I would be more in favour in advancing the
separate-source-and-build-dir approach.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-09-08 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 17:31 [Buildroot] [Bug 12191] New: cmake BUILDDIR bugzilla at busybox.net
2019-09-05 18:48 ` [Buildroot] [Bug 12191] " bugzilla at busybox.net
2019-09-05 20:40 ` bugzilla at busybox.net
2019-09-06 1:21 ` bugzilla at busybox.net
2019-09-08 15:45 ` bugzilla at busybox.net [this message]
2019-09-08 16:39 ` bugzilla at busybox.net
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=bug-12191-163-PkEju4eWhR@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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