From: Jakub Narebski <jnareb@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: "J.C. Pizarro" <jcpiza@gmail.com>,
gcc@gcc.gnu.org, git@vger.kernel.org,
David Miller <davem@davemloft.net>,
Daniel Berlin <dberlin@dberlin.org>,
Ismail Donmez <ismail@pardus.org.tr>
Subject: Re: In future, to replace autotools by cmake like KDE4 did?
Date: Fri, 7 Dec 2007 14:56:09 +0100 [thread overview]
Message-ID: <200712071456.11019.jnareb@gmail.com> (raw)
In-Reply-To: <47594021.40200@op5.se>
Andreas Ericsson wrote:
> Jakub Narebski wrote:
> >
> > Although there was some talk about whether giw should use autotools,
> > or perhaps CMake, or handmade ./configure script like MPlayer IIRC,
> > instead of its own handmade Makefile...
> >
>
> To tell the truth, I'd be much happier if everything like that got
> put in a header file or some such. 95% of what we figure out by looking
> at "uname" output can already be learned by looking at the various
> pre-defined macros.
>
> Fortunately, there's a project devoted solely to this, so most of
> the tedious research need not be done. It can be found at
> http://predef.sourceforge.net/
Code talks, bullsh*t walks.
Pre-defined macros cannot tell us if one have specific libraries
installed, cannot tell us if formatted IO functions support 'size
specifiers' even though compiler claim C99 compliance or even though
compiler doesn't claim C99 compliance but supports this, etc.
But perhaps the "uname" based compile configuration could be replaced
by testing pre-defined macros... at least for C code, and git is not
only C code.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2007-12-07 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 2:10 In future, to replace autotools by cmake like KDE4 did? J.C. Pizarro
2007-12-07 7:56 ` Marcel Holtmann
2007-12-07 12:14 ` Jakub Narebski
2007-12-07 12:44 ` Andreas Ericsson
2007-12-07 13:56 ` Jakub Narebski [this message]
2007-12-07 14:42 ` J.C. Pizarro
2007-12-07 16:10 ` Marco Costalba
2007-12-10 20:23 ` Jan Hudec
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=200712071456.11019.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=ae@op5.se \
--cc=davem@davemloft.net \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=git@vger.kernel.org \
--cc=ismail@pardus.org.tr \
--cc=jcpiza@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 NNTP newsgroup(s).