Opened 11 years ago

Closed 2 years ago

Last modified 2 years ago

#23772 closed defect (fixed)

InsightToolKit: fix linking against python 2.6 framework

Reported by: jeremyhu (Jeremy Huddleston Sequoia) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: cssdev, petrrr
Port: cmake InsightToolkit

Description

I tried adding this to fix the linking:

configure.ldflags-append -F${frameworks_dir}

but that did not get passed to the cmake build process. I'm not sure if this is an issue with cmake or InsightToolkit.

Change History (7)

comment:1 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)

I wonder if you need to uncomment (and edit) Wrapping/WrapITK/Python/CMakeLists.tx

# ADD_CUSTOM_TARGET(PythonCompile ALL
#   ${PYTHON_EXECUTABLE}
#   ${PY_SITE_PACKAGES_PATH}/../compileall.py -l
#   -d "${CMAKE_INSTALL_PREFIX}/${WRAP_ITK_INSTALL_PREFIX}/lib"
#   ${WrapITK_BINARY_DIR}/lib
#
#   COMMAND ${PYTHON_EXECUTABLE}
#   ${PY_SITE_PACKAGES_PATH}/../compileall.py -l
#   -d "${CMAKE_INSTALL_PREFIX}/${WRAP_ITK_INSTALL_PREFIX}/Python"
#   ${WrapITK_BINARY_DIR}/Python
#
#   DEPENDS SwigRuntimePython ${PYTHON_MODULES}

comment:2 Changed 10 years ago by jmroot (Joshua Root)

Cc: css@… added
Type: requestdefect

comment:3 Changed 10 years ago by cssdev

Rather than using configure.ldflags, you should probably just pass the special CMake environment variable directly to the cmake configuration:

configure.env-append    CMAKE_FRAMEWORK_PATH=${frameworks_dir}

comment:4 Changed 6 years ago by mf2k (Frank Schima)

Keywords: python build failure removed
Owner: changed from dweber@… to macports-tickets@…

dweber has retired. See #43834.

comment:5 Changed 6 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:6 Changed 2 years ago by yan12125 (Chih-Hsuan Yen)

Resolution: fixed
Status: newclosed

In 1b59ebeba1383f1288adf62161e256119283fec1/macports-ports (master):

InsightToolkit{,312,314}: removed in favor of InsightToolkit-devel

The last ITK 3.x release 3.20 is out in 2010, and 4.x have been there
for almost 8 years. I see no reason to keep 3.x around.

Closes: #23772
Closes: #26373
Closes: #33857
Closes: #37894
Closes: #42973
Closes: #45634
Closes: #45670
Ref: #47691

comment:7 Changed 2 years ago by yan12125 (Chih-Hsuan Yen)

InsightToolkit (3.16.0) has been dropped in favor of InsightToolkit-devel (4.8.2). The latter does not include Python bindings. Feel free to open new issues if you need to use ITK with Python.

Note: See TracTickets for help on using tickets.