Re: install_name for libraries and frameworks on OS X

2008-05-22 Thread Blake Nicholson
On May 22, 2008, at 4:26 AM, Nicola Pero wrote: Please let me know if you have any feedback on my patch below, or if you think it is ready to commit. The only (purely aestethical) change I'd make is I'd put make sure GNUSTEP_ABSOLUTE_INSTALL_PATHS gets set to '' if not running on Mac OS X ...

Re: install_name for libraries and frameworks on OS X

2008-05-21 Thread Blake Nicholson
On May 18, 2008, at 8:02 AM, Nicola Pero wrote: 1) Update configure.ac in gnustep-make so it prints a warning if the user is on darwin and uses a filesystem layout other than 'apple'. This warning will tell the user they need to either set DYLD_LIBRARY_PATH and DYLD_FRAMEWORK_PATH in their shell'

[gnustep-gui] [NSMenuItem setKeyEquivalent:] nil value

2008-05-17 Thread Blake Nicholson
I just wanted to bring something to the attention of any gnustep-gui folks out there. On Mac OS X, nil should never be passed as a key equivalent. To define no key equivalent, one should pass an empty string. The code for [NSMenuItem setKeyEquivalent:] in gnustep-gui checks for (and corr

Re: install_name for libraries and frameworks on OS X

2008-05-14 Thread Blake Nicholson
having a ./configure flag to turn that behaviour on and off ? Or maybe a make option (make full_install_name=yes ?) Thanks -Original Message- From: Blake Nicholson <[EMAIL PROTECTED]> Sent: Tuesday, 13 May, 2008 20:41 To: [EMAIL PROTECTED] Cc: gnustep-dev@gnu.org Subject: Re: i

Re: install_name for libraries and frameworks on OS X

2008-05-13 Thread Blake Nicholson
Hi Nicola, Thank you for the extensive feedback. It appears to me that your suggestion is that we go with what I described as option 1 (tell users on OS X they need to use the apple filesystem). This is a reasonable solution to me. I think it would be wise to add some checking to confi

install_name for libraries and frameworks on OS X

2008-05-12 Thread Blake Nicholson
I plan to apply the following patch to gnustep-make, but would like to see if anyone has any feedback against doing so first. The purpose of this patch is to set the install_name on Mac OS X to an absolute (rather than relative) path for libraries and frameworks. My reason for doing this

[PATCH] GSCategories.h: removal of IF_NO_GC

2008-05-09 Thread Blake Nicholson
With the addition of the #define of IF_NO_GC in GNUstep.h in revision 26357, we no longer need to #define it in GSCategories.h. The patch below removes the definition of IF_NO_GC from GSCategories.h. If people would prefer, we could instead leave this in GSCategories.h and surround it with

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-30 Thread Blake Nicholson
On Mar 30, 2008, at 10:27 AM, Nicola Pero wrote: On 30 Mar 2008, at 14:55, Blake Nicholson wrote: Nicola, Unfortunately, I think the sample output I sent was not a good representation. Sorry about that. I went ahead and built base under apple-apple-apple and redirected stderr to a file

Re: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-24 Thread Blake Nicholson
the output of 'make messages=yes' on Mac OS X that shows the warnings you are wanting to suppress ? Thanks On 22 Mar 2008, at 14:45, Blake Nicholson wrote: I sent this a few days back and haven't heard anything so I thought I'd try again. I'm not sure if I haven't he

Fwd: PATCH: suppress deprecation warnings on OS X Leopard

2008-03-22 Thread Blake Nicholson
heir relevant makefiles? 2) Is INTERNAL_OBJCFLAGS the correct variable to which this compiler setting should be added? Thanks, Blake Begin forwarded message: From: Blake Nicholson <[EMAIL PROTECTED]> Date: March 18, 2008 4:00:28 PM GMT-04:00 To: gnustep-dev@gnu.org Subject: PATCH: suppress

PATCH: suppress deprecation warnings on OS X Leopard

2008-03-18 Thread Blake Nicholson
The following patch modifies target.make so that it adds the compiler option -Wno-deprecated-declarations when compiling GNUstep on Mac OS X 10.5 (Leopard) using Apple's GCC. Is this kind of wholesale disabling of warnings okay, or should this be done on an individual GNUmakefile level?