RE: gnustep make on MacOSX

[Nicola Pero]

You need to check the Apple documentation - IIRC, in Mac OS X 10.5 Apple 
completely changed the way you specify 
the files that an application can open (see UTExportedTypeDeclarations etc).

Thanks


PS: On this topic, I think the current way that gnustep-make creates Info.plist 
files "for you" is actually rather
confusing/in the way.  It merges information from the makefiles with your 
.plist fragment, causing much confusion as most people
don't expect to have to provide a .plist fragment instead of the full .plist; 
moreover they have to understand what
variables/makefile fragments are used by gnustep-make and how, can't easily 
keep their code up-to-date, and gnustep-make
has this difficult task of merging/creating plists which is slow and 
complicated.

For the next significant release of gnustep-make I'd like to revamp the 
generation of Info.plist files - by scrapping it :-)

I'd like a new system where:

 * if you provide an Info.plist file, it will be used verbatim with no changes 
as it is.  You may have to provide
two, one for GNUstep and one for Apple (we need to make providing two very 
simple), as I don't think they are 
compatible at the moment (but they could be!).  But at least you can write a 
full Info.plist file yourself, 
or copy&edit it from an existing application, without having to understand 
anything about how gnustep-make works.

 * if you don't provide one, a minimalistic one will be automatically generated 
for you (actually, does it need to be ?
if the application can start without one, we'll omit this step entirely, and it 
will be even simpler)

Unfortunately, this (not generating Info.plist files, and using the ones from 
the user) would be incompatible 
with the current behaviour - I guess for backwards compatibility the new 
behaviour could be triggered by 
using a GNUmakefile variable; the old behaviour would generate a warning to 
encourage people to change their
code - and after a few years we may be able to slowly make the new one the 
default and eventually lose the 
old behaviour before the end of the decade.

Obviously comments are welcome - does anyone find the existing behaviour which 
generates Info.plist files useful ?


-----Original Message-----
From: "Andreas Höschler" <ahoesch@smartsoft.de>
Sent: Friday, 16 July, 2010 16:00
To: discuss-gnustep@gnu.org
Subject: gnustep make on MacOSX

Hi all,

I am preparing migration from MacOSX 10.2.8 (Power PC) to MacOSX  
10.5.2 (Intel) and have problems building apps with gnustep make on  
this new platform. I have an app that is supposed to edit *.sproject  
files.  I have Info-gnustep.plist and CustomInfo.plist with

...
NSTypes = (
      {
         NSName = "sproject";
         NSHumanReadableName = "sproject File";
         NSUnixExtensions = ("sproject");
         NSDOSExtensions = ("sproject");
         NSRole = Editor;
         NSIcon = "projfile.tiff";
       },
...

I have also tried to copy and adopt /Applications/TextEdit.app/ 
Contents/Info.plist to my /Applications/InterfaceBuilder/Contents/ 
Info.plist with no success. How can I make gnustep make to generate  
MacOSX apps that are recognized by Finder.app as editors for given  
document types (*.smib in my case)?

Thanks a lot,

  Andreas




_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnustep