[Ctk-developers] unknown log4qt in non-superbuild

[Jean-Christophe Fillion-Robin]

On Fri, Sep 30, 2011 at 6:22 AM, Thomas Wolf
<thomas.wolf at vision.ee.ethz.ch>wrote:

> Hi Jean-Christophe,
>
> thansk for inspecting the matter. I am currently investigating your
> suggestion.
>
> >
> > Waiting we find a solution, would it be possible for you to follow
> > what's done in UseCase2 to have your project compiling and linking.
> >
> > You could do something like:
> > Within the /path/to/ThirdParty/CMakeLists.txt
> >
> > SET(CTK_LIB_PluginFramework OFF)
> > SET(CTK_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_RUNTIME_OUTPUT_DIRECTORY})
> > SET(CTK_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_LIBRARY_OUTPUT_DIRECTORY})
> > SET(CTK_ARCHIVE_OUTPUT_DIRECTORY ${CMAKE_ARCHIVE_OUTPUT_DIRECTORY})
> > SET(LogQt_DIR "/path/to/Log4Qt-build")
> > add_subdirectory(CTK)
> > set(CTK_DIR ${CMAKE_CURRENT_BINARY_DIR}/CTK-build)
> > find_package(CTK)
>
>
> I'm slightly puzzled. Why do you turn of the CTKPluginFramework? As my
> parent project is MITK, CTKPluginFramework ist actually *the thing* i
> need from CTK.
>

This was just an example ... I wanted to test quickly and I enabled the
minimum.
Jc


>
> Regards,
> Thomas
>



-- 
+1 919 869 8849
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20110930/8ebae140/attachment.htm>