From looky12 at bk.ru  Thu Dec  1 16:29:09 2011
From: looky12 at bk.ru (=?UTF-8?B?bG9va3kxMiBsb29reTEy?=)
Date: Thu, 01 Dec 2011 20:29:09 +0400
Subject: [Ctk-developers] =?utf-8?q?ctkDICOMDemoSCUMain=2Eobj_=3A_error_LN?=
	=?utf-8?q?K2019?=
Message-ID: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>

Hello everyone, i have some problems in build process, thanks for your attention.

1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
1>Performing update step (git fetch) for 'qxmlrpc'
1>Performing configure step for 'qxmlrpc'
1>-- Configuring done
1>-- Generating done
1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
1>Performing build step for 'qxmlrpc'
1>Microsoft (R) Visual Studio Version 9.0.30729.1.
1>Copyright (C) Microsoft Corp. All rights reserved.
1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped ==========
1>No install step for 'qxmlrpc'
1>Completed 'qxmlrpc'
1>Build log was saved at "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
1>qxmlrpc - 0 error(s), 0 warning(s)
2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32 ------
2>Performing configure step for 'CTK-Configure'
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
2>-- CTKCore: BFD support disabled
2>-- Configuring done
2>-- Generating done
2>CMake Warning:
2>? Manually-specified variables were not used by the project:
2>??? CTEST_USE_LAUNCHERS
2>??? DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
2>??? DOCUMENTATION_TARGET_IN_ALL
2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
2>No build step for 'CTK-Configure'
2>No install step for 'CTK-Configure'
2>Completed 'CTK-Configure'
2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
2>CTK-Configure - 0 error(s), 0 warning(s)
3>------ Build started: Project: CTK-build, Configuration: Debug Win32 ------
3>Microsoft (R) Visual Studio Version 9.0.30729.1.
3>Copyright (C) Microsoft Corp. All rights reserved.
3>1>------ Build started: Project: CTKVisualizationVTKWidgets, Configuration: Debug Win32 ------
3>1>Compiling...
3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug Win32 ------
3>2>Linking...
3>1>ctkVTKScalarsToColorsView.cpp
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@@UAE at XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)" (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)" (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: class OFCondition __thiscall ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU@@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString@@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)" (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ) referenced in function _main
3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal error LNK1120: 9 unresolved externals
3>2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596) : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606) : error C2664: 'void vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins, Configuration: Debug Win32 ------
3>3>Linking...
3>3>LINK : fatal error LNK1104: cannot open file '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
3>3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped ==========
3>Project : error PRJ0019: A tool returned an error code from 
3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
3>CTK-build - 14 error(s), 0 warning(s)
========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111201/e0cd2ccc/attachment.htm>

From pieper at ibility.net  Thu Dec  1 19:10:00 2011
From: pieper at ibility.net (Steve Pieper)
Date: Thu, 1 Dec 2011 14:10:00 -0500
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
References: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
Message-ID: <CA+OFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>

Hi -

Looks like you are also getting build errors related to ctkVTK -- makes me
wonder if somehow your build isn't up to date. If you turn off dicom and
vtk does everything else build?

-Steve

On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:

> Hello everyone, i have some problems in build process, thanks for your
> attention.
>
> 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
> 1>Performing update step (git fetch) for 'qxmlrpc'
> 1>Performing configure step for 'qxmlrpc'
> 1>-- Configuring done
> 1>-- Generating done
> 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
> 1>Performing build step for 'qxmlrpc'
> 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 1>Copyright (C) Microsoft Corp. All rights reserved.
> 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped
> ==========
> 1>No install step for 'qxmlrpc'
> 1>Completed 'qxmlrpc'
> 1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
> 1>qxmlrpc - 0 error(s), 0 warning(s)
> 2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32
> ------
> 2>Performing configure step for 'CTK-Configure'
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
> 2>-- Generated:
> C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
> 2>-- CTKCore: BFD support disabled
> 2>-- Configuring done
> 2>-- Generating done
> 2>CMake Warning:
> 2>  Manually-specified variables were not used by the project:
> 2>    CTEST_USE_LAUNCHERS
> 2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
> 2>    DOCUMENTATION_TARGET_IN_ALL
> 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
> 2>No build step for 'CTK-Configure'
> 2>No install step for 'CTK-Configure'
> 2>Completed 'CTK-Configure'
> 2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
> 2>CTK-Configure - 0 error(s), 0 warning(s)
> 3>------ Build started: Project: CTK-build, Configuration: Debug Win32
> ------
> 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 3>Copyright (C) Microsoft Corp. All rights reserved.
> 3>1>------ Build started: Project: CTKVisualizationVTKWidgets,
> Configuration: Debug Win32 ------
> 3>1>Compiling...
> 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug
> Win32 ------
> 3>2>Linking...
> 3>1>ctkVTKScalarsToColorsView.cpp
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU
> @@UAE?AVOFCondition@@E at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU
> @@UAE?AVOFCondition@@XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@
> @UAE at XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)"
> (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)"
> (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: class OFCondition __thiscall
> ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class
> OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU
> @@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString
> @@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
> (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const
> &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in
> function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
> referenced in function _main
> 3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal
> error LNK1120: 9 unresolved externals
> 3>2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
> 3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
> : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f
> &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to
> 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
> : error C2664: 'void
> vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot
> convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
> 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
> 3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins,
> Configuration: Debug Win32 ------
> 3>3>Linking...
> 3>3>LINK : fatal error LNK1104: cannot open file
> '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
> 3>3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
> 3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
> 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped
> ==========
> 3>Project : error PRJ0019: A tool returned an error code from
> 3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
> 3>CTK-build - 14 error(s), 0 warning(s)
> ========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========
>
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111201/53ed0a51/attachment.htm>

From jchris.fillionr at kitware.com  Fri Dec  2 05:20:25 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Fri, 2 Dec 2011 00:20:25 -0500
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <CA+OFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
References: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CA+OFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
Message-ID: <CANLz8R4oe5iy17PAz1vKXGLKhxiBdc3wGgsrXBK9ABVgN0d7sA@mail.gmail.com>

Julien> Could this issue be related to the fact that the option
USE_TRANSFER_FUNCTION_CHARTS is now enabled by default ?
See https://github.com/commontk/CTK/commit/29201c2

Jc

On Thu, Dec 1, 2011 at 2:10 PM, Steve Pieper <pieper at ibility.net> wrote:

> Hi -
>
> Looks like you are also getting build errors related to ctkVTK -- makes me
> wonder if somehow your build isn't up to date. If you turn off dicom and
> vtk does everything else build?
>
> -Steve
>
>  On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
>
>>  Hello everyone, i have some problems in build process, thanks for your
>> attention.
>>
>> 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32
>> ------
>> 1>Performing update step (git fetch) for 'qxmlrpc'
>> 1>Performing configure step for 'qxmlrpc'
>> 1>-- Configuring done
>> 1>-- Generating done
>> 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
>> 1>Performing build step for 'qxmlrpc'
>> 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
>> 1>Copyright (C) Microsoft Corp. All rights reserved.
>> 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped
>> ==========
>> 1>No install step for 'qxmlrpc'
>> 1>Completed 'qxmlrpc'
>> 1>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
>> 1>qxmlrpc - 0 error(s), 0 warning(s)
>> 2>------ Build started: Project: CTK-Configure, Configuration: Debug
>> Win32 ------
>> 2>Performing configure step for 'CTK-Configure'
>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
>> 2>-- Generated:
>> C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
>> 2>-- CTKCore: BFD support disabled
>> 2>-- Configuring done
>> 2>-- Generating done
>> 2>CMake Warning:
>> 2>  Manually-specified variables were not used by the project:
>> 2>    CTEST_USE_LAUNCHERS
>> 2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
>> 2>    DOCUMENTATION_TARGET_IN_ALL
>> 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
>> 2>No build step for 'CTK-Configure'
>> 2>No install step for 'CTK-Configure'
>> 2>Completed 'CTK-Configure'
>> 2>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
>> 2>CTK-Configure - 0 error(s), 0 warning(s)
>> 3>------ Build started: Project: CTK-build, Configuration: Debug Win32
>> ------
>> 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
>> 3>Copyright (C) Microsoft Corp. All rights reserved.
>> 3>1>------ Build started: Project: CTKVisualizationVTKWidgets,
>> Configuration: Debug Win32 ------
>> 3>1>Compiling...
>> 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug
>> Win32 ------
>> 3>2>Linking...
>> 3>1>ctkVTKScalarsToColorsView.cpp
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: virtual class OFCondition __thiscall
>> ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU
>> @@UAE?AVOFCondition@@E at Z) referenced in function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: virtual class OFCondition __thiscall
>> ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU
>> @@UAE?AVOFCondition@@XZ) referenced in function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@
>> @UAE at XZ) referenced in function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)"
>> (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function
>> _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)"
>> (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function
>> _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: class OFCondition __thiscall
>> ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class
>> OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU
>> @@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString
>> @@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
>> (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const
>> &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in
>> function _main
>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>> "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
>> referenced in function _main
>> 3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal
>> error LNK1120: 9 unresolved externals
>> 3>2>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
>> 3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
>> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
>> : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f
>> &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to
>> 'vtkIdTypeArray *'
>> 3>1>        Conversion from integral type to pointer type requires
>> reinterpret_cast, C-style cast or function-style cast
>> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
>> : error C2664: 'void
>> vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot
>> convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
>> 3>1>        Conversion from integral type to pointer type requires
>> reinterpret_cast, C-style cast or function-style cast
>> 3>1>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
>> 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
>> 3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins,
>> Configuration: Debug Win32 ------
>> 3>3>Linking...
>> 3>3>LINK : fatal error LNK1104: cannot open file
>> '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
>> 3>3>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
>> 3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
>> 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped
>> ==========
>> 3>Project : error PRJ0019: A tool returned an error code from
>> 3>Build log was saved at
>> "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
>> 3>CTK-build - 14 error(s), 0 warning(s)
>> ========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped
>> ==========
>>
>>
>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>


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

From julien.finet at kitware.com  Fri Dec  2 05:42:35 2011
From: julien.finet at kitware.com (Julien Finet)
Date: Thu, 1 Dec 2011 23:42:35 -0600
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <CANLz8R4oe5iy17PAz1vKXGLKhxiBdc3wGgsrXBK9ABVgN0d7sA@mail.gmail.com>
References: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CA+OFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
	<CANLz8R4oe5iy17PAz1vKXGLKhxiBdc3wGgsrXBK9ABVgN0d7sA@mail.gmail.com>
Message-ID: <CAKoWPPEbhisZxymNPvSFL9tbjKJOFroFtkNB0han5v5Ac7eLiA@mail.gmail.com>

Good catch, I just disabled it by default.
julien.

On Thu, Dec 1, 2011 at 11:20 PM, Jean-Christophe Fillion-Robin <
jchris.fillionr at kitware.com> wrote:

> Julien> Could this issue be related to the fact that the option
> USE_TRANSFER_FUNCTION_CHARTS is now enabled by default ?
> See https://github.com/commontk/CTK/commit/29201c2
>
> Jc
>
>
> On Thu, Dec 1, 2011 at 2:10 PM, Steve Pieper <pieper at ibility.net> wrote:
>
>> Hi -
>>
>> Looks like you are also getting build errors related to ctkVTK -- makes
>> me wonder if somehow your build isn't up to date. If you turn off dicom and
>> vtk does everything else build?
>>
>> -Steve
>>
>>  On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
>>
>>>  Hello everyone, i have some problems in build process, thanks for your
>>> attention.
>>>
>>> 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32
>>> ------
>>> 1>Performing update step (git fetch) for 'qxmlrpc'
>>> 1>Performing configure step for 'qxmlrpc'
>>> 1>-- Configuring done
>>> 1>-- Generating done
>>> 1>-- Build files have been written to:
>>> C:/CTK/CTK-superbuild/qxmlrpc-build
>>> 1>Performing build step for 'qxmlrpc'
>>> 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
>>> 1>Copyright (C) Microsoft Corp. All rights reserved.
>>> 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped
>>> ==========
>>> 1>No install step for 'qxmlrpc'
>>> 1>Completed 'qxmlrpc'
>>> 1>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
>>> 1>qxmlrpc - 0 error(s), 0 warning(s)
>>> 2>------ Build started: Project: CTK-Configure, Configuration: Debug
>>> Win32 ------
>>> 2>Performing configure step for 'CTK-Configure'
>>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
>>> 2>-- Generated:
>>> C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
>>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
>>> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
>>> 2>-- CTKCore: BFD support disabled
>>> 2>-- Configuring done
>>> 2>-- Generating done
>>> 2>CMake Warning:
>>> 2>  Manually-specified variables were not used by the project:
>>> 2>    CTEST_USE_LAUNCHERS
>>> 2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
>>> 2>    DOCUMENTATION_TARGET_IN_ALL
>>> 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
>>> 2>No build step for 'CTK-Configure'
>>> 2>No install step for 'CTK-Configure'
>>> 2>Completed 'CTK-Configure'
>>> 2>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
>>> 2>CTK-Configure - 0 error(s), 0 warning(s)
>>> 3>------ Build started: Project: CTK-build, Configuration: Debug Win32
>>> ------
>>> 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
>>> 3>Copyright (C) Microsoft Corp. All rights reserved.
>>> 3>1>------ Build started: Project: CTKVisualizationVTKWidgets,
>>> Configuration: Debug Win32 ------
>>> 3>1>Compiling...
>>> 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug
>>> Win32 ------
>>> 3>2>Linking...
>>> 3>1>ctkVTKScalarsToColorsView.cpp
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: virtual class OFCondition __thiscall
>>> ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU
>>> @@UAE?AVOFCondition@@E at Z) referenced in function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: virtual class OFCondition __thiscall
>>> ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU
>>> @@UAE?AVOFCondition@@XZ) referenced in function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@
>>> @UAE at XZ) referenced in function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)"
>>> (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function
>>> _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)"
>>> (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function
>>> _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: class OFCondition __thiscall
>>> ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class
>>> OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU
>>> @@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString
>>> @@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
>>> (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const
>>> &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in
>>> function _main
>>> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
>>> "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
>>> referenced in function _main
>>> 3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe :
>>> fatal error LNK1120: 9 unresolved externals
>>> 3>2>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
>>> 3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
>>> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
>>> : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f
>>> &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to
>>> 'vtkIdTypeArray *'
>>> 3>1>        Conversion from integral type to pointer type requires
>>> reinterpret_cast, C-style cast or function-style cast
>>> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
>>> : error C2664: 'void
>>> vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot
>>> convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
>>> 3>1>        Conversion from integral type to pointer type requires
>>> reinterpret_cast, C-style cast or function-style cast
>>> 3>1>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
>>> 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
>>> 3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins,
>>> Configuration: Debug Win32 ------
>>> 3>3>Linking...
>>> 3>3>LINK : fatal error LNK1104: cannot open file
>>> '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
>>> 3>3>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
>>> 3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
>>> 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped
>>> ==========
>>> 3>Project : error PRJ0019: A tool returned an error code from
>>> 3>Build log was saved at
>>> "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
>>> 3>CTK-build - 14 error(s), 0 warning(s)
>>> ========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped
>>> ==========
>>>
>>>
>>>
>>> _______________________________________________
>>> Ctk-developers mailing list
>>> Ctk-developers at commontk.org
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>
>>>
>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>>
>
>
> --
> +1 919 869 8849
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111201/b7d7e37d/attachment.htm>

From s.zelzer at dkfz-heidelberg.de  Fri Dec  2 08:24:17 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Fri, 02 Dec 2011 09:24:17 +0100
Subject: [Ctk-developers] Doxygen groups
Message-ID: <4ED88B31.4070403@dkfz-heidelberg.de>

Hi CTK developers,

I just pushed some doxygen related commits to improve the structure of 
our API documentation.

Mainly, I added a couple of new doxygen groups and added to each class 
declaration a "\ingroup ..." doxygen command. If you create new classes, 
please make sure to use the \ingroup command in the class documentation 
block to get a correct mapping. This makes it easier for people looking 
at the generated documentation to see what each library / project in CTK 
provides.

To see the current changes, you will have to wait until our doxygen 
documentation is regenerated (or build it locally yourself).

Thanks,

Sascha


From jchris.fillionr at kitware.com  Fri Dec  2 13:13:02 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Fri, 2 Dec 2011 08:13:02 -0500
Subject: [Ctk-developers] Doxygen groups
In-Reply-To: <4ED88B31.4070403@dkfz-heidelberg.de>
References: <4ED88B31.4070403@dkfz-heidelberg.de>
Message-ID: <CANLz8R7ZcWd9sgkGMogxBKwmJhcggVM5CJvcsZZW1eEQCH7+AQ@mail.gmail.com>

It looks great :) Thanks for taking care of that.

Aas a side note, I noticed that the "DICOM Application Hosting" group
doesn't seem to list any modules or classes.

Jc

On Fri, Dec 2, 2011 at 3:24 AM, Sascha Zelzer
<s.zelzer at dkfz-heidelberg.de>wrote:

> Hi CTK developers,
>
> I just pushed some doxygen related commits to improve the structure of our
> API documentation.
>
> Mainly, I added a couple of new doxygen groups and added to each class
> declaration a "\ingroup ..." doxygen command. If you create new classes,
> please make sure to use the \ingroup command in the class documentation
> block to get a correct mapping. This makes it easier for people looking at
> the generated documentation to see what each library / project in CTK
> provides.
>
> To see the current changes, you will have to wait until our doxygen
> documentation is regenerated (or build it locally yourself).
>
> Thanks,
>
> Sascha
> ______________________________**_________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-**bin/mailman/listinfo/ctk-**developers<http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers>
>



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

From s.zelzer at dkfz-heidelberg.de  Fri Dec  2 13:23:05 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Fri, 02 Dec 2011 14:23:05 +0100
Subject: [Ctk-developers] Doxygen groups
In-Reply-To: <CANLz8R7ZcWd9sgkGMogxBKwmJhcggVM5CJvcsZZW1eEQCH7+AQ@mail.gmail.com>
References: <4ED88B31.4070403@dkfz-heidelberg.de>
	<CANLz8R7ZcWd9sgkGMogxBKwmJhcggVM5CJvcsZZW1eEQCH7+AQ@mail.gmail.com>
Message-ID: <4ED8D139.3050103@dkfz-heidelberg.de>

Yes, that is work in progress.

- Sascha

On 12/02/2011 02:13 PM, Jean-Christophe Fillion-Robin wrote:
> It looks great :) Thanks for taking care of that.
>
> Aas a side note, I noticed that the "DICOM Application Hosting" group 
> doesn't seem to list any modules or classes.
>
> Jc
>
> On Fri, Dec 2, 2011 at 3:24 AM, Sascha Zelzer 
> <s.zelzer at dkfz-heidelberg.de <mailto:s.zelzer at dkfz-heidelberg.de>> wrote:
>
>     Hi CTK developers,
>
>     I just pushed some doxygen related commits to improve the
>     structure of our API documentation.
>
>     Mainly, I added a couple of new doxygen groups and added to each
>     class declaration a "\ingroup ..." doxygen command. If you create
>     new classes, please make sure to use the \ingroup command in the
>     class documentation block to get a correct mapping. This makes it
>     easier for people looking at the generated documentation to see
>     what each library / project in CTK provides.
>
>     To see the current changes, you will have to wait until our
>     doxygen documentation is regenerated (or build it locally yourself).
>
>     Thanks,
>
>     Sascha
>     _______________________________________________
>     Ctk-developers mailing list
>     Ctk-developers at commontk.org <mailto:Ctk-developers at commontk.org>
>     http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
>
>
> -- 
> +1 919 869 8849
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111202/5b22cbb5/attachment.htm>

