On further investigation, the App doesn’t have an .sdef, so, the “sdef” tool, must generate it from the old style ‘aete’ resources. So, the fault could be in either “sdef” or “sdp”.
I’ve trying to look at the output from “sdef” but it’s in a horrible format - no line endings, so it’s hard to read. If I try to open it as an xml in XCode all I get is a one HUGE line of text and XCode struggles to deal with it (slow as a very slow thing on a cold morning). Cheers Dave > On 25 Jun 2015, at 14:29, Dave <d...@looktowindward.com> wrote: > > >> On 25 Jun 2015, at 14:24, Jean-Daniel Dupas <mail...@xenonium.com> wrote: >> That just means you wrote an invalid sdef file in the first place. > > Really? No kidding?!?!? lol > > The .sdef file comes with the App I am trying to generate the header file > for!!!!! > > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > Please do not post admin requests or moderator comments to the list. > Contact the moderators at cocoa-dev-admins(at)lists.apple.com > > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/cocoa-dev/dave%40looktowindward.com > > This email sent to d...@looktowindward.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
