[Metakit] Fwd: Metakit On Tiger Solution

[markw]

Hi,

I hope the original sender doesn't mind me posting this to the list  
but it seems silly for people to keep having to ask for this.

This worked for me.

cheers

mark

Begin forwarded message:

> From: John Abel <admin at ccj-online.co.uk>
> Date: 13 May 2006 21:51:35 BDT
> To: markw <mark at junklight.com>
> Subject: Fwd: Metakit On Tiger Solution
>
> Mark,
>
> Here ya go!  This is one of 2 solutions that I've got, but it is  
> the only that works properly.
>
> Regards
>
> John
>
>> Begin forwarded message:
>>
>>> From: David Morford <david at semanteme.com>
>>> Date: 22 January 2006 21:37:01 GMT
>>> To: admin at ccj-online.co.uk
>>> Subject: Metakit On Tiger Solution
>>>
>>> Jon,
>>>
>>> Saw your post on Metakit build on Tiger with a Python 2.4  
>>> framework. Had the same problem here and just found the solution  
>>> so I thought I would forward along. After configuring in the  
>>> build directory, edit the Makefile and add this:
>>>
>>> PYTHONLIB_LD = g++ -bundle -framework Python
>>>
>>> Then find the target for Mk4py and change it to use the link  
>>> variable above, ie., uses PYTHONLIB_LD vs. SHLIB_LD.
>>>
>>> Mk4py$(SHLIB_SUFFIX): $(PYOBJS) $(LOBJS) $(LINK_SPECIAL_FILES)
>>> 	$(PYTHONLIB_LD) -o $@ $(PYOBJS) $(LOBJS) $(LINK_SPECIAL_FLAGS)
>>>
>>>
>>> a make install will copy the lib and python file to site-packages  
>>> and then change the Mk4py.dylib to Mk4py.so and it should be  
>>> groovy. Python 2.4 built as framework on 10.4 must enforce  
>>> something new WRT loading shared libraries, either from Python or  
>>> Tiger or both. Perhaps the 2.4.x framework misses adding .dylib  
>>> as a recognized extension that is loadable and is indicated by  
>>> changing the file name as stated above to get it to work once it  
>>> is compiled with the framework switch as bundle. Or... Tiger is  
>>> doing something odd with its new dyld or it may have something to  
>>> do with the framework build not generating a libpython24.dylib by  
>>> default even though the 'Python' binary in the framework is  
>>> exactly the same thing as the libpython2.dylib in /{opt or usr}/ 
>>> local/lib
>>>
>>> Note that I used the file path for the framework when I  
>>> configured it from also, like so:
>>>
>>> ../unix/configure --prefix=/opt/local --with-python=/Library/ 
>>> Frameworks/Python.framework/Versions/2.4
>>>
>>> I ran into numerous issues getting Python 2.4.2 building and  
>>> copying resources correctly as a framework without hosing the  
>>> installed Python. I ran into more issues with PyObjC, AppScript  
>>> and pythonw and Redland. I had to create a lot of the symlinks  
>>> and manually copy resrouces and libpython2.dylib myself. The  
>>> portfile for Python 2.4 on DarwinPorts is completely wrong. Using  
>>> the Python 2.3 makefile and sources Apple puts up as part of  
>>> Darwin as a reference helped quite a bit.
>>>
>>> I'll send mail to Jean-Claude with the problem so he can make a  
>>> patch/fix/whatever.
>>>
>>> Regards,
>>> Dave
>>>
>>> David Morford | Founder, Partner  | david at semanteme.com
>>> Semanteme LLC | www.semanteme.com | "Individual results will vary."
>>
>