From looky12 at bk.ru  Tue Dec  6 00:22:57 2011
From: looky12 at bk.ru (=?UTF-8?B?bG9va3kxMiBsb29reTEy?=)
Date: Tue, 06 Dec 2011 04:22:57 +0400
Subject: [Ctk-developers]
 =?utf-8?q?ctkDICOMDemoSCUMain=2Eobj_=3A_error_LN?= =?utf-8?q?K2019?=
In-Reply-To: <CAOFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
References: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CAOFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
Message-ID: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>

If i turn off only VTK in this configuration, all other projects builds.? "Makes me wonder if somehow your build isn't up to date" - sorry but i think i understand this not correctly, maybe because i attempt build projects separately at first, and then all solution. 

Sorry for my English
Oleg.


01?Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net>:
 
  
  
Hi - 

Looks like you are also getting build errors related to ctkVTK -- makes me wonder if somehow your build isn't up to date. If you turn off dicom and vtk does everything else build?

-Steve

On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
Hello everyone, i have some problems in build process, thanks for your attention.

1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
1>Performing update step (git fetch) for 'qxmlrpc'
1>Performing configure step for 'qxmlrpc'
1>-- Configuring done
1>-- Generating done
1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
1>Performing build step for 'qxmlrpc'
1>Microsoft (R) Visual Studio Version 9.0.30729.1.
1>Copyright (C) Microsoft Corp. All rights reserved.
1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped ==========
1>No install step for 'qxmlrpc'
1>Completed 'qxmlrpc'
1>Build log was saved at "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
1>qxmlrpc - 0 error(s), 0 warning(s)
2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32 ------
2>Performing configure step for 'CTK-Configure'
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
2>-- CTKCore: BFD support disabled
2>-- Configuring done
2>-- Generating done
2>CMake Warning:
2>? Manually-specified variables were not used by the project:
2>??? CTEST_USE_LAUNCHERS
2>??? DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
2>??? DOCUMENTATION_TARGET_IN_ALL
2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
2>No build step for 'CTK-Configure'
2>No install step for 'CTK-Configure'
2>Completed 'CTK-Configure'
2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
2>CTK-Configure - 0 error(s), 0 warning(s)
3>------ Build started: Project: CTK-build, Configuration: Debug Win32 ------
3>Microsoft (R) Visual Studio Version 9.0.30729.1.
3>Copyright (C) Microsoft Corp. All rights reserved.
3>1>------ Build started: Project: CTKVisualizationVTKWidgets, Configuration: Debug Win32 ------
3>1>Compiling...
3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug Win32 ------
3>2>Linking...
3>1>ctkVTKScalarsToColorsView.cpp
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@@UAE at XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)" (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)" (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: class OFCondition __thiscall ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU@@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString@@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)" (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ) referenced in function _main
3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal error LNK1120: 9 unresolved externals
3>2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596) : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606) : error C2664: 'void vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins, Configuration: Debug Win32 ------
3>3>Linking...
3>3>LINK : fatal error LNK1104: cannot open file '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
3>3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped ==========
3>Project : error PRJ0019: A tool returned an error code from 
3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
3>CTK-build - 14 error(s), 0 warning(s)
========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========



_______________________________________________
Ctk-developers mailing list
Ctk-developers at commontk.org
http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111206/15aa814e/attachment.htm>

From pieper at ibility.net  Tue Dec  6 00:38:22 2011
From: pieper at ibility.net (Steve Pieper)
Date: Mon, 5 Dec 2011 19:38:22 -0500
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
References: <E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CAOFd4wQZ9=qDxa+NSf4gT_P0BeYAJ0Ggdy1hBoQPH93Nd91Ew@mail.gmail.com>
	<E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
Message-ID: <CA+OFd4xA6R6jk1foQ-nBAhCba9UwpoFNmmcuG7N2-ecgyFNkVg@mail.gmail.com>

Hi Oleg -

Sorry - I wasn't clear - it's not your English :)

I meant that because the superbuild (top) level of the ctk cmake process
does checkouts and builds of several other packages (vtk, dcmtk, etc) I
wondered if one of those external projects was out of data or didn't build
correctly.  If you tried to build the packages by hand that might explain
the issue - typically for ctk we would just configure the ctk superbuild
level and let it take care of the dependencies.

Hope that makes more sense,
-Steve



On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru> wrote:

