unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: CHENG Gao <chenggao@royau.me>
Cc: emacs-devel@gnu.org
Subject: Re: Some MacOSX build related questions
Date: Wed, 19 Oct 2011 17:50:26 +0200	[thread overview]
Message-ID: <B09F3BCD-FF99-43EE-8AAD-0454FD8FE791@swipnet.se> (raw)
In-Reply-To: <m27h41i5hk.fsf@royau.me>


19 okt 2011 kl. 13:29 skrev CHENG Gao:

> 
> 1) In nextstep/README, it states MacOSX supported are 10.4 and up.
> I suppose this is official. (It must be)
> 

I guess so.

> 2) Considering 1), some code that checks MAC_OS_X_VERSION > 1030 or <
> 1040  or even < 1020 seems not necessary anymore. 
> 

No, but nobody has taken the time to clean it up.

> 3) For same reason, is MAC_OS_X_VERSION_MAX_ALLOWED >=
> MAC_OS_X_VERSION_10_4 check necessary anymore?
> 

Same answer as above.

> 4) MAC_OS_X_VERSION_10_x (3, 4, 5, 6 at present) are defined in nsterm.h
> and some other files. Is it necessary? Is it enough as nsgui.h does? (as below)
> 
> ,----
> | #ifdef NS_IMPL_COCOA
> | #include <AvailabilityMacros.h>
> | #endif /* NS_IMPL_COCOA */
> `----

No, this is not enough.  For example, MAC_OS_X_VERSION_10_6 is not defined on OSX 10.4, but we use it in the source, so we must define it if not defined.
The define for MAC_OS_X_VERSION_10_6 in nsterm.m is redundant though.

> 
> 5) In nsimage.m, it has 'onTiger' check (defined in nsterm.h). If
> official support version is 10.4 (Tiger) and up, this seems not
> necessary anymore.
> 

I guess it is not, if indeed that function is available in Tiger and onwards.  But it might also mean that it is only available in Tiger and not in later versions.  I haven't checked.

	Jan D.




  parent reply	other threads:[~2011-10-19 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 11:29 Some MacOSX build related questions CHENG Gao
2011-10-19 15:45 ` Adrian Robert
2011-10-19 15:50 ` Jan Djärv [this message]
2011-10-19 16:05   ` CHENG Gao

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=B09F3BCD-FF99-43EE-8AAD-0454FD8FE791@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=chenggao@royau.me \
    --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).