From: Matthias Klose <doko@debian.org>
To: Sam James <sam@gentoo.org>,
Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: YunQiang Su <wzssyqa@gmail.com>, binutils@sourceware.org
Subject: Re: [PATCH] gprofng: 30700 tmpdir/gp-collect-app_F test fails
Date: Fri, 18 Aug 2023 08:38:29 +0200 [thread overview]
Message-ID: <a21ff18b-0b1a-4aca-104e-68e0b49bfe5e@debian.org> (raw)
In-Reply-To: <87lee9yly0.fsf@gentoo.org>
On 18.08.23 07:10, Sam James via Binutils wrote:
>> Is it legal to create a build directory inside a source tree?
>>
>
> No, the source tree should be treated as immutable please. It's ok
> to create directories within the build dir, but not the source tree.
you are confusing things. In general you have the option to build within the
source tree or with a separate build tree. Some projects like GCC discourage to
build within the source tree and recommend building in a separate build tree.
There is no restriction where the build tree can be located. In the past I have
seen some issue when specifying the build tree relatively to the source tree,
but in general it's the same to configure the build tree with a relative path or
an absolute path. Now if you have a separate build tree, then the source tree
should not be modified, there is no restriction to create a sub-directory for
the build. This works for ages, i.e. dpkg based packaging has no other choice
than using the root of the source tree for builds, and that works for at least
27 years.
Matthias
next prev parent reply other threads:[~2023-08-18 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 20:33 vladimir.mezentsev
2023-08-17 4:22 ` YunQiang Su
2023-08-17 18:44 ` Vladimir Mezentsev
2023-08-18 2:11 ` YunQiang Su
2023-08-18 5:01 ` Vladimir Mezentsev
2023-08-18 5:09 ` YunQiang Su
2023-08-18 5:10 ` Sam James
2023-08-18 6:38 ` Matthias Klose [this message]
2023-08-18 6:45 ` Sam James
[not found] ` <f4c4c9956ccb5bc55fe95f51ee858e3558aa6acbe8d0d0ca0e8716bafbc1fbab@mu.id>
2023-08-18 6:49 ` Sam James
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=a21ff18b-0b1a-4aca-104e-68e0b49bfe5e@debian.org \
--to=doko@debian.org \
--cc=binutils@sourceware.org \
--cc=sam@gentoo.org \
--cc=vladimir.mezentsev@oracle.com \
--cc=wzssyqa@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).