From: Carl Worth <cworth@cworth.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: notmuch@notmuchmail.org, Thomas Schwinge <thomas@schwinge.name>
Subject: Re: Build system
Date: Thu, 10 Mar 2011 20:02:33 -0800 [thread overview]
Message-ID: <87ei6e8fty.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87wrk6iluv.fsf@raven.defaultvalue.org>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Thu, 10 Mar 2011 17:42:16 -0600, Rob Browning <rlb@defaultvalue.org> wrote:
> > This isn't ideal since it means that a non-srcdir build won't get access
> > to updated emacs nor test-suite bits without re-running configure. If
> > someone would like to do work to fix either or both of these cases, that
> > would be helpful.
>
> If you're willing to depend on GNU coreutils, would "cp -rl ..." work?
I'd be willing to, but it wouldn't then also get access to new files
that appear in the test suite, (where the Makefiles could actually find
new, uncopied source files).
But wait, what am I thinking... the whole approach of the non-srcdir
builds as currently implemented also copies the Makefiles. So nothing at
all is going to work without re-running configure for non-srcdir builds.
I suppose that what we want is for configure to automatically add
dependencies for every file that it copies. Then if any of these copied
files get changed in the srcdir, configure would be run again.
That should be pretty slick, I think.
-Carl
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2011-03-11 4:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:01 [PATCH] Have to configure and build inside the source directory Thomas Schwinge
2011-01-12 17:58 ` Michal Sojka
2011-01-28 20:58 ` Carl Worth
2011-01-28 23:18 ` Rob Browning
2011-03-09 23:19 ` Carl Worth
2011-01-30 10:12 ` Build system (was: [PATCH] Have to configure and build inside the source directory.) Thomas Schwinge
2011-01-30 10:28 ` Build system Thomas Schwinge
2011-01-30 11:14 ` Carl Worth
2011-02-08 8:55 ` Thomas Schwinge
2011-02-08 21:13 ` Michal Sojka
2011-03-10 19:38 ` Carl Worth
2011-03-10 19:36 ` Carl Worth
2011-03-10 23:42 ` Rob Browning
2011-03-11 4:02 ` Carl Worth [this message]
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ei6e8fty.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=rlb@defaultvalue.org \
--cc=thomas@schwinge.name \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).