Hi Matt,
If I understand you correctly, your application linked successfully but
when starting it, Windows reported that it could not find some Poco
libraries, right?
In the past we had problems like this for our own projects (which use
MITK as an external project). However, when we switched to use CMake
"exports" files in MITK, the problem was gone and everything worked
without the additional target_link_libraries entries for the executable.
So I actually do not know what is causing this, but if it solves your
issue on Windows, I wouldn't care much about it. It certainly does not
hurt to have these lines.
Best,
Sascha
On 09/13/2011 02:56 PM, Clarkson, Matt wrote:
Hi there,
on Windows, I am was getting errors loading the Poco libraries. They
weren't found. I noticed that for the MITK project template, and hence
for my external application, the code was like this:
target_link_libraries(${MY_APP_NAME} org_blueberry_osgi ${ALL_LIBRARIES})
if(WIN32)
target_link_libraries(${MY_APP_NAME} ${QT_QTCORE_LIBRARY}
${QT_QTMAIN_LIBRARY})
endif()
However, for ExtApp in the main MITK distribution:
IF (WIN32)
FIND_PACKAGE(Qt4)
TARGET_LINK_LIBRARIES(ExtApp ${QT_QTCORE_LIBRARY} ${QT_QTMAIN_LIBRARY})
ENDIF(WIN32)
TARGET_LINK_LIBRARIES(ExtApp
optimized PocoFoundation debug PocoFoundationd
optimized PocoUtil debug PocoUtild
org_blueberry_osgi
${ALL_LIBRARIES})
When I added code like the second option, specifying both optimized
and debug versions, the application ran.
So, should this be standard? or added to the MITK project? Are other
people not having similar problems?
Thanks
Matt
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
