Follow-up Comment #1, bug #26280 (project gnustep):
Hi Jonathan
sorry for the late reply.
The problem you're experiencing might be due to a misunderstanding / lack of
explanations in the gnustep-make documentation.
I guess I'll quote stuff from gnustep-make --
# If you want to insert your own entries into Info.plist (or
# Info-gnustep.plist) you should create a xxxInfo.plist file (where
# xxx is the bundle name) and gnustep-make will automatically
# read it and merge it into Info-gnustep.plist.
So, you shouldn't create an Info-gnustep.plist file yourself. Create a
xxxInfo.plist file instead. gnustep-make will read it, merge it with any
additional information it automatically needs to add to create the "official"
Info-gnustep.plist, and generate Info-gnustep.plist.
Applications work in the same way; eg, if you check Gorm, you'll see it has a
GormInfo.plist with its custom entries; the Info-gnustep.plist is
automatically generated by gnustep-make from GormInfo.plist.
Let me know if this is of any help. Sorry again for the very late reply.
Thanks
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?26280>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