> If i turn off only VTK in this configuration, all other projects builds.
> "Makes me wonder if somehow your build isn't up to date" - sorry but i
> think i understand this not correctly, maybe because i attempt build
> projects separately at first, and then all solution**.
>
> Sorry for my English
> Oleg.
>
>
> 01 Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net>:
>
>  Hi -
>
> Looks like you are also getting build errors related to ctkVTK -- makes me
> wonder if somehow your build isn't up to date. If you turn off dicom and
> vtk does everything else build?
>
> -Steve
>
> On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru<http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>
> > wrote:
>
> Hello everyone, i have some problems in build process, thanks for your
> attention.
>
> 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
> 1>Performing update step (git fetch) for 'qxmlrpc'
> 1>Performing configure step for 'qxmlrpc'
> 1>-- Configuring done
> 1>-- Generating done
> 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
> 1>Performing build step for 'qxmlrpc'
> 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 1>Copyright (C) Microsoft Corp. All rights reserved.
> 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped
> ==========
> 1>No install step for 'qxmlrpc'
> 1>Completed 'qxmlrpc'
> 1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
> 1>qxmlrpc - 0 error(s), 0 warning(s)
> 2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32
> ------
> 2>Performing configure step for 'CTK-Configure'
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
> 2>-- Generated:
> C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
> 2>-- CTKCore: BFD support disabled
> 2>-- Configuring done
> 2>-- Generating done
> 2>CMake Warning:
> 2>  Manually-specified variables were not used by the project:
> 2>    CTEST_USE_LAUNCHERS
> 2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
> 2>    DOCUMENTATION_TARGET_IN_ALL
> 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
> 2>No build step for 'CTK-Configure'
> 2>No install step for 'CTK-Configure'
> 2>Completed 'CTK-Configure'
> 2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
> 2>CTK-Configure - 0 error(s), 0 warning(s)
> 3>------ Build started: Project: CTK-build, Configuration: Debug Win32
> ------
> 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 3>Copyright (C) Microsoft Corp. All rights reserved.
> 3>1>------ Build started: Project: CTKVisualizationVTKWidgets,
> Configuration: Debug Win32 ------
> 3>1>Compiling...
> 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug
> Win32 ------
> 3>2>Linking...
> 3>1>ctkVTKScalarsToColorsView.cpp
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU
> @@UAE?AVOFCondition@@E at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU
> @@UAE?AVOFCondition@@XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@
> @UAE at XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)"
> (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)"
> (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: class OFCondition __thiscall
> ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class
> OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU
> @@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString
> @@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
> (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const
> &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in
> function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
> referenced in function _main
> 3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal
> error LNK1120: 9 unresolved externals
> 3>2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
> 3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
> : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f
> &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to
> 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
> : error C2664: 'void
> vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot
> convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
> 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
> 3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins,
> Configuration: Debug Win32 ------
> 3>3>Linking...
> 3>3>LINK : fatal error LNK1104: cannot open file
> '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
> 3>3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
> 3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
> 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped
> ==========
> 3>Project : error PRJ0019: A tool returned an error code from
> 3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
> 3>CTK-build - 14 error(s), 0 warning(s)
> ========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========
>
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org<http://e.mail.ru/cgi-bin/sentmsg?compose&To=Ctk-developers at commontk.org>
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111205/a2579eb1/attachment.htm>

From looky12 at bk.ru  Tue Dec  6 01:19:31 2011
From: looky12 at bk.ru (=?UTF-8?B?bG9va3kxMiBsb29reTEy?=)
Date: Tue, 06 Dec 2011 05:19:31 +0400
Subject: [Ctk-developers]
 =?utf-8?q?ctkDICOMDemoSCUMain=2Eobj_=3A_error_LN?= =?utf-8?q?K2019?=
In-Reply-To: <CAOFd4xA6R6jk1foQ-nBAhCba9UwpoFNmmcuG7N2-ecgyFNkVg@mail.gmail.com>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CAOFd4xA6R6jk1foQ-nBAhCba9UwpoFNmmcuG7N2-ecgyFNkVg@mail.gmail.com>
Message-ID: <E1RXjgx-0003fs-00.looky12-bk-ru@f248.mail.ru>

Hello Steve, thanks for your notice

At first i attempt too build ctk-cuperbuild, but not all projects (vtk, dcmtk, etc)? correctly checkouts at once, and i manually select " build current project" .? Then if all packages checkouts and builds, but error still exist, i open package dirictory with errors and trying to rebuild it.

06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net>:
 
  
  
Hi Oleg - 

Sorry - I wasn't clear - it's not your English :)

I meant that because the superbuild (top) level of the ctk cmake process does checkouts and builds of several other packages (vtk, dcmtk, etc) I wondered if one of those external projects was out of data or didn't build correctly.? If you tried to build the packages by hand that might explain the issue - typically for ctk we would just configure the ctk superbuild level and let it take care of the dependencies.

Hope that makes more sense,
-Steve



On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru> wrote:
If i turn off only VTK in this configuration, all other projects builds.? "Makes me wonder if somehow your build isn't up to date" - sorry but i think i understand this not correctly, maybe because i attempt build projects separately at first, and then all solution. 

Sorry for my English
Oleg.


01?Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net>:
 
 
 
Hi - 

Looks like you are also getting build errors related to ctkVTK -- makes me wonder if somehow your build isn't up to date. If you turn off dicom and vtk does everything else build?

-Steve

On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
Hello everyone, i have some problems in build process, thanks for your attention.

1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
1>Performing update step (git fetch) for 'qxmlrpc'
 1>Performing configure step for 'qxmlrpc'
1>-- Configuring done
1>-- Generating done
1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
1>Performing build step for 'qxmlrpc'
 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
1>Copyright (C) Microsoft Corp. All rights reserved.
1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped ==========
1>No install step for 'qxmlrpc'
 1>Completed 'qxmlrpc'
1>Build log was saved at "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
1>qxmlrpc - 0 error(s), 0 warning(s)
2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32 ------
 2>Performing configure step for 'CTK-Configure'
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
2>-- CTKCore: BFD support disabled
2>-- Configuring done
2>-- Generating done
 2>CMake Warning:
2>? Manually-specified variables were not used by the project:
2>??? CTEST_USE_LAUNCHERS
2>??? DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
2>??? DOCUMENTATION_TARGET_IN_ALL
2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
 2>No build step for 'CTK-Configure'
2>No install step for 'CTK-Configure'
2>Completed 'CTK-Configure'
2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
 2>CTK-Configure - 0 error(s), 0 warning(s)
3>------ Build started: Project: CTK-build, Configuration: Debug Win32 ------
3>Microsoft (R) Visual Studio Version 9.0.30729.1.
3>Copyright (C) Microsoft Corp. All rights reserved.
 3>1>------ Build started: Project: CTKVisualizationVTKWidgets, Configuration: Debug Win32 ------
3>1>Compiling...
3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug Win32 ------
 3>2>Linking...
3>1>ctkVTKScalarsToColorsView.cpp
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@@UAE at XZ) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)" (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)" (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: class OFCondition __thiscall ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU@@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString@@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)" (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function _main
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ) referenced in function _main
3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal error LNK1120: 9 unresolved externals
 3>2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596) : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
 3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606) : error C2664: 'void vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
 3>1>??????? Conversion from integral type to pointer type requires reinterpret_cast, C-style cast or function-style cast
3>1>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins, Configuration: Debug Win32 ------
3>3>Linking...
3>3>LINK : fatal error LNK1104: cannot open file '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
 3>3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped ==========
3>Project : error PRJ0019: A tool returned an error code from 
3>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
 3>CTK-build - 14 error(s), 0 warning(s)
========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========



_______________________________________________
Ctk-developers mailing list
Ctk-developers at commontk.org
http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers


  

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111206/c6809115/attachment.htm>

From domibel at debian.org  Tue Dec  6 02:09:26 2011
From: domibel at debian.org (Dominique Belhachemi)
Date: Mon, 5 Dec 2011 21:09:26 -0500
Subject: [Ctk-developers] CTK tag
Message-ID: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>

Hi,

I was wondering whether it is possible to create a tag for CTK.

More and more people are using ctk and it would be good to have
something like a pre-release. What do you thing about tagging the ctk
version Slicer 4 is using?

Thanks
-Dominique


From m.nolden at dkfz-heidelberg.de  Tue Dec  6 12:46:37 2011
From: m.nolden at dkfz-heidelberg.de (Marco Nolden)
Date: Tue, 06 Dec 2011 13:46:37 +0100
Subject: [Ctk-developers] CTK tag
In-Reply-To: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
Message-ID: <4EDE0EAD.4030401@dkfz.de>

Hi Dominique,

tagging is a really good idea, we already started discussions about this 
at the recent hackfest.

Would you use this tag as a basis for the Debian packaging? As far as I 
know the Debian packaging procedure it will take some time till this 
really gets accepted in "unstable". What is the timeframe that you 
expect? Would you update CTK to a more recent version before entering 
"unstable"? I'm asking because we're also planning a debian package for 
MITK and we would at least need some fixes from the most recent version 
of CTK.
Another option would be to apply some fixes on the Slicer 4 version and 
create a dedicated ctk-for-debian release branch on Github and discuss 
the fixes to put in there.

Best
Marco




On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
> Hi,
>
> I was wondering whether it is possible to create a tag for CTK.
>
> More and more people are using ctk and it would be good to have
> something like a pre-release. What do you thing about tagging the ctk
> version Slicer 4 is using?
>
> Thanks
> -Dominique
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers


-- 
----------------------------------------------------------------------
Dipl.-Inform. Med. Marco Nolden
Deutsches Krebsforschungszentrum       (German Cancer Research Center)
Div. Medical & Biological Informatics          Tel: (+49) 6221-42 2325
Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de


From pieper at ibility.net  Tue Dec  6 15:19:32 2011
From: pieper at ibility.net (Steve Pieper)
Date: Tue, 6 Dec 2011 10:19:32 -0500
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <E1RXjgx-0003fs-00.looky12-bk-ru@f248.mail.ru>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CAOFd4xA6R6jk1foQ-nBAhCba9UwpoFNmmcuG7N2-ecgyFNkVg@mail.gmail.com>
	<E1RXjgx-0003fs-00.looky12-bk-ru@f248.mail.ru>
Message-ID: <CA+OFd4xY3zCv2NnU=KKeGat2F_htpq2miaOCyoVjHWnFYr4rFg@mail.gmail.com>

Maybe someone else on the ctk list has ideas - I've been building ctk on
linux from within slicer4 and it's working fine but I haven't tried windows
lately - has anyone else?

-teve

On Mon, Dec 5, 2011 at 8:19 PM, looky12 looky12 <looky12 at bk.ru> wrote:

