From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Support for out-of-tree build
Date: Fri, 20 Nov 2015 00:02:07 -0500 [thread overview]
Message-ID: <20151120050207.GW3818@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151120040955.GV3818@brightrain.aerifal.cx>
On Thu, Nov 19, 2015 at 11:09:55PM -0500, Rich Felker wrote:
> On Thu, Nov 19, 2015 at 12:22:09AM +0000, Petr Hosek wrote:
> > > > clean:
> > > > - rm -f crt/*.o
> > > > + rm -f $(objdir)/crt/*.o
> > > > rm -f $(OBJS)
> > > > rm -f $(LOBJS)
> > > > rm -f $(ALL_LIBS) lib/*.[ao] lib/*.so
> > >
> > > This can probably just be rm -rf obj, but perhaps we should wait to
> > > make that change. And seeing this, I'm mildly in favor of hard-coding
> > > obj/ (everywhere) rather than using $(objdir)/ simply because the
> > > latter is really dangerous if you override it on the command line with
> > > an unwanted setting (like make clean objdir=/).
> >
> > That's why I avoided using rm -rf $(objdir). I can imagine the use case for
> > setting $(objdir) to a different location, changing this to make it
> > hard-coded wouldn't be a problem if you prefer.
>
> Did you mean "can't imagine a use"? To me this looks roughly like a
> "second level of out-of-tree support" that's probably not useful, and
> could be error-prone e.g. if somebody tries to get clever and use
> objdir=., or could be dangerous (objdir=). I think it's best just to
> hard-code it.
>
> [...]
>
> > +test -f Makefile || ln -sf $srcdir/Makefile .
>
> Is there a reason you do it this way rather than checking for
> srcdir=.? The reason I ask is that existence of a stray makefile
> that's not a symlink to the musl makefile should probably be an error
> here rather than silently ignored. But maybe there are more things to
> consider..
Additional thought: can't we just ln -s $srcdir/src $srcdir/crt . in
configure and never have to bother with $(srcdir) in the makefiles?
That seems like another big benefit we can get out of putting all the
generated files in obj/ (and lib/).
Rich
next prev parent reply other threads:[~2015-11-20 5:02 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 23:40 Petr Hosek
2015-11-07 13:05 ` Szabolcs Nagy
2015-11-08 0:43 ` Rich Felker
2015-11-08 2:16 ` Szabolcs Nagy
2015-11-08 2:29 ` Rich Felker
2015-11-11 22:02 ` Petr Hosek
2015-11-11 23:08 ` Rich Felker
2015-11-12 0:01 ` Rich Felker
2015-11-12 0:28 ` Petr Hosek
2015-11-12 14:50 ` Szabolcs Nagy
2015-11-12 20:17 ` Petr Hosek
2015-11-12 20:30 ` Rich Felker
2015-11-12 21:10 ` Szabolcs Nagy
2015-11-12 21:52 ` Rich Felker
2015-11-12 22:35 ` Petr Hosek
2015-11-12 23:41 ` Rich Felker
2015-11-17 2:45 ` Petr Hosek
2015-11-17 6:05 ` Petr Hosek
2015-11-17 19:51 ` Szabolcs Nagy
2015-11-17 21:00 ` Rich Felker
2015-11-17 21:37 ` Petr Hosek
2015-11-17 22:01 ` Rich Felker
2015-11-17 22:15 ` Petr Hosek
2015-11-17 22:58 ` Rich Felker
2015-11-17 23:06 ` Szabolcs Nagy
2015-11-17 23:27 ` Rich Felker
2015-11-17 23:43 ` Rich Felker
2015-11-17 23:54 ` Petr Hosek
2015-11-18 0:19 ` Szabolcs Nagy
2015-11-18 0:19 ` Rich Felker
2015-11-18 20:19 ` Petr Hosek
2015-11-18 21:44 ` Rich Felker
2015-11-19 0:22 ` Petr Hosek
2015-11-20 4:09 ` Rich Felker
2015-11-20 5:02 ` Rich Felker [this message]
2015-11-20 10:51 ` Szabolcs Nagy
2015-11-30 1:25 ` Petr Hosek
2015-11-20 22:20 ` Rich Felker
2015-11-30 1:29 ` Petr Hosek
2015-11-30 1:35 ` Rich Felker
2015-11-30 2:49 ` Petr Hosek
2015-11-30 21:14 ` Rich Felker
2015-11-30 22:14 ` Rich Felker
2015-12-01 2:14 ` Petr Hosek
2015-12-09 0:39 ` Rich Felker
2015-12-10 1:39 ` Petr Hosek
2015-12-10 12:47 ` Szabolcs Nagy
2016-01-17 22:32 ` Rich Felker
2016-01-17 23:41 ` Szabolcs Nagy
2016-01-20 3:49 ` Rich Felker
2015-11-21 1:05 ` Szabolcs Nagy
2015-11-21 1:16 ` Szabolcs Nagy
2015-11-22 14:56 ` Szabolcs Nagy
2015-11-30 1:30 ` Petr Hosek
2015-11-30 12:01 ` Szabolcs Nagy
2015-11-30 22:22 ` Rich Felker
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=20151120050207.GW3818@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).