[Insight-developers] ITK & WrapITK Install better, still not great.

[Ashish Sharma]

I could come up with the following possible locations for WrapITK install:

1. ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0/WrapITK.
This is EXISTING. Sure this should be changed

2. ${CMAKE_INSTALL_PREFIX}/lib/WrapITK-4.0/ .
With this  user sets up path per WrapITK version or we could do that as part
of the installation

3. ${CMAKE_INSTALL_PREFIX}/lib/.
Versioned names for WrapITK modules. But where to keep python proxies?
Should we have versioned names for them as well?

4. ${CMAKE_INSTALL_PREFIX}/lib/ITK-4.0/WrapITK/
Might be better to put all ITK-4.0 packages inside a single ITK-4.0
directory. We won't require versioned names.

5. ${CMAKE_INSTALL_PREFIX}/lib/ITK-4.0/
Put all wrapITK libraries here along with libraries of other packages. We
won't require versioned names.

6. ${JAVA_LIB_PATH}/lib/ & ${PYTHON_LIB_PATH}
Versioned names for WrapITK modules for respective languages. Not really
sure if this would be appropriate?
Any comments/thoughts on these are welcome :-)

Ashish

On Thu, May 5, 2011 at 2:09 PM, Ashish Sharma <ashishs99 at gmail.com> wrote:

> Hi Williams,
>
> We are looking into this and we will get to you as soon as possible.
>
> Ashish
>
> On Wed, May 4, 2011 at 5:01 PM, Williams, Norman K <
> norman-k-williams at uiowa.edu> wrote:
>
>> So say you want to use ITK with Wrapping.  Wrapping demands shared
>> libraries, which means you have to fool around with setting
>> {DY}LD_LIBRARY_PATH. If you use TCL (as we do) TCLLIBPATH, or the
>> equivalent environment variable for the wrapping language of your choice
>> needs setting as well.
>>
>>
>> So here's the situation right now:
>>
>> 1. ITK libraries go into ${CMAKE_INSTALL_PREFIX}/lib
>> 2. ITK Config files (I.e. where you want to point ITK_DIR) go
>>   into ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0
>> 3. WrapITK libraries go into
>> ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0/WrapITK/lib
>> 4. WrapITK Tcl files goes into
>> ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0/WrapITK/Tcl
>> 5. Python stuff goes into
>> ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0/WrapITK/lib &
>>   ${CMAKE_INSTALL_PREFIX}/lib/cmake/ITK-4.0/WrapITK/Python
>>
>> Now I don't know what the right thing to do is, but it's a complete change
>> from ITKV3.x
>>
>> Before all the libraries went to
>> ${CMAKE_INSTALL_PREFIX}/lib/InsightToolkit, & Wrapping stuff went into
>> .../InsightToolkit/WrapITK ...
>>
>> The ITK3 wasn't that bad, but the ITK4 way is squirrelly. Especially in
>> these respects:
>>
>> 1. Putting the CMake stuff in .../lib/cmake/ITK-4.0 instead of in
>> .../lib/InsightToolkit
>> 2. Putting the libraries in .../lib instead of .../lib/InsightToolkit
>> 3. ESPECIALLY WrapITK burying its libraries in .../lib/cmake/ITK-4.0
>>
>> So which of the things the current Install process does are by design, and
>> which are done just by happenstance?
>>
>>
>>
>> ________________________________
>> Notice: This UI Health Care e-mail (including attachments) is covered by
>> the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
>> confidential and may be legally privileged.  If you are not the intended
>> recipient, you are hereby notified that any retention, dissemination,
>> distribution, or copying of this communication is strictly prohibited.
>>  Please reply to the sender that you have received the message in error,
>> then delete it.  Thank you.
>> ________________________________
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20110517/11841aa8/attachment.htm>