> Hello Steve, thanks for your notice
>
> At first i attempt too build ctk-cuperbuild, but not all projects (vtk,
> dcmtk, etc)  correctly checkouts at once, and i manually select " build
> current project" .  Then if all packages checkouts and builds, but error
> still exist, i open package dirictory with errors and trying to rebuild it.
>
> 06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net>:
>
>  Hi Oleg -
>
> Sorry - I wasn't clear - it's not your English :)
>
> I meant that because the superbuild (top) level of the ctk cmake process
> does checkouts and builds of several other packages (vtk, dcmtk, etc) I
> wondered if one of those external projects was out of data or didn't build
> correctly.  If you tried to build the packages by hand that might explain
> the issue - typically for ctk we would just configure the ctk superbuild
> level and let it take care of the dependencies.
>
> Hope that makes more sense,
> -Steve
>
>
>
> On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru<http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>
> > wrote:
>
> If i turn off only VTK in this configuration, all other projects builds.
> "Makes me wonder if somehow your build isn't up to date" - sorry but i
> think i understand this not correctly, maybe because i attempt build
> projects separately at first, and then all solution**.
>
> Sorry for my English
> Oleg.
>
>
> 01 Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net<http://e.mail.ru/cgi-bin/sentmsg?compose&To=pieper at ibility.net>
> >:
>
>   Hi -
>
> Looks like you are also getting build errors related to ctkVTK -- makes me
> wonder if somehow your build isn't up to date. If you turn off dicom and
> vtk does everything else build?
>
> -Steve
>
> On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru<http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>
> > wrote:
>
>  Hello everyone, i have some problems in build process, thanks for your
> attention.
>
> 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
> 1>Performing update step (git fetch) for 'qxmlrpc'
> 1>Performing configure step for 'qxmlrpc'
> 1>-- Configuring done
> 1>-- Generating done
> 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
> 1>Performing build step for 'qxmlrpc'
> 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 1>Copyright (C) Microsoft Corp. All rights reserved.
> 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped
> ==========
> 1>No install step for 'qxmlrpc'
> 1>Completed 'qxmlrpc'
> 1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
> 1>qxmlrpc - 0 error(s), 0 warning(s)
> 2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32
> ------
> 2>Performing configure step for 'CTK-Configure'
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
> 2>-- Generated:
> C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
> 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
> 2>-- CTKCore: BFD support disabled
> 2>-- Configuring done
> 2>-- Generating done
> 2>CMake Warning:
> 2>  Manually-specified variables were not used by the project:
> 2>    CTEST_USE_LAUNCHERS
> 2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
> 2>    DOCUMENTATION_TARGET_IN_ALL
> 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
> 2>No build step for 'CTK-Configure'
> 2>No install step for 'CTK-Configure'
> 2>Completed 'CTK-Configure'
> 2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
> 2>CTK-Configure - 0 error(s), 0 warning(s)
> 3>------ Build started: Project: CTK-build, Configuration: Debug Win32
> ------
> 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
> 3>Copyright (C) Microsoft Corp. All rights reserved.
> 3>1>------ Build started: Project: CTKVisualizationVTKWidgets,
> Configuration: Debug Win32 ------
> 3>1>Compiling...
> 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug
> Win32 ------
> 3>2>Linking...
> 3>1>ctkVTKScalarsToColorsView.cpp
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU
> @@UAE?AVOFCondition@@E at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall
> ctkDcmSCU::negotiateAssociation(void)" (?negotiateAssociation at ctkDcmSCU
> @@UAE?AVOFCondition@@XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual __thiscall ctkDcmSCU::~ctkDcmSCU(void)" (??1ctkDcmSCU@
> @UAE at XZ) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: virtual class OFCondition __thiscall ctkDcmSCU::initNetwork(void)"
> (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerAETitle(class OFString const &)"
> (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in function
> _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: class OFCondition __thiscall
> ctkDcmSCU::addPresentationContext(class OFString const &,class OFList<class
> OFString> const &,enum T_ASC_SC_ROLE)" (?addPresentationContext at ctkDcmSCU
> @@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString
> @@@@W4T_ASC_SC_ROLE@@@Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
> (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: void __thiscall ctkDcmSCU::setPeerHostName(class OFString const
> &)" (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z) referenced in
> function _main
> 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol
> "public: __thiscall ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
> referenced in function _main
> 3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe : fatal
> error LNK1120: 9 unresolved externals
> 3>2>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
> 3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
> : error C2664: 'void vtkControlPointsItem::MovePoints(const vtkVector2f
> &,vtkIdTypeArray *)' : cannot convert parameter 2 from 'bool' to
> 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
> : error C2664: 'void
> vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray *)' : cannot
> convert parameter 2 from 'bool' to 'vtkIdTypeArray *'
> 3>1>        Conversion from integral type to pointer type requires
> reinterpret_cast, C-style cast or function-style cast
> 3>1>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
> 3>1>CTKVisualizationVTKWidgets - 2 error(s), 0 warning(s)
> 3>3>------ Build started: Project: CTKVisualizationVTKWidgetsPlugins,
> Configuration: Debug Win32 ------
> 3>3>Linking...
> 3>3>LINK : fatal error LNK1104: cannot open file
> '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
> 3>3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
> 3>3>CTKVisualizationVTKWidgetsPlugins - 1 error(s), 0 warning(s)
> 3>========== Build: 0 succeeded, 3 failed, 29 up-to-date, 0 skipped
> ==========
> 3>Project : error PRJ0019: A tool returned an error code from
> 3>Build log was saved at
> "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
> 3>CTK-build - 14 error(s), 0 warning(s)
> ========== Build: 2 succeeded, 1 failed, 5 up-to-date, 0 skipped ==========
>
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org<http://e.mail.ru/cgi-bin/sentmsg?compose&To=Ctk-developers at commontk.org>
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111206/86023b00/attachment.htm>

From domibel at debian.org  Tue Dec  6 16:05:53 2011
From: domibel at debian.org (Dominique Belhachemi)
Date: Tue, 6 Dec 2011 11:05:53 -0500
Subject: [Ctk-developers] CTK tag
In-Reply-To: <4EDE0EAD.4030401@dkfz.de>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
Message-ID: <CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>

Hi Marco,

Yes, I would use the tagged version for Debian. I just need something
what can be considered as "stable enough".

CTK has already been accepted in 'experimental' back in July
(http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
the upload to 'unstable' would take only a couple of minutes.

Don't worry about MITK, we can always update the package in 'unstable'.

Additionally to creating the tag I would like to see a bump in the soname.
Updating the MINOR value would be the correct thing to do because I am
sure that the ABI/API changed a lot.
-set(CTK_MINOR_VERSION 1)
+set(CTK_MINOR_VERSION 2)

But if this is not possible, updating the PATCH value would help as well.
-set(CTK_PATCH_VERSION 0)
+set(CTK_PATCH_VERSION 1)

Thanks
-Dominique

On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
<m.nolden at dkfz-heidelberg.de> wrote:
> Hi Dominique,
>
> tagging is a really good idea, we already started discussions about this at
> the recent hackfest.
>
> Would you use this tag as a basis for the Debian packaging? As far as I know
> the Debian packaging procedure it will take some time till this really gets
> accepted in "unstable". What is the timeframe that you expect? Would you
> update CTK to a more recent version before entering "unstable"? I'm asking
> because we're also planning a debian package for MITK and we would at least
> need some fixes from the most recent version of CTK.
> Another option would be to apply some fixes on the Slicer 4 version and
> create a dedicated ctk-for-debian release branch on Github and discuss the
> fixes to put in there.
>
> Best
> Marco
>
>
>
>
>
> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>
>> Hi,
>>
>> I was wondering whether it is possible to create a tag for CTK.
>>
>> More and more people are using ctk and it would be good to have
>> something like a pre-release. What do you thing about tagging the ctk
>> version Slicer 4 is using?
>>
>> Thanks
>> -Dominique
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
>
> --
> ----------------------------------------------------------------------
> Dipl.-Inform. Med. Marco Nolden
> Deutsches Krebsforschungszentrum ? ? ? (German Cancer Research Center)
> Div. Medical & Biological Informatics ? ? ? ? ?Tel: (+49) 6221-42 2325
> Im Neuenheimer Feld 280 ? ? ? ? ? ? ? ? ? ? ? ?Fax: (+49) 6221-42 2345
> D-69120 Heidelberg ? ? ? ? ? ? ? ? ? ? ? ? ? ? eMail: M.Nolden at dkfz.de


From m.nolden at dkfz-heidelberg.de  Tue Dec  6 16:55:34 2011
From: m.nolden at dkfz-heidelberg.de (Marco Nolden)
Date: Tue, 06 Dec 2011 17:55:34 +0100
Subject: [Ctk-developers] CTK tag
In-Reply-To: <CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
	<CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
Message-ID: <4EDE4906.2030807@dkfz.de>

On 12/06/2011 05:05 PM, Dominique Belhachemi wrote:
> Hi Marco,
>
> Yes, I would use the tagged version for Debian. I just need something
> what can be considered as "stable enough".
>
> CTK has already been accepted in 'experimental' back in July
> (http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
> the upload to 'unstable' would take only a couple of minutes.

Hi Dominique,

that's nice. I wasn't sure if there is some extra step/validation 
necessary to get from experimental to unstable.
>
> Don't worry about MITK, we can always update the package in 'unstable'.
>

Thanks.


> Additionally to creating the tag I would like to see a bump in the soname.
> Updating the MINOR value would be the correct thing to do because I am
> sure that the ABI/API changed a lot.
> -set(CTK_MINOR_VERSION 1)
> +set(CTK_MINOR_VERSION 2)
>
> But if this is not possible, updating the PATCH value would help as well.
> -set(CTK_PATCH_VERSION 0)
> +set(CTK_PATCH_VERSION 1)
>

Yes, the ABI/API has changed a lot. Changing the version number should 
be easy, I just don't know which hash is currently referenced in Slicer 
4. We should create a branch based on that hash, add the version bump 
and tag it v0.2.0. I added an issue to github: 
https://github.com/commontk/CTK/issues/117

Best
Marco


> Thanks
> -Dominique
>
> On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
> <m.nolden at dkfz-heidelberg.de>  wrote:
>> Hi Dominique,
>>
>> tagging is a really good idea, we already started discussions about this at
>> the recent hackfest.
>>
>> Would you use this tag as a basis for the Debian packaging? As far as I know
>> the Debian packaging procedure it will take some time till this really gets
>> accepted in "unstable". What is the timeframe that you expect? Would you
>> update CTK to a more recent version before entering "unstable"? I'm asking
>> because we're also planning a debian package for MITK and we would at least
>> need some fixes from the most recent version of CTK.
>> Another option would be to apply some fixes on the Slicer 4 version and
>> create a dedicated ctk-for-debian release branch on Github and discuss the
>> fixes to put in there.
>>
>> Best
>> Marco
>>
>>
>>
>>
>>
>> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>>
>>> Hi,
>>>
>>> I was wondering whether it is possible to create a tag for CTK.
>>>
>>> More and more people are using ctk and it would be good to have
>>> something like a pre-release. What do you thing about tagging the ctk
>>> version Slicer 4 is using?
>>>
>>> Thanks
>>> -Dominique
>>> _______________________________________________
>>> Ctk-developers mailing list
>>> Ctk-developers at commontk.org
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>>
>>
>> --
>> ----------------------------------------------------------------------
>> Dipl.-Inform. Med. Marco Nolden
>> Deutsches Krebsforschungszentrum       (German Cancer Research Center)
>> Div. Medical&  Biological Informatics          Tel: (+49) 6221-42 2325
>> Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
>> D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers


-- 
----------------------------------------------------------------------
Dipl.-Inform. Med. Marco Nolden
Deutsches Krebsforschungszentrum       (German Cancer Research Center)
Div. Medical & Biological Informatics          Tel: (+49) 6221-42 2325
Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de


From s.zelzer at dkfz-heidelberg.de  Tue Dec  6 17:06:02 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Tue, 06 Dec 2011 18:06:02 +0100
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <CA+OFd4xY3zCv2NnU=KKeGat2F_htpq2miaOCyoVjHWnFYr4rFg@mail.gmail.com>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<E1RW9VW-0001D3-00.looky12-bk-ru@f60.mail.ru>
	<CAOFd4xA6R6jk1foQ-nBAhCba9UwpoFNmmcuG7N2-ecgyFNkVg@mail.gmail.com>
	<E1RXjgx-0003fs-00.looky12-bk-ru@f248.mail.ru>
	<CA+OFd4xY3zCv2NnU=KKeGat2F_htpq2miaOCyoVjHWnFYr4rFg@mail.gmail.com>
Message-ID: <4EDE4B7A.4050409@dkfz-heidelberg.de>

We regularly build CTK under Windows (superbuild) but not the 
ctkDICOMDemoSCUMain.cpp (I think).

What Visual Studio version are you using and which build options of CTK 
did you change?

- Sascha

On 12/06/2011 04:19 PM, Steve Pieper wrote:
> Maybe someone else on the ctk list has ideas - I've been building ctk 
> on linux from within slicer4 and it's working fine but I haven't tried 
> windows lately - has anyone else?
>
> -teve
>
> On Mon, Dec 5, 2011 at 8:19 PM, looky12 looky12 <looky12 at bk.ru 
> <mailto:looky12 at bk.ru>> wrote:
>
>     Hello Steve, thanks for your notice
>
>     At first i attempt too build ctk-cuperbuild, but not all projects
>     (vtk, dcmtk, etc)  correctly checkouts at once, and i manually
>     select " build current project" .  Then if all packages checkouts
>     and builds, but error still exist, i open package dirictory with
>     errors and trying to rebuild it.
>
>     06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net
>     <mailto:pieper at ibility.net>>:
>
>         Hi Oleg -
>
>         Sorry - I wasn't clear - it's not your English :)
>
>         I meant that because the superbuild (top) level of the ctk
>         cmake process does checkouts and builds of several other
>         packages (vtk, dcmtk, etc) I wondered if one of those external
>         projects was out of data or didn't build correctly.  If you
>         tried to build the packages by hand that might explain the
>         issue - typically for ctk we would just configure the ctk
>         superbuild level and let it take care of the dependencies.
>
>         Hope that makes more sense,
>         -Steve
>
>
>
>         On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru
>         <http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>>
>         wrote:
>
>             If i turn off only VTK in this configuration, all other
>             projects builds.  "Makes me wonder if somehow your build
>             isn't up to date" - sorry but i think i understand this
>             not correctly, maybe because i attempt build projects
>             separately at first, and then all solution.
>
>             Sorry for my English
>             Oleg.
>
>
>             01 Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net
>             <http://e.mail.ru/cgi-bin/sentmsg?compose&To=pieper at ibility.net>>:
>
>                 Hi -
>
>                 Looks like you are also getting build errors related
>                 to ctkVTK -- makes me wonder if somehow your build
>                 isn't up to date. If you turn off dicom and vtk does
>                 everything else build?
>
>                 -Steve
>
>                 On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12
>                 <looky12 at bk.ru
>                 <http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>>
>                 wrote:
>
>                     Hello everyone, i have some problems in build
>                     process, thanks for your attention.
>
>                     1>------ Build started: Project: qxmlrpc,
>                     Configuration: Debug Win32 ------
>                     1>Performing update step (git fetch) for 'qxmlrpc'
>                     1>Performing configure step for 'qxmlrpc'
>                     1>-- Configuring done
>                     1>-- Generating done
>                     1>-- Build files have been written to:
>                     C:/CTK/CTK-superbuild/qxmlrpc-build
>                     1>Performing build step for 'qxmlrpc'
>                     1>Microsoft (R) Visual Studio Version 9.0.30729.1.
>                     1>Copyright (C) Microsoft Corp. All rights reserved.
>                     1>========== Build: 0 succeeded, 0 failed, 3
>                     up-to-date, 0 skipped ==========
>                     1>No install step for 'qxmlrpc'
>                     1>Completed 'qxmlrpc'
>                     1>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
>                     1>qxmlrpc - 0 error(s), 0 warning(s)
>                     2>------ Build started: Project: CTK-Configure,
>                     Configuration: Debug Win32 ------
>                     2>Performing configure step for 'CTK-Configure'
>                     2>-- Generated:
>                     C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
>                     2>-- Generated:
>                     C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
>                     2>-- Generated:
>                     C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
>                     2>-- Generated:
>                     C:/CTK/CTK-superbuild/CTK-build/Project.xml
>                     2>-- CTKCore: BFD support disabled
>                     2>-- Configuring done
>                     2>-- Generating done
>                     2>CMake Warning:
>                     2>  Manually-specified variables were not used by
>                     the project:
>                     2>    CTEST_USE_LAUNCHERS
>                     2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
>                     2>    DOCUMENTATION_TARGET_IN_ALL
>                     2>-- Build files have been written to:
>                     C:/CTK/CTK-superbuild/CTK-build
>                     2>No build step for 'CTK-Configure'
>                     2>No install step for 'CTK-Configure'
>                     2>Completed 'CTK-Configure'
>                     2>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
>                     2>CTK-Configure - 0 error(s), 0 warning(s)
>                     3>------ Build started: Project: CTK-build,
>                     Configuration: Debug Win32 ------
>                     3>Microsoft (R) Visual Studio Version 9.0.30729.1.
>                     3>Copyright (C) Microsoft Corp. All rights reserved.
>                     3>1>------ Build started: Project:
>                     CTKVisualizationVTKWidgets, Configuration: Debug
>                     Win32 ------
>                     3>1>Compiling...
>                     3>2>------ Build started: Project:
>                     ctkDICOMDemoSCU, Configuration: Debug Win32 ------
>                     3>2>Linking...
>                     3>1>ctkVTKScalarsToColorsView.cpp
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: virtual class
>                     OFCondition __thiscall
>                     ctkDcmSCU::sendECHORequest(unsigned char)"
>                     (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: virtual class
>                     OFCondition __thiscall
>                     ctkDcmSCU::negotiateAssociation(void)"
>                     (?negotiateAssociation at ctkDcmSCU@@UAE?AVOFCondition@@XZ)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: virtual
>                     __thiscall ctkDcmSCU::~ctkDcmSCU(void)"
>                     (??1ctkDcmSCU@@UAE at XZ) referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: virtual class
>                     OFCondition __thiscall
>                     ctkDcmSCU::initNetwork(void)"
>                     (?initNetwork at ctkDcmSCU@@UAE?AVOFCondition@@XZ)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: void
>                     __thiscall ctkDcmSCU::setPeerAETitle(class
>                     OFString const &)"
>                     (?setPeerAETitle at ctkDcmSCU@@QAEXABVOFString@@@Z)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: class
>                     OFCondition __thiscall
>                     ctkDcmSCU::addPresentationContext(class OFString
>                     const &,class OFList<class OFString> const &,enum
>                     T_ASC_SC_ROLE)"
>                     (?addPresentationContext at ctkDcmSCU@@QAE?AVOFCondition@@ABVOFString@@ABV?$OFList at VOFString@@@@W4T_ASC_SC_ROLE@@@Z)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: void
>                     __thiscall ctkDcmSCU::setPeerPort(unsigned short)"
>                     (?setPeerPort at ctkDcmSCU@@QAEXG at Z) referenced in
>                     function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: void
>                     __thiscall ctkDcmSCU::setPeerHostName(class
>                     OFString const &)"
>                     (?setPeerHostName at ctkDcmSCU@@QAEXABVOFString@@@Z)
>                     referenced in function _main
>                     3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>                     unresolved external symbol "public: __thiscall
>                     ctkDcmSCU::ctkDcmSCU(void)" (??0ctkDcmSCU@@QAE at XZ)
>                     referenced in function _main
>                     3>2>C:\CTK\CTK-superbuild\CTK-build\bin\Debug\ctkDICOMDemoSCU.exe
>                     : fatal error LNK1120: 9 unresolved externals
>                     3>2>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\CTK-build\Applications\ctkDICOMDemoSCU\ctkDICOMDemoSCU.dir\Debug\BuildLog.htm"
>                     3>2>ctkDICOMDemoSCU - 10 error(s), 0 warning(s)
>                     3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(596)
>                     : error C2664: 'void
>                     vtkControlPointsItem::MovePoints(const vtkVector2f
>                     &,vtkIdTypeArray *)' : cannot convert parameter 2
>                     from 'bool' to 'vtkIdTypeArray *'
>                     3>1>        Conversion from integral type to
>                     pointer type requires reinterpret_cast, C-style
>                     cast or function-style cast
>                     3>1>..\..\..\..\..\..\Libs\Visualization\VTK\Widgets\ctkVTKScalarsToColorsView.cpp(606)
>                     : error C2664: 'void
>                     vtkControlPointsItem::SpreadPoints(float,vtkIdTypeArray
>                     *)' : cannot convert parameter 2 from 'bool' to
>                     'vtkIdTypeArray *'
>                     3>1>        Conversion from integral type to
>                     pointer type requires reinterpret_cast, C-style
>                     cast or function-style cast
>                     3>1>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\CTKVisualizationVTKWidgets.dir\Debug\BuildLog.htm"
>                     3>1>CTKVisualizationVTKWidgets - 2 error(s), 0
>                     warning(s)
>                     3>3>------ Build started: Project:
>                     CTKVisualizationVTKWidgetsPlugins, Configuration:
>                     Debug Win32 ------
>                     3>3>Linking...
>                     3>3>LINK : fatal error LNK1104: cannot open file
>                     '..\..\..\..\..\bin\Debug\CTKVisualizationVTKWidgets.lib'
>                     3>3>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\CTK-build\Libs\Visualization\VTK\Widgets\Plugins\CTKVisualizationVTKWidgetsPlugins.dir\Debug\BuildLog.htm"
>                     3>3>CTKVisualizationVTKWidgetsPlugins - 1
>                     error(s), 0 warning(s)
>                     3>========== Build: 0 succeeded, 3 failed, 29
>                     up-to-date, 0 skipped ==========
>                     3>Project : error PRJ0019: A tool returned an
>                     error code from
>                     3>Build log was saved at
>                     "file://c:\CTK\CTK-superbuild\CTK-build.dir\Debug\BuildLog.htm"
>                     3>CTK-build - 14 error(s), 0 warning(s)
>                     ========== Build: 2 succeeded, 1 failed, 5
>                     up-to-date, 0 skipped ==========
>
>
>
>                     _______________________________________________
>                     Ctk-developers mailing list
>                     Ctk-developers at commontk.org
>                     <http://e.mail.ru/cgi-bin/sentmsg?compose&To=Ctk-developers at commontk.org>
>                     http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111206/765a9083/attachment.htm>

From s.zelzer at dkfz-heidelberg.de  Tue Dec  6 19:50:22 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Tue, 06 Dec 2011 20:50:22 +0100
Subject: [Ctk-developers] CTK tag
In-Reply-To: <CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
	<CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
Message-ID: <4EDE71FE.6030501@dkfz-heidelberg.de>

Hi Dominique,

Thanks a lot for your efforts!

I am not experienced with Debian packages but I wonder what the actual 
set of libraries for such a CTK package would be. And how do the library 
versions relate to the package version? Shouldn't we package each 
library separately, or are those questions irrelevant for Debian unstable?

I am also not sure if bumping the minor version is enough, especially if 
we look at the libraries as a whole. We had discussions about versioning 
of our libraries and having a global major/minor/patch set for all CTK 
versions is certainly not adequate. But maybe people do not care that 
much regarding Debian unstable...

Sorry for the brain dump,

Sascha

On 12/06/2011 05:05 PM, Dominique Belhachemi wrote:
> Hi Marco,
>
> Yes, I would use the tagged version for Debian. I just need something
> what can be considered as "stable enough".
>
> CTK has already been accepted in 'experimental' back in July
> (http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
> the upload to 'unstable' would take only a couple of minutes.
>
> Don't worry about MITK, we can always update the package in 'unstable'.
>
> Additionally to creating the tag I would like to see a bump in the soname.
> Updating the MINOR value would be the correct thing to do because I am
> sure that the ABI/API changed a lot.
> -set(CTK_MINOR_VERSION 1)
> +set(CTK_MINOR_VERSION 2)
>
> But if this is not possible, updating the PATCH value would help as well.
> -set(CTK_PATCH_VERSION 0)
> +set(CTK_PATCH_VERSION 1)
>
> Thanks
> -Dominique
>
> On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
> <m.nolden at dkfz-heidelberg.de>  wrote:
>> Hi Dominique,
>>
>> tagging is a really good idea, we already started discussions about this at
>> the recent hackfest.
>>
>> Would you use this tag as a basis for the Debian packaging? As far as I know
>> the Debian packaging procedure it will take some time till this really gets
>> accepted in "unstable". What is the timeframe that you expect? Would you
>> update CTK to a more recent version before entering "unstable"? I'm asking
>> because we're also planning a debian package for MITK and we would at least
>> need some fixes from the most recent version of CTK.
>> Another option would be to apply some fixes on the Slicer 4 version and
>> create a dedicated ctk-for-debian release branch on Github and discuss the
>> fixes to put in there.
>>
>> Best
>> Marco
>>
>>
>>
>>
>>
>> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>> Hi,
>>>
>>> I was wondering whether it is possible to create a tag for CTK.
>>>
>>> More and more people are using ctk and it would be good to have
>>> something like a pre-release. What do you thing about tagging the ctk
>>> version Slicer 4 is using?
>>>
>>> Thanks
>>> -Dominique
>>> _______________________________________________
>>> Ctk-developers mailing list
>>> Ctk-developers at commontk.org
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>>
>> --
>> ----------------------------------------------------------------------
>> Dipl.-Inform. Med. Marco Nolden
>> Deutsches Krebsforschungszentrum       (German Cancer Research Center)
>> Div. Medical&  Biological Informatics          Tel: (+49) 6221-42 2325
>> Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
>> D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers



From domibel at debian.org  Tue Dec  6 22:43:25 2011
From: domibel at debian.org (Dominique Belhachemi)
Date: Tue, 6 Dec 2011 17:43:25 -0500
Subject: [Ctk-developers] CTK tag
In-Reply-To: <4EDE71FE.6030501@dkfz-heidelberg.de>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
	<CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
	<4EDE71FE.6030501@dkfz-heidelberg.de>
Message-ID: <CAAvaLCwHHEDCXBDeW+iBCXh_TVPr4Y0HGVSN4FddNbQLw_OcKw@mail.gmail.com>

Hi Sascha,

Moving each library in a separate package is possible but I wouldn't
want to do it. It is too much work.

Currently, CTK is using the same major/minor/patch number for each library.

$ ls CTK-build/bin/
libCTKCore.so      libCTKCore.so.0.1.0       libCTKPluginFramework.so.0.1
libCTKCore.so.0.1  libCTKPluginFramework.so  libCTKPluginFramework.so.0.1.0


The Debian package wouldn't change that. Please have a look at the
current package in 'experimental':
   http://packages.debian.org/experimental/amd64/libctk0.1/filelist

Thanks
-Dominique

P.S. Please not that "Ubuntu" = "Debian unstable + closed source
graphics driver" :)


On Tue, Dec 6, 2011 at 2:50 PM, Sascha Zelzer
<s.zelzer at dkfz-heidelberg.de> wrote:
> Hi Dominique,
>
> Thanks a lot for your efforts!
>
> I am not experienced with Debian packages but I wonder what the actual set
> of libraries for such a CTK package would be. And how do the library
> versions relate to the package version? Shouldn't we package each library
> separately, or are those questions irrelevant for Debian unstable?
>
> I am also not sure if bumping the minor version is enough, especially if we
> look at the libraries as a whole. We had discussions about versioning of our
> libraries and having a global major/minor/patch set for all CTK versions is
> certainly not adequate. But maybe people do not care that much regarding
> Debian unstable...
>
> Sorry for the brain dump,
>
> Sascha
>
>
> On 12/06/2011 05:05 PM, Dominique Belhachemi wrote:
>>
>> Hi Marco,
>>
>> Yes, I would use the tagged version for Debian. I just need something
>> what can be considered as "stable enough".
>>
>> CTK has already been accepted in 'experimental' back in July
>> (http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
>> the upload to 'unstable' would take only a couple of minutes.
>>
>> Don't worry about MITK, we can always update the package in 'unstable'.
>>
>> Additionally to creating the tag I would like to see a bump in the soname.
>> Updating the MINOR value would be the correct thing to do because I am
>> sure that the ABI/API changed a lot.
>> -set(CTK_MINOR_VERSION 1)
>> +set(CTK_MINOR_VERSION 2)
>>
>> But if this is not possible, updating the PATCH value would help as well.
>> -set(CTK_PATCH_VERSION 0)
>> +set(CTK_PATCH_VERSION 1)
>>
>> Thanks
>> -Dominique
>>
>> On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
>> <m.nolden at dkfz-heidelberg.de> ?wrote:
>>>
>>> Hi Dominique,
>>>
>>> tagging is a really good idea, we already started discussions about this
>>> at
>>> the recent hackfest.
>>>
>>> Would you use this tag as a basis for the Debian packaging? As far as I
>>> know
>>> the Debian packaging procedure it will take some time till this really
>>> gets
>>> accepted in "unstable". What is the timeframe that you expect? Would you
>>> update CTK to a more recent version before entering "unstable"? I'm
>>> asking
>>> because we're also planning a debian package for MITK and we would at
>>> least
>>> need some fixes from the most recent version of CTK.
>>> Another option would be to apply some fixes on the Slicer 4 version and
>>> create a dedicated ctk-for-debian release branch on Github and discuss
>>> the
>>> fixes to put in there.
>>>
>>> Best
>>> Marco
>>>
>>>
>>>
>>>
>>>
>>> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>>>
>>>> Hi,
>>>>
>>>> I was wondering whether it is possible to create a tag for CTK.
>>>>
>>>> More and more people are using ctk and it would be good to have
>>>> something like a pre-release. What do you thing about tagging the ctk
>>>> version Slicer 4 is using?
>>>>
>>>> Thanks
>>>> -Dominique
>>>> _______________________________________________
>>>> Ctk-developers mailing list
>>>> Ctk-developers at commontk.org
>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>
>>>
>>>
>>> --
>>> ----------------------------------------------------------------------
>>> Dipl.-Inform. Med. Marco Nolden
>>> Deutsches Krebsforschungszentrum ? ? ? (German Cancer Research Center)
>>> Div. Medical& ?Biological Informatics ? ? ? ? ?Tel: (+49) 6221-42 2325
>>>
>>> Im Neuenheimer Feld 280 ? ? ? ? ? ? ? ? ? ? ? ?Fax: (+49) 6221-42 2345
>>> D-69120 Heidelberg ? ? ? ? ? ? ? ? ? ? ? ? ? ? eMail: M.Nolden at dkfz.de
>>
>> _______________________________________________
>>
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>


From looky12 at bk.ru  Tue Dec  6 23:11:18 2011
From: looky12 at bk.ru (=?UTF-8?B?bG9va3kxMiBsb29reTEy?=)
Date: Wed, 07 Dec 2011 03:11:18 +0400
Subject: [Ctk-developers]
 =?utf-8?q?ctkDICOMDemoSCUMain=2Eobj_=3A_error_LN?= =?utf-8?q?K2019?=
In-Reply-To: <4EDE4B7A.4050409@dkfz-heidelberg.de>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<CA+OFd4xY3zCv2NnU=KKeGat2F_htpq2miaOCyoVjHWnFYr4rFg@mail.gmail.com>
	<4EDE4B7A.4050409@dkfz-heidelberg.de>
Message-ID: <E1RY4AQ-0002Sp-00.looky12-bk-ru@f250.mail.ru>


I use vs 2008 with QT addin. Attached archive contain ctk files of root directory (with ctk configuration i think).

06 ??????? 2011, 21:06 ?? Sascha Zelzer <s.zelzer at dkfz-heidelberg.de>:
 
  
  
 
 We regularly build CTK under Windows (superbuild) but not the ctkDICOMDemoSCUMain.cpp (I think).
 
 What Visual Studio version are you using and which build options of CTK did you change?
 
 - Sascha
 
 On 12/06/2011 04:19 PM, Steve Pieper wrote: Maybe someone else on the ctk list has ideas - I've been building ctk on linux from within slicer4 and it's working fine but I haven't tried windows lately - has anyone else?
 
 -teve
 
 
 On Mon, Dec 5, 2011 at 8:19 PM, looky12 looky12 <looky12 at bk.ru> wrote:
  
Hello Steve, thanks for your notice
 
 At first i attempt too build ctk-cuperbuild, but not all projects (vtk, dcmtk, etc)? correctly checkouts at once, and i manually select " build current project" .? Then if all packages checkouts and builds, but error still exist, i open package dirictory with errors and trying to rebuild it.
 
 06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net>:
  
 
 
 
 
Hi Oleg - 
 
 Sorry - I wasn't clear - it's not your English :)
 
 I meant that because the superbuild (top) level of the ctk cmake process does checkouts and builds of several other packages (vtk, dcmtk, etc) I wondered if one of those external projects was out of data or didn't build correctly.? If you tried to build the packages by hand that might explain the issue - typically for ctk we would just configure the ctk superbuild level and let it take care of the dependencies.
 
 Hope that makes more sense,
 -Steve
 
 
 
  
 
On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru> wrote:
   
 
If i turn off only VTK in this configuration, all other projects builds.? "Makes me wonder if somehow your build isn't up to date" - sorry but i think i understand this not correctly, maybe because i attempt build projects separately at first, and then all solution. 
 
 Sorry for my English
 Oleg.
 
 
 01?Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net>:
   
 
 
 
 
 
Hi - 
 
 Looks like you are also getting build errors related to ctkVTK -- makes me wonder if somehow your build isn't up to date. If you turn off dicom and vtk does everything else build?
 
 -Steve
 
   
 
 
 On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
    
 
 
 
 
Hello everyone, i have some problems in build process, thanks for your attention.
 
 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
 1>Performing update step (git fetch) for 'qxmlrpc'
 1>Performing configure step for 'qxmlrpc'
 1>-- Configuring done
 1>-- Generating done
 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
 1>Performing build step for 'qxmlrpc'
 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
 1>Copyright (C) Microsoft Corp. All rights reserved.
 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped ==========
 1>No install step for 'qxmlrpc'
 1>Completed 'qxmlrpc'
 1>Build log was saved at "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
 1>qxmlrpc - 0 error(s), 0 warning(s)
 2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32 ------
 2>Performing configure step for 'CTK-Configure'
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
 2>-- CTKCore: BFD support disabled
 2>-- Configuring done
 2>-- Generating done
 2>CMake Warning:
 2>? Manually-specified variables were not used by the project:
 2>??? CTEST_USE_LAUNCHERS
 2>??? DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
 2>??? DOCUMENTATION_TARGET_IN_ALL
 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
 2>No build step for 'CTK-Configure'
 2>No install step for 'CTK-Configure'
 2>Completed 'CTK-Configure'
 2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
 2>CTK-Configure - 0 error(s), 0 warning(s)
 3>------ Build started: Project: CTK-build, Configuration: Debug Win32 ------
 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
 3>Copyright (C) Microsoft Corp. All rights reserved.
 3>1>------ Build started: Project: CTKVisualizationVTKWidgets, Configuration: Debug Win32 ------
3>1>Compiling...
 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug Win32 ------
 3>2>Linking...
3>1>ctkVTKScalarsToColorsView.cpp
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z) referenced in function _main.........................................................................................................................

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111207/208fc322/attachment.htm>

From looky12 at bk.ru  Tue Dec  6 23:45:16 2011
From: looky12 at bk.ru (=?UTF-8?B?bG9va3kxMiBsb29reTEy?=)
Date: Wed, 07 Dec 2011 03:45:16 +0400
Subject: [Ctk-developers]
 =?utf-8?q?ctkDICOMDemoSCUMain=2Eobj_=3A_error_LN?= =?utf-8?q?K2019?=
In-Reply-To: <E1RY4AQ-0002Sp-00.looky12-bk-ru@f250.mail.ru>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<4EDE4B7A.4050409@dkfz-heidelberg.de>
	<E1RY4AQ-0002Sp-00.looky12-bk-ru@f250.mail.ru>
Message-ID: <E1RY4hI-0006V3-00.looky12-bk-ru@f268.mail.ru>

I been wrong, this is my configuration file.

07 ??????? 2011, 03:29 ?? looky12 looky12 <looky12 at bk.ru>:
 
  
  

I use vs 2008 with QT addin. Attached archive contain ctk files of root directory (with ctk configuration i think).

06 ??????? 2011, 21:06 ?? Sascha Zelzer <s.zelzer at dkfz-heidelberg.de>:
 
  
  
 
 We regularly build CTK under Windows (superbuild) but not the ctkDICOMDemoSCUMain.cpp (I think).
 
 What Visual Studio version are you using and which build options of CTK did you change?
 
 - Sascha
 
 On 12/06/2011 04:19 PM, Steve Pieper wrote: Maybe someone else on the ctk list has ideas - I've been building ctk on linux from within slicer4 and it's working fine but I haven't tried windows lately - has anyone else?
 
 -teve
 
 
 On Mon, Dec 5, 2011 at 8:19 PM, looky12 looky12 <looky12 at bk.ru> wrote:
  
Hello Steve, thanks for your notice
 
 At first i attempt too build ctk-cuperbuild, but not all projects (vtk, dcmtk, etc)? correctly checkouts at once, and i manually select " build current project" .? Then if all packages checkouts and builds, but error still exist, i open package dirictory with errors and trying to rebuild it.
 
 06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net>:
  
 
 
 
 
Hi Oleg - 
 
 Sorry - I wasn't clear - it's not your English :)
 
 I meant that because the superbuild (top) level of the ctk cmake process does checkouts and builds of several other packages (vtk, dcmtk, etc) I wondered if one of those external projects was out of data or didn't build correctly.? If you tried to build the packages by hand that might explain the issue - typically for ctk we would just configure the ctk superbuild level and let it take care of the dependencies.
 
 Hope that makes more sense,
 -Steve
 
 
 
  
 
On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12 <looky12 at bk.ru> wrote:
   
 
If i turn off only VTK in this configuration, all other projects builds.? "Makes me wonder if somehow your build isn't up to date" - sorry but i think i understand this not correctly, maybe because i attempt build projects separately at first, and then all solution. 
 
 Sorry for my English
 Oleg.
 
 
 01?Dec 2011, 23:11 ?? Steve Pieper <pieper at ibility.net>:
   
 
 
 
 
 
Hi - 
 
 Looks like you are also getting build errors related to ctkVTK -- makes me wonder if somehow your build isn't up to date. If you turn off dicom and vtk does everything else build?
 
 -Steve
 
   
 
 
 On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12 <looky12 at bk.ru> wrote:
    
 
 
 
 
Hello everyone, i have some problems in build process, thanks for your attention.
 
 1>------ Build started: Project: qxmlrpc, Configuration: Debug Win32 ------
 1>Performing update step (git fetch) for 'qxmlrpc'
 1>Performing configure step for 'qxmlrpc'
 1>-- Configuring done
 1>-- Generating done
 1>-- Build files have been written to: C:/CTK/CTK-superbuild/qxmlrpc-build
 1>Performing build step for 'qxmlrpc'
 1>Microsoft (R) Visual Studio Version 9.0.30729.1.
 1>Copyright (C) Microsoft Corp. All rights reserved.
 1>========== Build: 0 succeeded, 0 failed, 3 up-to-date, 0 skipped ==========
 1>No install step for 'qxmlrpc'
 1>Completed 'qxmlrpc'
 1>Build log was saved at "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
 1>qxmlrpc - 0 error(s), 0 warning(s)
 2>------ Build started: Project: CTK-Configure, Configuration: Debug Win32 ------
 2>Performing configure step for 'CTK-Configure'
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
 2>-- Generated: C:/CTK/CTK-superbuild/CTK-build/Project.xml
 2>-- CTKCore: BFD support disabled
 2>-- Configuring done
 2>-- Generating done
 2>CMake Warning:
 2>? Manually-specified variables were not used by the project:
 2>??? CTEST_USE_LAUNCHERS
 2>??? DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
 2>??? DOCUMENTATION_TARGET_IN_ALL
 2>-- Build files have been written to: C:/CTK/CTK-superbuild/CTK-build
 2>No build step for 'CTK-Configure'
 2>No install step for 'CTK-Configure'
 2>Completed 'CTK-Configure'
 2>Build log was saved at "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
 2>CTK-Configure - 0 error(s), 0 warning(s)
 3>------ Build started: Project: CTK-build, Configuration: Debug Win32 ------
 3>Microsoft (R) Visual Studio Version 9.0.30729.1.
 3>Copyright (C) Microsoft Corp. All rights reserved.
 3>1>------ Build started: Project: CTKVisualizationVTKWidgets, Configuration: Debug Win32 ------
3>1>Compiling...
 3>2>------ Build started: Project: ctkDICOMDemoSCU, Configuration: Debug Win32 ------
 3>2>Linking...
3>1>ctkVTKScalarsToColorsView.cpp
 3>2>ctkDICOMDemoSCUMain.obj : error LNK2019: unresolved external symbol "public: virtual class OFCondition __thiscall ctkDcmSCU::sendECHORequest(unsigned char)" (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z) referenced in function _main.........................................................................................................................

 
_______________________________________________
Ctk-developers mailing list
Ctk-developers at commontk.org
http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers

   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111207/ff504a91/attachment.htm>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CMakeCache.txt
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111207/ff504a91/attachment.txt>

From s.zelzer at dkfz-heidelberg.de  Wed Dec  7 21:41:56 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Wed, 07 Dec 2011 22:41:56 +0100
Subject: [Ctk-developers] CTK tag
In-Reply-To: <CAAvaLCwHHEDCXBDeW+iBCXh_TVPr4Y0HGVSN4FddNbQLw_OcKw@mail.gmail.com>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
	<CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
	<4EDE71FE.6030501@dkfz-heidelberg.de>
	<CAAvaLCwHHEDCXBDeW+iBCXh_TVPr4Y0HGVSN4FddNbQLw_OcKw@mail.gmail.com>
Message-ID: <4EDFDDA4.80405@dkfz-heidelberg.de>

Hi Dominique,

thanks for the P.S. ;-)

I was aware of the content of the libctk0.1 deb package and that is 
actually the main reason for all of my questions. Would it even be 
possible to have multiple libraries with different SO names in the same 
package?

Right now, if for example Slicer depends only on libCTKCore.so.0.1 and 
we create a new debian package and one of the other libraries requires a 
major version bump because of API incompatibility, wouldn't that mean 
that Slicer needs also to be repackaged (if the CTK package is upgraded 
on a system with also Slicer package installed)?

Maybe this is all too theoretical and we are not at a stage yet where 
those things matter...

Thanks,

Sascha

On 12/06/2011 11:43 PM, Dominique Belhachemi wrote:
> Hi Sascha,
>
> Moving each library in a separate package is possible but I wouldn't
> want to do it. It is too much work.
>
> Currently, CTK is using the same major/minor/patch number for each library.
>
> $ ls CTK-build/bin/
> libCTKCore.so      libCTKCore.so.0.1.0       libCTKPluginFramework.so.0.1
> libCTKCore.so.0.1  libCTKPluginFramework.so  libCTKPluginFramework.so.0.1.0
>
>
> The Debian package wouldn't change that. Please have a look at the
> current package in 'experimental':
>     http://packages.debian.org/experimental/amd64/libctk0.1/filelist
>
> Thanks
> -Dominique
>
> P.S. Please not that "Ubuntu" = "Debian unstable + closed source
> graphics driver" :)
>
>
> On Tue, Dec 6, 2011 at 2:50 PM, Sascha Zelzer
> <s.zelzer at dkfz-heidelberg.de>  wrote:
>> Hi Dominique,
>>
>> Thanks a lot for your efforts!
>>
>> I am not experienced with Debian packages but I wonder what the actual set
>> of libraries for such a CTK package would be. And how do the library
>> versions relate to the package version? Shouldn't we package each library
>> separately, or are those questions irrelevant for Debian unstable?
>>
>> I am also not sure if bumping the minor version is enough, especially if we
>> look at the libraries as a whole. We had discussions about versioning of our
>> libraries and having a global major/minor/patch set for all CTK versions is
>> certainly not adequate. But maybe people do not care that much regarding
>> Debian unstable...
>>
>> Sorry for the brain dump,
>>
>> Sascha
>>
>>
>> On 12/06/2011 05:05 PM, Dominique Belhachemi wrote:
>>> Hi Marco,
>>>
>>> Yes, I would use the tagged version for Debian. I just need something
>>> what can be considered as "stable enough".
>>>
>>> CTK has already been accepted in 'experimental' back in July
>>> (http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
>>> the upload to 'unstable' would take only a couple of minutes.
>>>
>>> Don't worry about MITK, we can always update the package in 'unstable'.
>>>
>>> Additionally to creating the tag I would like to see a bump in the soname.
>>> Updating the MINOR value would be the correct thing to do because I am
>>> sure that the ABI/API changed a lot.
>>> -set(CTK_MINOR_VERSION 1)
>>> +set(CTK_MINOR_VERSION 2)
>>>
>>> But if this is not possible, updating the PATCH value would help as well.
>>> -set(CTK_PATCH_VERSION 0)
>>> +set(CTK_PATCH_VERSION 1)
>>>
>>> Thanks
>>> -Dominique
>>>
>>> On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
>>> <m.nolden at dkfz-heidelberg.de>    wrote:
>>>> Hi Dominique,
>>>>
>>>> tagging is a really good idea, we already started discussions about this
>>>> at
>>>> the recent hackfest.
>>>>
>>>> Would you use this tag as a basis for the Debian packaging? As far as I
>>>> know
>>>> the Debian packaging procedure it will take some time till this really
>>>> gets
>>>> accepted in "unstable". What is the timeframe that you expect? Would you
>>>> update CTK to a more recent version before entering "unstable"? I'm
>>>> asking
>>>> because we're also planning a debian package for MITK and we would at
>>>> least
>>>> need some fixes from the most recent version of CTK.
>>>> Another option would be to apply some fixes on the Slicer 4 version and
>>>> create a dedicated ctk-for-debian release branch on Github and discuss
>>>> the
>>>> fixes to put in there.
>>>>
>>>> Best
>>>> Marco
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>>>> Hi,
>>>>>
>>>>> I was wondering whether it is possible to create a tag for CTK.
>>>>>
>>>>> More and more people are using ctk and it would be good to have
>>>>> something like a pre-release. What do you thing about tagging the ctk
>>>>> version Slicer 4 is using?
>>>>>
>>>>> Thanks
>>>>> -Dominique
>>>>> _______________________________________________
>>>>> Ctk-developers mailing list
>>>>> Ctk-developers at commontk.org
>>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>>
>>>>
>>>> --
>>>> ----------------------------------------------------------------------
>>>> Dipl.-Inform. Med. Marco Nolden
>>>> Deutsches Krebsforschungszentrum       (German Cancer Research Center)
>>>> Div. Medical&    Biological Informatics          Tel: (+49) 6221-42 2325
>>>>
>>>> Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
>>>> D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de
>>> _______________________________________________
>>>
>>> Ctk-developers mailing list
>>> Ctk-developers at commontk.org
>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers



From domibel at debian.org  Wed Dec  7 23:36:41 2011
From: domibel at debian.org (Dominique Belhachemi)
Date: Wed, 7 Dec 2011 18:36:41 -0500
Subject: [Ctk-developers] CTK tag
In-Reply-To: <4EDFDDA4.80405@dkfz-heidelberg.de>
References: <CAAvaLCwQGOWgSedEE9ROgOV=ODeYwZRjNm7=XO00jk+YTvZPNw@mail.gmail.com>
	<4EDE0EAD.4030401@dkfz.de>
	<CAAvaLCwTma90wBxh0wzNUawBp2B8u8sr8uzu5Jh56VVxt=12wA@mail.gmail.com>
	<4EDE71FE.6030501@dkfz-heidelberg.de>
	<CAAvaLCwHHEDCXBDeW+iBCXh_TVPr4Y0HGVSN4FddNbQLw_OcKw@mail.gmail.com>
	<4EDFDDA4.80405@dkfz-heidelberg.de>
Message-ID: <CAAvaLCzEhd03qnW=QTj_uHV1aPUny1dczcd6Ofac9xsGoiDwUA@mail.gmail.com>

Multiple SO names within CTK are possible.

Lets say we have the package libctk6 and it contains libCTKCore.so.0.1 .

If I bump libCTKCore.so.0.1 to libCTKCore.so.0.2 I would simply bump
libctk6 to libctk7. Slicer would still use libctk6. If I want Slicer
to use libctk7 then I would trigger a rebuild (without changing the
Slicer source package).

All you have to do is to tag a version.

-Dominique


On Wed, Dec 7, 2011 at 4:41 PM, Sascha Zelzer
<s.zelzer at dkfz-heidelberg.de> wrote:
> Hi Dominique,
>
> thanks for the P.S. ;-)
>
> I was aware of the content of the libctk0.1 deb package and that is actually
> the main reason for all of my questions. Would it even be possible to have
> multiple libraries with different SO names in the same package?
>
> Right now, if for example Slicer depends only on libCTKCore.so.0.1 and we
> create a new debian package and one of the other libraries requires a major
> version bump because of API incompatibility, wouldn't that mean that Slicer
> needs also to be repackaged (if the CTK package is upgraded on a system with
> also Slicer package installed)?
>
> Maybe this is all too theoretical and we are not at a stage yet where those
> things matter...
>
> Thanks,
>
> Sascha
>
>
> On 12/06/2011 11:43 PM, Dominique Belhachemi wrote:
>>
>> Hi Sascha,
>>
>> Moving each library in a separate package is possible but I wouldn't
>> want to do it. It is too much work.
>>
>> Currently, CTK is using the same major/minor/patch number for each
>> library.
>>
>> $ ls CTK-build/bin/
>> libCTKCore.so ? ? ?libCTKCore.so.0.1.0 ? ? ? libCTKPluginFramework.so.0.1
>> libCTKCore.so.0.1 ?libCTKPluginFramework.so
>> ?libCTKPluginFramework.so.0.1.0
>>
>>
>> The Debian package wouldn't change that. Please have a look at the
>> current package in 'experimental':
>> ? ?http://packages.debian.org/experimental/amd64/libctk0.1/filelist
>>
>> Thanks
>> -Dominique
>>
>> P.S. Please not that "Ubuntu" = "Debian unstable + closed source
>> graphics driver" :)
>>
>>
>> On Tue, Dec 6, 2011 at 2:50 PM, Sascha Zelzer
>> <s.zelzer at dkfz-heidelberg.de> ?wrote:
>>>
>>> Hi Dominique,
>>>
>>> Thanks a lot for your efforts!
>>>
>>> I am not experienced with Debian packages but I wonder what the actual
>>> set
>>> of libraries for such a CTK package would be. And how do the library
>>> versions relate to the package version? Shouldn't we package each library
>>> separately, or are those questions irrelevant for Debian unstable?
>>>
>>> I am also not sure if bumping the minor version is enough, especially if
>>> we
>>> look at the libraries as a whole. We had discussions about versioning of
>>> our
>>> libraries and having a global major/minor/patch set for all CTK versions
>>> is
>>> certainly not adequate. But maybe people do not care that much regarding
>>> Debian unstable...
>>>
>>> Sorry for the brain dump,
>>>
>>> Sascha
>>>
>>>
>>> On 12/06/2011 05:05 PM, Dominique Belhachemi wrote:
>>>>
>>>> Hi Marco,
>>>>
>>>> Yes, I would use the tagged version for Debian. I just need something
>>>> what can be considered as "stable enough".
>>>>
>>>> CTK has already been accepted in 'experimental' back in July
>>>> (http://packages.qa.debian.org/c/ctk/news/20110717T133234Z.html). So
>>>> the upload to 'unstable' would take only a couple of minutes.
>>>>
>>>> Don't worry about MITK, we can always update the package in 'unstable'.
>>>>
>>>> Additionally to creating the tag I would like to see a bump in the
>>>> soname.
>>>> Updating the MINOR value would be the correct thing to do because I am
>>>> sure that the ABI/API changed a lot.
>>>> -set(CTK_MINOR_VERSION 1)
>>>> +set(CTK_MINOR_VERSION 2)
>>>>
>>>> But if this is not possible, updating the PATCH value would help as
>>>> well.
>>>> -set(CTK_PATCH_VERSION 0)
>>>> +set(CTK_PATCH_VERSION 1)
>>>>
>>>> Thanks
>>>> -Dominique
>>>>
>>>> On Tue, Dec 6, 2011 at 7:46 AM, Marco Nolden
>>>> <m.nolden at dkfz-heidelberg.de> ? ?wrote:
>>>>>
>>>>> Hi Dominique,
>>>>>
>>>>> tagging is a really good idea, we already started discussions about
>>>>> this
>>>>> at
>>>>> the recent hackfest.
>>>>>
>>>>> Would you use this tag as a basis for the Debian packaging? As far as I
>>>>> know
>>>>> the Debian packaging procedure it will take some time till this really
>>>>> gets
>>>>> accepted in "unstable". What is the timeframe that you expect? Would
>>>>> you
>>>>> update CTK to a more recent version before entering "unstable"? I'm
>>>>> asking
>>>>> because we're also planning a debian package for MITK and we would at
>>>>> least
>>>>> need some fixes from the most recent version of CTK.
>>>>> Another option would be to apply some fixes on the Slicer 4 version and
>>>>> create a dedicated ctk-for-debian release branch on Github and discuss
>>>>> the
>>>>> fixes to put in there.
>>>>>
>>>>> Best
>>>>> Marco
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 12/06/2011 03:09 AM, Dominique Belhachemi wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I was wondering whether it is possible to create a tag for CTK.
>>>>>>
>>>>>> More and more people are using ctk and it would be good to have
>>>>>> something like a pre-release. What do you thing about tagging the ctk
>>>>>> version Slicer 4 is using?
>>>>>>
>>>>>> Thanks
>>>>>> -Dominique
>>>>>> _______________________________________________
>>>>>> Ctk-developers mailing list
>>>>>> Ctk-developers at commontk.org
>>>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ----------------------------------------------------------------------
>>>>> Dipl.-Inform. Med. Marco Nolden
>>>>> Deutsches Krebsforschungszentrum ? ? ? (German Cancer Research Center)
>>>>> Div. Medical& ? ?Biological Informatics ? ? ? ? ?Tel: (+49) 6221-42
>>>>> 2325
>>>>>
>>>>> Im Neuenheimer Feld 280 ? ? ? ? ? ? ? ? ? ? ? ?Fax: (+49) 6221-42 2345
>>>>> D-69120 Heidelberg ? ? ? ? ? ? ? ? ? ? ? ? ? ? eMail: M.Nolden at dkfz.de
>>>>
>>>> _______________________________________________
>>>>
>>>> Ctk-developers mailing list
>>>> Ctk-developers at commontk.org
>>>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>>
>>>
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>


From s.zelzer at dkfz-heidelberg.de  Thu Dec  8 07:36:39 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Thu, 08 Dec 2011 08:36:39 +0100
Subject: [Ctk-developers] New Wiki Main Page
Message-ID: <4EE06907.2040904@dkfz-heidelberg.de>

Hi CTK developers,

During the last Hackfest in Sophia-Antipolis we identified the need to 
better communicate to first time users what CTK provides and how it can 
help the medical imaging community.

One step into that direction has been quite technical [1].

The second step, which we discussed on the last day of the Hackfest 
involved the CTK Wiki. We decided to do a redesign and put the focus of 
the main page on the four main working areas of CTK (which were also 
identified during this week). The result can be seen here:

http://www.commontk.org/index.php/Main_Page

CTK developers working on one or more of these main areas should have a 
look at the text and links and verify the available information. 
Feedback is also welcome.

Thanks,

Sascha

[1] 
http://public.kitware.com/pipermail/ctk-developers/2011-November/000889.html


From pieper at ibility.net  Thu Dec  8 14:55:47 2011
From: pieper at ibility.net (Steve Pieper)
Date: Thu, 8 Dec 2011 09:55:47 -0500
Subject: [Ctk-developers] New Wiki Main Page
In-Reply-To: <4EE06907.2040904@dkfz-heidelberg.de>
References: <4EE06907.2040904@dkfz-heidelberg.de>
Message-ID: <CA+OFd4w3k8u4OMZ=9Ui2Usn4FNr-KDPy_tsYOhuXBgy_XHy3Vg@mail.gmail.com>

Looks great Sascha - thanks!

I added some material to the ctkDICOM page.

-Steve

p.s. And I changed the page name to DICOM not Dicom :D

On Thu, Dec 8, 2011 at 2:36 AM, Sascha Zelzer
<s.zelzer at dkfz-heidelberg.de> wrote:
> Hi CTK developers,
>
> During the last Hackfest in Sophia-Antipolis we identified the need to
> better communicate to first time users what CTK provides and how it can help
> the medical imaging community.
>
> One step into that direction has been quite technical [1].
>
> The second step, which we discussed on the last day of the Hackfest involved
> the CTK Wiki. We decided to do a redesign and put the focus of the main page
> on the four main working areas of CTK (which were also identified during
> this week). The result can be seen here:
>
> http://www.commontk.org/index.php/Main_Page
>
> CTK developers working on one or more of these main areas should have a look
> at the text and links and verify the available information. Feedback is also
> welcome.
>
> Thanks,
>
> Sascha
>
> [1]
> http://public.kitware.com/pipermail/ctk-developers/2011-November/000889.html
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers


From s.zelzer at dkfz-heidelberg.de  Thu Dec  8 20:14:40 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Thu, 08 Dec 2011 21:14:40 +0100
Subject: [Ctk-developers] ctkDICOMDemoSCUMain.obj : error LNK2019
In-Reply-To: <E1RY4AQ-0002Sp-00.looky12-bk-ru@f250.mail.ru>
References: <E1RXioD-0006fj-00.looky12-bk-ru@f169.mail.ru>
	<CA+OFd4xY3zCv2NnU=KKeGat2F_htpq2miaOCyoVjHWnFYr4rFg@mail.gmail.com>
	<4EDE4B7A.4050409@dkfz-heidelberg.de>
	<E1RY4AQ-0002Sp-00.looky12-bk-ru@f250.mail.ru>
Message-ID: <4EE11AB0.7050000@dkfz-heidelberg.de>

Hi,

I just had to compile a recent CTK version for our project on Windows 
(VS 2008) and run into very similar issues. I just pushed the Windows 
fixes to the CTK repository. Let us know if that also solves your issues.

Thanks,

Sascha

On 12/07/2011 12:11 AM, looky12 looky12 wrote:
>
> I use vs 2008 with QT addin. Attached archive contain ctk files of 
> root directory (with ctk configuration i think).
>
> 06 ??????? 2011, 21:06 ?? Sascha Zelzer <s.zelzer at dkfz-heidelberg.de>:
>
>     We regularly build CTK under Windows (superbuild) but not the
>     ctkDICOMDemoSCUMain.cpp (I think).
>
>     What Visual Studio version are you using and which build options
>     of CTK did you change?
>
>     - Sascha
>
>     On 12/06/2011 04:19 PM, Steve Pieper wrote:
>>     Maybe someone else on the ctk list has ideas - I've been building
>>     ctk on linux from within slicer4 and it's working fine but I
>>     haven't tried windows lately - has anyone else?
>>
>>     -teve
>>
>>     On Mon, Dec 5, 2011 at 8:19 PM, looky12 looky12 <looky12 at bk.ru
>>     <sentmsg?compose&To=looky12 at bk.ru>> wrote:
>>
>>         Hello Steve, thanks for your notice
>>
>>         At first i attempt too build ctk-cuperbuild, but not all
>>         projects (vtk, dcmtk, etc)  correctly checkouts at once, and
>>         i manually select " build current project" .  Then if all
>>         packages checkouts and builds, but error still exist, i open
>>         package dirictory with errors and trying to rebuild it.
>>
>>         06 ??????? 2011, 04:38 ?? Steve Pieper <pieper at ibility.net
>>         <sentmsg?compose&To=pieper at ibility.net>>:
>>
>>             Hi Oleg -
>>
>>             Sorry - I wasn't clear - it's not your English :)
>>
>>             I meant that because the superbuild (top) level of the
>>             ctk cmake process does checkouts and builds of several
>>             other packages (vtk, dcmtk, etc) I wondered if one of
>>             those external projects was out of data or didn't build
>>             correctly.  If you tried to build the packages by hand
>>             that might explain the issue - typically for ctk we would
>>             just configure the ctk superbuild level and let it take
>>             care of the dependencies.
>>
>>             Hope that makes more sense,
>>             -Steve
>>
>>
>>
>>             On Mon, Dec 5, 2011 at 7:22 PM, looky12 looky12
>>             <looky12 at bk.ru
>>             <http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>>
>>             wrote:
>>
>>                 If i turn off only VTK in this configuration, all
>>                 other projects builds.  "Makes me wonder if somehow
>>                 your build isn't up to date" - sorry but i think i
>>                 understand this not correctly, maybe because i
>>                 attempt build projects separately at first, and then
>>                 all solution.
>>
>>                 Sorry for my English
>>                 Oleg.
>>
>>
>>                 01 Dec 2011, 23:11 ?? Steve Pieper
>>                 <pieper at ibility.net
>>                 <http://e.mail.ru/cgi-bin/sentmsg?compose&To=pieper at ibility.net>>:
>>
>>                     Hi -
>>
>>                     Looks like you are also getting build errors
>>                     related to ctkVTK -- makes me wonder if somehow
>>                     your build isn't up to date. If you turn off
>>                     dicom and vtk does everything else build?
>>
>>                     -Steve
>>
>>                     On Thu, Dec 1, 2011 at 11:29 AM, looky12 looky12
>>                     <looky12 at bk.ru
>>                     <http://e.mail.ru/cgi-bin/sentmsg?compose&To=looky12 at bk.ru>>
>>                     wrote:
>>
>>                         Hello everyone, i have some problems in build
>>                         process, thanks for your attention.
>>
>>                         1>------ Build started: Project: qxmlrpc,
>>                         Configuration: Debug Win32 ------
>>                         1>Performing update step (git fetch) for
>>                         'qxmlrpc'
>>                         1>Performing configure step for 'qxmlrpc'
>>                         1>-- Configuring done
>>                         1>-- Generating done
>>                         1>-- Build files have been written to:
>>                         C:/CTK/CTK-superbuild/qxmlrpc-build
>>                         1>Performing build step for 'qxmlrpc'
>>                         1>Microsoft (R) Visual Studio Version
>>                         9.0.30729.1.
>>                         1>Copyright (C) Microsoft Corp. All rights
>>                         reserved.
>>                         1>========== Build: 0 succeeded, 0 failed, 3
>>                         up-to-date, 0 skipped ==========
>>                         1>No install step for 'qxmlrpc'
>>                         1>Completed 'qxmlrpc'
>>                         1>Build log was saved at
>>                         "file://c:\CTK\CTK-superbuild\qxmlrpc.dir\Debug\BuildLog.htm"
>>                         1>qxmlrpc - 0 error(s), 0 warning(s)
>>                         2>------ Build started: Project:
>>                         CTK-Configure, Configuration: Debug Win32 ------
>>                         2>Performing configure step for 'CTK-Configure'
>>                         2>-- Generated:
>>                         C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep.txt
>>                         2>-- Generated:
>>                         C:/CTK/CTK-superbuild/CTK-build/DGraphInput-alldep-withext.txt
>>                         2>-- Generated:
>>                         C:/CTK/CTK-superbuild/CTK-build/DGraphInput.txt
>>                         2>-- Generated:
>>                         C:/CTK/CTK-superbuild/CTK-build/Project.xml
>>                         2>-- CTKCore: BFD support disabled
>>                         2>-- Configuring done
>>                         2>-- Generating done
>>                         2>CMake Warning:
>>                         2>  Manually-specified variables were not
>>                         used by the project:
>>                         2>    CTEST_USE_LAUNCHERS
>>                         2>    DOCUMENTATION_ARCHIVES_OUTPUT_DIRECTORY
>>                         2>    DOCUMENTATION_TARGET_IN_ALL
>>                         2>-- Build files have been written to:
>>                         C:/CTK/CTK-superbuild/CTK-build
>>                         2>No build step for 'CTK-Configure'
>>                         2>No install step for 'CTK-Configure'
>>                         2>Completed 'CTK-Configure'
>>                         2>Build log was saved at
>>                         "file://c:\CTK\CTK-superbuild\CTK-Configure.dir\Debug\BuildLog.htm"
>>                         2>CTK-Configure - 0 error(s), 0 warning(s)
>>                         3>------ Build started: Project: CTK-build,
>>                         Configuration: Debug Win32 ------
>>                         3>Microsoft (R) Visual Studio Version
>>                         9.0.30729.1.
>>                         3>Copyright (C) Microsoft Corp. All rights
>>                         reserved.
>>                         3>1>------ Build started: Project:
>>                         CTKVisualizationVTKWidgets, Configuration:
>>                         Debug Win32 ------
>>                         3>1>Compiling...
>>                         3>2>------ Build started: Project:
>>                         ctkDICOMDemoSCU, Configuration: Debug Win32
>>                         ------
>>                         3>2>Linking...
>>                         3>1>ctkVTKScalarsToColorsView.cpp
>>                         3>2>ctkDICOMDemoSCUMain.obj : error LNK2019:
>>                         unresolved external symbol "public: virtual
>>                         class OFCondition __thiscall
>>                         ctkDcmSCU::sendECHORequest(unsigned char)"
>>                         (?sendECHORequest at ctkDcmSCU@@UAE?AVOFCondition@@E at Z)
>>                         referenced in function
>>                         _main.........................................................................................................................
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20111208/19bee320/attachment.htm>