unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adrian Robert <adrian.b.robert@gmail.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: build system observations
Date: Wed, 6 Aug 2008 21:36:47 -0400	[thread overview]
Message-ID: <2B6A2B11-2FF8-460C-9A69-B211E39473BB@gmail.com> (raw)
In-Reply-To: <200808061729.m76HT06A013042@sallyv1.ics.uci.edu>


>>> #  define GNU_OBJC_CFLAGS -fgnu-runtime -Wno-import -fconstant-
>>> string-class=NSConstantString -DGNUSTEP_BASE_LIBRARY=1 -
>>> DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGSWARN -DGSDIAGNOSE
>>>     This is a new flag, better use autoconf substitions instead of
>>> the preprocessor.
>>
>> I'm not sure how to do this, but have no objection to someone else
>> making the change if it simplifies things.
>
> In configure.in:
> GNU_OBJC_CFLAGS=...
> AC_SUBST(GNU_OBJC_CFLAGS)
>
> and use @GNU_OBJC_CFLAGS@ in Makefile.in

OK.  Looking more closely there seems to be no pattern to when to use  
@...@ or #define.  In configure.in there is:

# ifdef NS_IMPL_GNUSTEP
#  define C_SWITCH_X_SYSTEM -D_REENTRANT -fPIC -fno-strict-aliasing
#  define GNU_OBJC_CFLAGS -fgnu-runtime -Wno-import ...
...

Since C_SWITCH_X_SYSTEM is a #define, it seems simpler to keep them  
both the same, instead of adding several lines in various places to do  
autoconf substitution.  Getting rid of the Makefile.c system should be  
an explicit project, done all at once.



>>> # ifdef C_SWITCH_SYSTEM
>>> # undef C_SWITCH_SYSTEM
>>> # endif
>>>
>>> This sequence has not effect, it can be removed.
>>
>> This actually comes BEFORE the above definitions, and is to prevent
>> redefinition errors.  Some files under src/s define this, but they do
>> so for X-Windows purposes.  The NS port using GNUstep can be built on
>> these systems and therefore needs to change the switch.
>
> Please look at how src/config.h is generated, it will have /* #  
> undef C_SWITCH_SYSTEM */
> so I think this never did anything.

OK, I see your point.  Removed.



>> I'd welcome help on this one.  I guess the Carbon port didn't need  
>> it,
>> but despite NS using identical "path shenanigans" to the Carbon port,
>> it didn't work there.  Not sure what the problem is.
>
> First take it out, and then when people see the problem, someone might
> help.  It's just a warning, so it should not harm anyone.

Out.





  reply	other threads:[~2008-08-07  1:36 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 18:47 Emacs.app merged Adrian Robert
2008-07-15 18:49 ` İsmail Dönmez
2008-07-15 19:28 ` Chong Yidong
2008-07-15 22:32 ` Thomas Christensen
2008-07-15 23:29   ` Cezar Halmagean
2008-07-16  9:25 ` a review of the merge (Re: Emacs.app merged) Dan Nicolaescu
2008-07-16 10:00   ` Jason Rumney
2008-07-16 12:17     ` Adrian Robert
2008-07-16 16:15       ` Stefan Monnier
2008-07-16 16:21   ` Stefan Monnier
2008-07-16 21:23     ` Dan Nicolaescu
2008-07-20  1:27       ` Adrian Robert
2008-07-20 11:56         ` Dan Nicolaescu
2008-07-28 13:25           ` Adrian Robert
2008-07-28 19:00             ` Dan Nicolaescu
2008-08-01 10:48               ` Adrian Robert
2008-08-01 11:09                 ` Jason Rumney
2008-08-01 12:55                   ` Dan Nicolaescu
2008-08-01 13:36                     ` Eli Zaretskii
2008-08-01 13:49                     ` Jason Rumney
2008-08-01 14:23                       ` Dan Nicolaescu
2008-08-01 14:48                         ` Adrian Robert
2008-08-01 15:07                           ` Dan Nicolaescu
2008-07-17  1:25   ` Adrian Robert
2008-07-17  3:24     ` Dan Nicolaescu
2008-07-17  4:16       ` FOR-RELEASE [was Re: a review of the merge (Re: Emacs.app merged)] Glenn Morris
2008-07-17  4:19       ` a review of the merge (Re: Emacs.app merged) Glenn Morris
2008-07-17 17:22       ` Adrian Robert
2008-07-17 18:08         ` Dan Nicolaescu
2008-07-17  3:43     ` Stefan Monnier
2008-07-17  7:33       ` David De La Harpe Golden
2008-07-17  6:55   ` Dan Nicolaescu
2008-07-16 19:26 ` Emacs.app merged Stefan Monnier
2008-07-17  1:26   ` Adrian Robert
2008-07-27 20:12 ` some missing code? (was: Re: Emacs.app merged) Dan Nicolaescu
2008-07-27 22:18 ` observations for ns*.m files (Re: " Dan Nicolaescu
2008-07-28  1:54   ` Adrian Robert
2008-07-28  2:58     ` Dan Nicolaescu
2008-07-28  4:16       ` Stefan Monnier
2008-07-28 11:00         ` Miles Bader
2008-07-28  7:15       ` Jason Rumney
2008-07-28 13:29         ` Adrian Robert
2008-07-28 13:54           ` Chong Yidong
2008-07-28 15:10           ` Jason Rumney
2008-07-28 13:28       ` Adrian Robert
2008-07-28 14:35         ` Dan Nicolaescu
2008-08-05  5:13 ` build system observations (was " Dan Nicolaescu
2008-08-06 16:25   ` Adrian Robert
2008-08-06 17:29     ` build system observations Dan Nicolaescu
2008-08-07  1:36       ` Adrian Robert [this message]
2008-09-05 15:03         ` Stefan Monnier

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2B6A2B11-2FF8-460C-9A69-B211E39473BB@gmail.com \
    --to=adrian.b.robert@gmail.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    /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.savannah.gnu.org/cgit/emacs.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).