From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Juergen Ruehle <j.ruehle@bmiag.de>
Cc: xconq7@sources.redhat.com, Hans Ronne <hronne@telia.com>
Subject: Re: Build system overhaul
Date: Thu, 18 Sep 2003 02:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0309171129320.13358-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <16232.14328.274000.891577@lapjr.intranet.kiel.bmiag.de>
Guten tag Juergen,
On Wed, 17 Sep 2003, Juergen Ruehle wrote:
> Would we have separate targets for these in kernel/Makefile or do we
> completely parameterize the build and pass in the flags and the target
> names from the calling Makefile? Are there more options?
I have not thoroughly investigated the matter, but I am thinking
about making separate targets so that we can take advantage of
make's ability to see if a target is "up to date". Otherwise, we
must include a "[ -f libconq_mw32.a ]" test in the target commands
or be forced to rebuild the lib every time the target gets
invoked. But, I also think it would be wise to supply the make
flags from the invoking makefile (i.e., the one in the sdl dir)
even in the case of separate targets. This would reduce the
number of alternate flag configurations that would have to be
maintained in various makefiles.
> solution seems much simpler to implement. But obviously it's up to
> whoever implements this (which probably wont be me:-)
In that case, it will probably be me. ;-)
Regards,
Eric
next prev parent reply other threads:[~2003-09-17 15:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 4:29 New Xconq Windows Executable Eric McDonald
2003-08-27 16:17 ` Eric McDonald
2003-08-27 16:37 ` Jim Kingdon
2003-08-27 17:20 ` Eric McDonald
2003-08-27 18:40 ` Hans Ronne
2003-08-27 19:53 ` Eric McDonald
2003-08-28 3:26 ` Hans Ronne
2003-08-28 13:38 ` Juergen Ruehle
2003-08-29 0:44 ` Eric McDonald
2003-08-29 8:35 ` Eric McDonald
2003-08-29 15:22 ` Juergen Ruehle
2003-08-30 5:47 ` Eric McDonald
2003-08-29 9:06 ` Hans Ronne
2003-08-29 15:57 ` Eric McDonald
2003-09-05 4:54 ` Tcl/Tk Interface Unification (was Re: New Xconq Windows Executable) Eric McDonald
2003-09-05 15:06 ` Hans Ronne
2003-09-05 15:51 ` Eric McDonald
2003-09-06 6:05 ` Hans Ronne
2003-09-15 3:43 ` Tcl/Tk Interface Unification Eric McDonald
2003-09-15 3:50 ` Hans Ronne
2003-09-15 14:32 ` Eric McDonald
2003-09-15 18:39 ` Hans Ronne
2003-09-15 19:38 ` Eric McDonald
2003-09-15 23:31 ` Hans Ronne
2003-09-16 13:53 ` Build system overhaul (Was: Tcl/Tk Interface Unification) Juergen Ruehle
2003-09-16 18:15 ` Eric McDonald
2003-09-16 20:23 ` Eric McDonald
2003-09-17 10:32 ` Hans Ronne
2003-09-17 15:54 ` Juergen Ruehle
2003-09-18 2:37 ` Eric McDonald [this message]
2003-09-08 17:46 ` Tcl/Tk Interface Unification (was Re: New Xconq Windows Executable) Eric McDonald
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=Pine.LNX.4.44.0309171129320.13358-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@telia.com \
--cc=j.ruehle@bmiag.de \
--cc=xconq7@sources.redhat.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).