Re: Unable to load nib file / Problem with CompileXIB

[Ryan Schmidt]

On Jan 18, 2021, at 06:40, Janosch Peters wrote:

> I need sparkle as a dependency for the new MacPass port. Your points about 
> sparkle are of course valid. When I wrote the message I thought it might 
> still be nice to give users the choice to use it or not - via a variant for 
> instance.

No, we would not accept such a variant. Ports should not update their own 
files. MacPorts updates the files when the user asks it to.

Re: Unable to load nib file / Problem with CompileXIB

[Janosch Peters via macports-users]

> Am 12.01.2021 um 02:46 schrieb Ryan Schmidt :
> 
> On Jan 11, 2021, at 09:41, Janosch Peters wrote:
> 
>> I am struggling to create working port file for 
>> sparkle(https://github.com/sparkle-project/Sparkle). All targets contained 
>> in the Xcode project are building with no errors but when I build & install 
>> sparkle via macports and start the „Sparkle Test App“ app bundle I get this: 
>> 
>> 2021-01-11 16:22:56.277 Sparkle Test App[66399:870691] Unable to load nib 
>> file: MainMenu, exiting
> 
> It might help if you attach or provide a link to your WIP portfile so that we 
> can try it out.
> 
> Also, how do you envision a sparkle port being useful in MacPorts? Being an 
> automatic update framework, the way someone would usually use sparkle is by 
> incorporating it into their own project's source code. That's how we normally 
> encounter sparkle in MacPorts, and then we have to expend some effort in 
> figuring out how to remove sparkle from that project, since we don't want 
> that functionality in ports installed by MacPorts. (MacPorts, not the project 
> itself via sparkle, is responsible for updating things.)
> 


Hi Ryan,

I need sparkle as a dependency for the new MacPass 
 port. Your points about 
sparkle are of course valid. When I wrote the message I thought it might still 
be nice to give users the choice to use it or not - via a variant for instance. 
Also, I thought it might be easier to satisfy the dependency for MacPass rather 
than to remove it via patches.

But it turned out that removing sparkle from MacPass is pretty easy and also I 
ran into other problems with sparkle concerning code signing. So for the time 
being, I decided that I will remove sparkle as a dependency.

Thanks anyway.

Re: Unable to load nib file / Problem with CompileXIB

[Ryan Schmidt]

On Jan 11, 2021, at 09:41, Janosch Peters wrote:

> I am struggling to create working port file for 
> sparkle(https://github.com/sparkle-project/Sparkle). All targets contained in 
> the Xcode project are building with no errors but when I build & install 
> sparkle via macports and start the „Sparkle Test App“ app bundle I get this: 
> 
> 2021-01-11 16:22:56.277 Sparkle Test App[66399:870691] Unable to load nib 
> file: MainMenu, exiting
> 
> I do not get this error if I run the same app bundle built from Xcode. I 
> noticed there is a difference between those app bundles. Whereas the macports 
> bundle looks like this:
> 
> Contents
>  |__ Resources
>   |__.lproj
>   |__InfoPlist.strings
> 
> 
> The Xcode app bundle looks like this:
> 
> Contents
>  |__ Resources
>   |__.lproj
>   |__MainMenu.string
> 
> 
> I have very limited Xcode experience but for me it looks like that the 
> missing MainMenu.string could be the problem. I also noticed that the 
> CompileXIB command is different between Xcode and macports. See [1] and [2] 
> attached. Is there a way to make MacPorts use a command like [2] instead of 
> [1]?

It might help if you attach or provide a link to your WIP portfile so that we 
can try it out.

Also, how do you envision a sparkle port being useful in MacPorts? Being an 
automatic update framework, the way someone would usually use sparkle is by 
incorporating it into their own project's source code. That's how we normally 
encounter sparkle in MacPorts, and then we have to expend some effort in 
figuring out how to remove sparkle from that project, since we don't want that 
functionality in ports installed by MacPorts. (MacPorts, not the project itself 
via sparkle, is responsible for updating things.)