pallet needs a new build for 10.6 compatibility

[blb@…]

For the DMG-distributed Pallet, it should really include a 64bit built as well, since otherwise anyone on 10.6 who build from source or used selfupdate will probably only have a 64bit MacPorts infrastructure.

A quick test here (on 10.6.1) required that the framework be set to use the 10.5 SDK and build "Standard" (32/64-bit Universal), and the same for the Pallet app itself.

I haven't had a chance to test on 10.5 yet, however.

Also, do we want to copy the MPGUI stuff someplace in contrib and out of the GSoC branch?

[domiman@…]

Cc Me!

[nlavine@…]

Cc Me!

[nlavine@…]

I would like to work on this, with the hope of getting it going by the end of the week. I've already started looking at it in Xcode, and found a couple build settings that need changing to make it build. I just got it to the point where I run into the same error that crashes the official MacPorts build, so hopefully I can start making actual progress soon.

However, I've never done any work on MacPorts before. Could anyone suggest documentation on how to get changes into the MacPorts system, or people to ask about that? Also, does anyone have experience working with the Pallet/MacPorts.framework codebase?

[armahg@…]

Replying to nlavine@…:

I would like to work on this, with the hope of getting it going by the end of the week. I've already started looking at it in Xcode, and found a couple build settings that need changing to make it build. I just got it to the point where I run into the same error that crashes the official MacPorts build, so hopefully I can start making actual progress soon.

However, I've never done any work on MacPorts before. Could anyone suggest documentation on how to get changes into the MacPorts system, or people to ask about that? Also, does anyone have experience working with the Pallet/MacPorts.framework codebase?

I have some experience with it. Juan - juanger@… also worked with it for his Google Summer of Code project so he is familiar with it (especially the Pallet source code). Is there a fix out yet for the Macports official build error? Perhaps you could apply the patch for that error locally and see if the build is successful. Feel free to ping myself or Juan with questions.

[nlavine@…]

After getting Pallet building, I ran it, and discovers that it dies on a line of code that looks like this:

[[MPIndex alloc] init];

(I believe it assigns that value to a variable as well, but it doesn't do anything interesting with it.)

Therefore, it seems like the bug is in fact in MacPorts.framework, which defines MPIndex. I got the source code for that and was able to build it fine, but I haven't been able to get it to run its unit tests. I suspect there is some simple settings error that I just can't find, but that if I could fix it, I could start unit testing. Do either of you have any ideas on how to get the unit tests to run? (I'm running OS 10.6, and I just did a subversion checkout of the framework this afternoon, so I should have the latest code.)

[juanger@…]

Replying to nlavine@…: I've uploaded a new dmg which solves this bug. The source code is still the same, I only changed the configuration and the Init.plist to make it 32/64-bit Universal and force it to run the 32 bits binary on Leopard to maintain compatibility.

Please report any problems you encounter and thanks for your patience.

[nlavine@…]

I tried to use the DMG build from wiki:MacPortsGUI, which I assume is yours, but it crashed with the crash report that I just attached.

[blb@…]

That's the old one, try ​Juan's new one. If that's good we should definitely change the link on the MacPortsGUI page.

[nlavine@…]

Ah, that loads fine. It didn't seem to be able to install gtk2, but that's probably a backend problem.

What needs to be done then to make this the official MacPorts port? It seems to me it would be much better if Pallet was installed like the rest of MacPorts software (plus it would then be upgraded like other software if that needed doing).

[blb@…]

There is a port for it, but it still needs to be updated for the latest work (ticket #21259).

[nlavine@…]

Replying to juanger@…:

Replying to nlavine@…: I've uploaded a new dmg which solves this bug. The source code is still the same, I only changed the configuration and the Init.plist to make it 32/64-bit Universal and force it to run the 32 bits binary on Leopard to maintain compatibility.

Please report any problems you encounter and thanks for your patience.

Juan, could you please post your modified Init.plist file? I'd like to submit this as a patch for the version in the contrib tree, but I'm not sure what changes I would have to make to get the effect you did.

[domiman@…]

the new one still crashes for me, after chossing the TCL directory. Snow Leopard 32-bit...

[alexhaj@…]

Replying to domiman@…:

the new one still crashes for me, after chossing the TCL directory. Snow Leopard 32-bit...

Same for me but in Lion 64-bit. What the hell is the matter with MacPorts GUI (Pallet)? Let's get it so it does not crash after choosing /Library/Tcl/

[aboutlinux@…]

Newer posts on same bug #30906

[aboutlinux@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to alexhaj@…:

Replying to domiman@…:

the new one still crashes for me, after chossing the TCL directory. Snow Leopard 32-bit...

Same for me but in Lion 64-bit. What the hell is the matter with MacPorts GUI (Pallet)? Let's get it so it does not crash after choosing /Library/Tcl/

You re-opened a 2-year-old bug and provided no further information, so there's nothing we can do with this. From what I can tell in #30906 this should no longer be a problem. If you still experience a problem, please check the existing open tickets, and if none of them describes the problem you experience, file a new report with all the necessary info.