[PySide] setup.py patch for OS X

[Matthew Brett]

Hi,

On Tue, Nov 20, 2012 at 1:53 PM, Christian Tismer <tismer at stackless.com> wrote:
> Hi Matt,
>
> Sent from my Ei4Steve
>
> On Nov 20, 2012, at 3:09, Matthew Brett <matthew.brett at gmail.com> wrote:
>
>> Hi,
>>
>> On Mon, Nov 19, 2012 at 5:10 PM, Christian Tismer <tismer at stackless.com> wrote:
>>> Hi again,
>>>
>>> Install-hell hits me again. :-(
>>>
>>> I uninstalled my homebrew version and tried to make sure that
>>> the new version from Matthew Bratt works for me. But it doesn't.
>>>
>>> I used his version of setup.py after removal and installing
>>> of Qt 4.8.3 into /Library/Frameworks and /Developer/Qt/Applications
>>> as the default is.
>>>
>>> No changes to any path related stuff in ~/.profile .
>>>
>>> When trying the build (on OS X 10.8.2), I get the following error:
>>>
>>> Linking CXX executable shiboken
>>> ld: framework not found QtCore
>>> clang: error: linker command failed with exit code 1 (use -v to see
>>> invocation)
>>> make[2]: *** [generator/shiboken] Error 1
>>> make[1]: *** [generator/CMakeFiles/shiboken.dir/all] Error 2
>>> make: *** [all] Error 2
>>> error: Error compiling shiboken
>>> (pydica)minimax:PySide-1.1.2 tismer$
>>>
>>>
>>> This is actually the very same problem that hit me since days and made me
>>> try Homebrew,
>>> which admittedly has its other shortcomings.
>>> /Library/Frameworks is on the path, and QtCore can be seen from there.
>>>
>>> Can somebody enlighten me what's wrong here?
>>> The patched setup.py should work on a standard installation, before I try to
>>> improve it and make it more flexible.
>>> Is that due to the fact that Matt uses OS X 10.6, as I think to recall?
>>
>> Yes, that's right - I'm on 10.6 on a couple of boxes, but I have a
>> 10.7 - I'll give it a try.
>>
>> It would be very good to get it working across the standard setups.
>
> Good news:
> Your installer works as is on Mountain Lion !!
>
> The only problem was cmake 2.8.10.1 installed by homebrew.
>
> I actually found a hint on gmane that was actually from you :-) (earlier this year).

Oh - really - 2.8.10.1 busted?  I thought they had fixed the bug in
2.8.10.1 - any chance of reporting back to the cmake guys on the list?

> Downgrading cmake to 2.8.9 did the trick.
> Maybe we need to add a version check that prevends the trouble I had with this.
> I think of black-listing versions that do not work.

I was hoping it was just 2.8.10 that was bust - but if the current
version is bust, yes, we probably ought to check...

Best,

Matthew