There's a problem with activating an installation of InsightToolkit
(currently in revision), when building it against python2.5 as a framework,
i.e.:
DEBUG: Adding file to file_map:
/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/WrapITK.pth
for: InsightToolkit
Error: Target org.macports.activate returned: Not a directory
Warning: the following items did not execute (for InsightToolkit):
org.macports.activate
Error: Status 1 encountered during processing.
[ r...@x ]# ls -l
/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
lrwxr-xr-x 1 root wheel 24 2009-05-13 14:28
/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 ->
/opt/local/lib/python2.5/
Perhaps the python2.5 port could not "pretend" to be a framework
installation (i.e., place no symlinks into the python framework, or actually
install as a framework, as in python2.6), or the port activation process
could be a little more flexible to allow the activation against a symlink
location.
The fix for this InsightToolkit port will be to change the build
configuration to point directly to the python2.5 installs under
${prefix}/lib, ${prefix}/include, etc.
Take care,
Darren
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
