From pieper at ibility.net  Sun Apr 10 14:53:03 2011
From: pieper at ibility.net (Steve Pieper)
Date: Sun, 10 Apr 2011 10:53:03 -0400
Subject: [Ctk-developers] Fwd: [Nipy-devel] big github issues improvement!!!
In-Reply-To: <BANLkTim1Zkwtb3mS36h1Lv2nyUS0TSENkw@mail.gmail.com>
References: <BANLkTim1Zkwtb3mS36h1Lv2nyUS0TSENkw@mail.gmail.com>
Message-ID: <BANLkTi=hdoS3fn5RLkMwhwjEOyKQLuWuww@mail.gmail.com>

These improvements look really nice...

---------- Forwarded message ----------
From: Fernando Perez <fperez.net at gmail.com>
Date: Sat, Apr 9, 2011 at 9:21 PM
Subject: [Nipy-devel] big github issues improvement!!!
To: IPython Development list <ipython-dev at scipy.org>
Cc: NIPY Developer's List <nipy-devel at neuroimaging.scipy.org>


Hi everyone,

check out e.g. https://github.com/ipython/ipython/issues

literally in the last few minutes (I know b/c I've been opening issues
pages all day, so I know a half hour ago it wasn't like this) they
rolled out a new issues interface.

I haven't explored it much yet, but already some of our biggest gripes
are improved:

- many labels (like we're using) don't obscure the issue titles.
- milestones, assigned persons as separate fields.
- multiple pages to see other issues
- working search !!! yes!

Finally, finally...  I kept saying these guys were so good, and the
old interface so bad, that something *had* to be coming.  But the wait
was getting long... This looks really, really great.

In case anyone from gh sees this: THANK YOU!!!


BTW, speaking of github, a post along the lines many of us in academia
have been talking about:

http://marciovm.com/i-want-a-github-of-science


Cheers,

f
_______________________________________________
Nipy-devel mailing list
Nipy-devel at neuroimaging.scipy.org
http://mail.scipy.org/mailman/listinfo/nipy-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20110410/2fb72012/attachment.htm>

From s.zelzer at dkfz-heidelberg.de  Sun Apr 10 16:01:39 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Sun, 10 Apr 2011 18:01:39 +0200
Subject: [Ctk-developers] Fwd: [Nipy-devel] big github issues
	improvement!!!
In-Reply-To: <BANLkTi=hdoS3fn5RLkMwhwjEOyKQLuWuww@mail.gmail.com>
References: <BANLkTim1Zkwtb3mS36h1Lv2nyUS0TSENkw@mail.gmail.com>
	<BANLkTi=hdoS3fn5RLkMwhwjEOyKQLuWuww@mail.gmail.com>
Message-ID: <4DA1D463.2060800@dkfz-heidelberg.de>

Yes, ceraintly an improvement. But seems to have bugs still... switching 
between open and closed issues does not do anything.

On 04/10/2011 04:53 PM, Steve Pieper wrote:
> These improvements look really nice...
>
> ---------- Forwarded message ----------
> From: *Fernando Perez* <fperez.net <http://fperez.net>@gmail.com 
> <http://gmail.com>>
> Date: Sat, Apr 9, 2011 at 9:21 PM
> Subject: [Nipy-devel] big github issues improvement!!!
> To: IPython Development list <ipython-dev at scipy.org 
> <mailto:ipython-dev at scipy.org>>
> Cc: NIPY Developer's List <nipy-devel at neuroimaging.scipy.org 
> <mailto:nipy-devel at neuroimaging.scipy.org>>
>
>
> Hi everyone,
>
> check out e.g. https://github.com/ipython/ipython/issues
>
> literally in the last few minutes (I know b/c I've been opening issues
> pages all day, so I know a half hour ago it wasn't like this) they
> rolled out a new issues interface.
>
> I haven't explored it much yet, but already some of our biggest gripes
> are improved:
>
> - many labels (like we're using) don't obscure the issue titles.
> - milestones, assigned persons as separate fields.
> - multiple pages to see other issues
> - working search !!! yes!
>
> Finally, finally...  I kept saying these guys were so good, and the
> old interface so bad, that something *had* to be coming.  But the wait
> was getting long... This looks really, really great.
>
> In case anyone from gh sees this: THANK YOU!!!
>
>
> BTW, speaking of github, a post along the lines many of us in academia
> have been talking about:
>
> http://marciovm.com/i-want-a-github-of-science
>
>
> Cheers,
>
> f
> _______________________________________________
> Nipy-devel mailing list
> Nipy-devel at neuroimaging.scipy.org 
> <mailto:Nipy-devel at neuroimaging.scipy.org>
> http://mail.scipy.org/mailman/listinfo/nipy-devel
>

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

From jchris.fillionr at kitware.com  Sun Apr 10 16:41:51 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Sun, 10 Apr 2011 12:41:51 -0400
Subject: [Ctk-developers] Fwd: [Nipy-devel] big github issues
	improvement!!!
In-Reply-To: <4DA1D463.2060800@dkfz-heidelberg.de>
References: <BANLkTim1Zkwtb3mS36h1Lv2nyUS0TSENkw@mail.gmail.com>
	<BANLkTi=hdoS3fn5RLkMwhwjEOyKQLuWuww@mail.gmail.com>
	<4DA1D463.2060800@dkfz-heidelberg.de>
Message-ID: <BANLkTiksFgUKDxjVLso30nkHi2xEAK1-3g@mail.gmail.com>

And assigning the issue to somebody is kinda slow :p

On Sun, Apr 10, 2011 at 12:01 PM, Sascha Zelzer <s.zelzer at dkfz-heidelberg.de
> wrote:

>  Yes, ceraintly an improvement. But seems to have bugs still... switching
> between open and closed issues does not do anything.
>
>
> On 04/10/2011 04:53 PM, Steve Pieper wrote:
>
> These improvements look really nice...
>
> ---------- Forwarded message ----------
> From: Fernando Perez <fperez.net at gmail.com>
> Date: Sat, Apr 9, 2011 at 9:21 PM
> Subject: [Nipy-devel] big github issues improvement!!!
> To: IPython Development list <ipython-dev at scipy.org>
> Cc: NIPY Developer's List <nipy-devel at neuroimaging.scipy.org>
>
>
> Hi everyone,
>
> check out e.g. https://github.com/ipython/ipython/issues
>
> literally in the last few minutes (I know b/c I've been opening issues
> pages all day, so I know a half hour ago it wasn't like this) they
> rolled out a new issues interface.
>
> I haven't explored it much yet, but already some of our biggest gripes
> are improved:
>
> - many labels (like we're using) don't obscure the issue titles.
> - milestones, assigned persons as separate fields.
> - multiple pages to see other issues
> - working search !!! yes!
>
> Finally, finally...  I kept saying these guys were so good, and the
> old interface so bad, that something *had* to be coming.  But the wait
> was getting long... This looks really, really great.
>
> In case anyone from gh sees this: THANK YOU!!!
>
>
> BTW, speaking of github, a post along the lines many of us in academia
> have been talking about:
>
> http://marciovm.com/i-want-a-github-of-science
>
>
> Cheers,
>
> f
> _______________________________________________
> Nipy-devel mailing list
> Nipy-devel at neuroimaging.scipy.org
> http://mail.scipy.org/mailman/listinfo/nipy-devel
>
>
>
> _______________________________________________
> 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/20110410/9dfd4f54/attachment.htm>

From jchris.fillionr at kitware.com  Mon Apr 11 16:21:45 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Mon, 11 Apr 2011 12:21:45 -0400
Subject: [Ctk-developers] Coming changes in External project organization
Message-ID: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>

Hi Folks,

Using CTK as an external project in more and more project, the path length
could be an issue on windows platform.
Indeed, the path length on windows is limited to 260 characters. [1]

*What motivates this change:*

Such problem could arise, if, for example, your project is build in folder
like:

"c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"


"YourProject" relying also on Superbuild and using CTK as an external
project .. will fail to build for some obscure reason.


*Current CTK organization:*

Currently the project are organized as described below:

 <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
 <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
...
 <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
 <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
...
 <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
 <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
...
 <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
 <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
...
 <CTK-SUPERBUILD>/CTK-build


*Solution proposed:*

With some minor changes, the structure would like:

 <CTK-SUPERBUILD>/CTK-build
 <CTK-SUPERBUILD>/VTK
 <CTK-SUPERBUILD>/VTK-build
 <CTK-SUPERBUILD>/VTK-cmake/src
 <CTK-SUPERBUILD>/VTK-cmake/tmp
 <CTK-SUPERBUILD>/VTK
 <CTK-SUPERBUILD>/DCMTK-build
 <CTK-SUPERBUILD>/DCMTK-cmake/src
 <CTK-SUPERBUILD>/DCMTK-cmake/tmp

Pros:
  - Doing so will decrease the average length of external project path
associated with CTK.
  - If needed, make the "cleaning" of external project easier "rm VTK*"
instead of "cd" in each CMakeExternals sub folders ..

*Action plan:*

I plan to implement and test this change this coming week.

That improvment shouldn't cause any issue, but If it happens to be a problem
within your project and you require some time to figure out a fix or would
like to contact me. Please, do it before the end of the week :)

Next week, following your comments I will then integrate the change to CTK
master.

Thanks
Jc

[1] http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath

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

From s.zelzer at dkfz-heidelberg.de  Mon Apr 11 16:29:43 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Mon, 11 Apr 2011 18:29:43 +0200
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
Message-ID: <4DA32C77.5070002@dkfz-heidelberg.de>

Hi Jc,

we use a similar structure for external projects in MITK, so +1 from me. 
I would only suggest a slight modification:

Can we use

<CTK-SUPERBUILD>/VTK-src
<CTK-SUPERBUILD>/VTK-tmp

instead of

<CTK-SUPERBUILD>/VTK-cmake/src
<CTK-SUPERBUILD>/VTK-cmake/tmp

?

Thanks for taking care of this,

Sascha

On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
> Hi Folks,
>
> Using CTK as an external project in more and more project, the path 
> length could be an issue on windows platform.
> Indeed, the path length on windows is limited to 260 characters. [1]
>
> *What motivates this change:*
>
> Such problem could arise, if, for example, your project is build in 
> folder like:
>
> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly" 
>
>
> "YourProject" relying also on Superbuild and using CTK as an external 
> project .. will fail to build for some obscure reason.
>
>
> *Current CTK organization:*
>
> Currently the project are organized as described below:
>
> <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
> <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
> ...
> <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
> <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
> ...
> <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
> <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
> ...
> <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
> <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
> ...
> <CTK-SUPERBUILD>/CTK-build
>
>
> *Solution proposed:*
>
> With some minor changes, the structure would like:
>
> <CTK-SUPERBUILD>/CTK-build
> <CTK-SUPERBUILD>/VTK
> <CTK-SUPERBUILD>/VTK-build
> <CTK-SUPERBUILD>/VTK-cmake/src
> <CTK-SUPERBUILD>/VTK-cmake/tmp
> <CTK-SUPERBUILD>/VTK
> <CTK-SUPERBUILD>/DCMTK-build
> <CTK-SUPERBUILD>/DCMTK-cmake/src
> <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>
> Pros:
>   - Doing so will decrease the average length of external project path 
> associated with CTK.
>   - If needed, make the "cleaning" of external project easier "rm 
> VTK*" instead of "cd" in each CMakeExternals sub folders ..
>
> *Action plan:*
>
> I plan to implement and test this change this coming week.
>
> That improvment shouldn't cause any issue, but If it happens to be a 
> problem within your project and you require some time to figure out a 
> fix or would like to contact me. Please, do it before the end of the 
> week :)
>
> Next week, following your comments I will then integrate the change to 
> CTK master.
>
> Thanks
> Jc
>
> [1] 
> http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>
> -- 
> +1 919 869 8849
>

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

From jchris.fillionr at kitware.com  Mon Apr 11 16:59:12 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Mon, 11 Apr 2011 12:59:12 -0400
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <4DA32C77.5070002@dkfz-heidelberg.de>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
	<4DA32C77.5070002@dkfz-heidelberg.de>
Message-ID: <BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>

Hi Sasha,

To clarify, when I wrote:

 <CTK-SUPERBUILD>/VTK-build
 <CTK-SUPERBUILD>/VTK-cmake/src
 <CTK-SUPERBUILD>/VTK-cmake/tmp
 <CTK-SUPERBUILD>/VTK

It means:

 <CTK-SUPERBUILD>/VTK-build         # Build directory
 <CTK-SUPERBUILD>/VTK-cmake         # Directory where CMake store
timestamps, source ...
 <CTK-SUPERBUILD>/VTK               # Source directory



Or should we use structure like this one instead:

 <CTK-SUPERBUILD>/VTK-build         # Build directory
 <CTK-SUPERBUILD>/VTK-cmake        # Directory where CMake store timestamps,
source ...
 <CTK-SUPERBUILD>/VTK-src                    # Source directory


What do you think ?

I would prefer option 1) since I am more use to it ... where the source
directory match the project name.

Thanks
Jc

On Mon, Apr 11, 2011 at 12:29 PM, Sascha Zelzer <s.zelzer at dkfz-heidelberg.de
> wrote:

>  Hi Jc,
>
> we use a similar structure for external projects in MITK, so +1 from me. I
> would only suggest a slight modification:
>
> Can we use
>
> <CTK-SUPERBUILD>/VTK-src
> <CTK-SUPERBUILD>/VTK-tmp
>
> instead of
>
>
> <CTK-SUPERBUILD>/VTK-cmake/src
> <CTK-SUPERBUILD>/VTK-cmake/tmp
>
> ?
>
> Thanks for taking care of this,
>
> Sascha
>
>
> On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
>
> Hi Folks,
>
> Using CTK as an external project in more and more project, the path length
> could be an issue on windows platform.
> Indeed, the path length on windows is limited to 260 characters. [1]
>
> *What motivates this change:*
>
> Such problem could arise, if, for example, your project is build in folder
> like:
>
> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>
>
> "YourProject" relying also on Superbuild and using CTK as an external
> project .. will fail to build for some obscure reason.
>
>
> *Current CTK organization:*
>
> Currently the project are organized as described below:
>
>  <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
>  <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
> ...
>  <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
>  <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
> ...
>  <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
>  <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
> ...
>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
> ...
>  <CTK-SUPERBUILD>/CTK-build
>
>
> *Solution proposed:*
>
> With some minor changes, the structure would like:
>
>  <CTK-SUPERBUILD>/CTK-build
>  <CTK-SUPERBUILD>/VTK
>  <CTK-SUPERBUILD>/VTK-build
>  <CTK-SUPERBUILD>/VTK-cmake/src
>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>  <CTK-SUPERBUILD>/VTK
>  <CTK-SUPERBUILD>/DCMTK-build
>  <CTK-SUPERBUILD>/DCMTK-cmake/src
>  <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>
> Pros:
>   - Doing so will decrease the average length of external project path
> associated with CTK.
>   - If needed, make the "cleaning" of external project easier "rm VTK*"
> instead of "cd" in each CMakeExternals sub folders ..
>
> *Action plan:*
>
> I plan to implement and test this change this coming week.
>
> That improvment shouldn't cause any issue, but If it happens to be a
> problem within your project and you require some time to figure out a fix or
> would like to contact me. Please, do it before the end of the week :)
>
> Next week, following your comments I will then integrate the change to CTK
> master.
>
> Thanks
> Jc
>
> [1]
> http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>
> --
> +1 919 869 8849
>
>
>
> _______________________________________________
> 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/20110411/e1a16b2d/attachment.htm>

From s.zelzer at dkfz-heidelberg.de  Mon Apr 11 17:03:38 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Mon, 11 Apr 2011 19:03:38 +0200
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
	<4DA32C77.5070002@dkfz-heidelberg.de>
	<BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
Message-ID: <4DA3346A.6030004@dkfz-heidelberg.de>

Ah, all right. Option 1) then sounds good to me.

Thanks,
Sascha

On 04/11/2011 06:59 PM, Jean-Christophe Fillion-Robin wrote:
> Hi Sasha,
>
> To clarify, when I wrote:
>
> <CTK-SUPERBUILD>/VTK-build
> <CTK-SUPERBUILD>/VTK-cmake/src
> <CTK-SUPERBUILD>/VTK-cmake/tmp
> <CTK-SUPERBUILD>/VTK
>
> It means:
>
> <CTK-SUPERBUILD>/VTK-build         # Build directory
> <CTK-SUPERBUILD>/VTK-cmake         # Directory where CMake store 
> timestamps, source ...
> <CTK-SUPERBUILD>/VTK               # Source directory
>
>
>
> Or should we use structure like this one instead:
>
> <CTK-SUPERBUILD>/VTK-build         # Build directory
> <CTK-SUPERBUILD>/VTK-cmake        # Directory where CMake store 
> timestamps, source ...
> <CTK-SUPERBUILD>/VTK-src                    # Source directory
>
>
> What do you think ?
>
> I would prefer option 1) since I am more use to it ... where the 
> source directory match the project name.
>
> Thanks
> Jc
>
> On Mon, Apr 11, 2011 at 12:29 PM, Sascha Zelzer 
> <s.zelzer at dkfz-heidelberg.de <mailto:s.zelzer at dkfz-heidelberg.de>> wrote:
>
>     Hi Jc,
>
>     we use a similar structure for external projects in MITK, so +1
>     from me. I would only suggest a slight modification:
>
>     Can we use
>
>     <CTK-SUPERBUILD>/VTK-src
>     <CTK-SUPERBUILD>/VTK-tmp
>
>     instead of
>
>
>     <CTK-SUPERBUILD>/VTK-cmake/src
>     <CTK-SUPERBUILD>/VTK-cmake/tmp
>
>     ?
>
>     Thanks for taking care of this,
>
>     Sascha
>
>
>     On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
>>     Hi Folks,
>>
>>     Using CTK as an external project in more and more project, the
>>     path length could be an issue on windows platform.
>>     Indeed, the path length on windows is limited to 260 characters. [1]
>>
>>     *What motivates this change:*
>>
>>     Such problem could arise, if, for example, your project is build
>>     in folder like:
>>
>>     "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>>
>>
>>     "YourProject" relying also on Superbuild and using CTK as an
>>     external project .. will fail to build for some obscure reason.
>>
>>
>>     *Current CTK organization:*
>>
>>     Currently the project are organized as described below:
>>
>>     <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
>>     <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
>>     ...
>>     <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
>>     <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
>>     ...
>>     <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
>>     <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
>>     ...
>>     <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
>>     <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
>>     ...
>>     <CTK-SUPERBUILD>/CTK-build
>>
>>
>>     *Solution proposed:*
>>
>>     With some minor changes, the structure would like:
>>
>>     <CTK-SUPERBUILD>/CTK-build
>>     <CTK-SUPERBUILD>/VTK
>>     <CTK-SUPERBUILD>/VTK-build
>>     <CTK-SUPERBUILD>/VTK-cmake/src
>>     <CTK-SUPERBUILD>/VTK-cmake/tmp
>>     <CTK-SUPERBUILD>/VTK
>>     <CTK-SUPERBUILD>/DCMTK-build
>>     <CTK-SUPERBUILD>/DCMTK-cmake/src
>>     <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>>
>>     Pros:
>>       - Doing so will decrease the average length of external project
>>     path associated with CTK.
>>       - If needed, make the "cleaning" of external project easier "rm
>>     VTK*" instead of "cd" in each CMakeExternals sub folders ..
>>
>>     *Action plan:*
>>
>>     I plan to implement and test this change this coming week.
>>
>>     That improvment shouldn't cause any issue, but If it happens to
>>     be a problem within your project and you require some time to
>>     figure out a fix or would like to contact me. Please, do it
>>     before the end of the week :)
>>
>>     Next week, following your comments I will then integrate the
>>     change to CTK master.
>>
>>     Thanks
>>     Jc
>>
>>     [1]
>>     http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>>
>>     -- 
>>     +1 919 869 8849 <tel:%2B1%20919%20869%208849>
>>
>
>
>     _______________________________________________
>     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/20110411/78d4bafe/attachment.htm>

From pieper at ibility.net  Mon Apr 11 17:09:52 2011
From: pieper at ibility.net (Steve Pieper)
Date: Mon, 11 Apr 2011 13:09:52 -0400
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
	<4DA32C77.5070002@dkfz-heidelberg.de>
	<BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
Message-ID: <BANLkTimdkURS6Th1KF9iQFsE7PZajvikdg@mail.gmail.com>

I'd also vote for the case where "VTK" means source directory (instead of
using VTK-src).

BTW, what goes in VTK-cmake/src ?  All I see now is timestamps and tmp
files...

-Steve

On Mon, Apr 11, 2011 at 12:59 PM, Jean-Christophe Fillion-Robin <
jchris.fillionr at kitware.com> wrote:

> Hi Sasha,
>
> To clarify, when I wrote:
>
>  <CTK-SUPERBUILD>/VTK-build
>  <CTK-SUPERBUILD>/VTK-cmake/src
>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>  <CTK-SUPERBUILD>/VTK
>
> It means:
>
>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>  <CTK-SUPERBUILD>/VTK-cmake         # Directory where CMake store
> timestamps, source ...
>  <CTK-SUPERBUILD>/VTK               # Source directory
>
>
>
> Or should we use structure like this one instead:
>
>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>  <CTK-SUPERBUILD>/VTK-cmake        # Directory where CMake store
> timestamps, source ...
>  <CTK-SUPERBUILD>/VTK-src                    # Source directory
>
>
> What do you think ?
>
> I would prefer option 1) since I am more use to it ... where the source
> directory match the project name.
>
> Thanks
> Jc
>
> On Mon, Apr 11, 2011 at 12:29 PM, Sascha Zelzer <
> s.zelzer at dkfz-heidelberg.de> wrote:
>
>>  Hi Jc,
>>
>> we use a similar structure for external projects in MITK, so +1 from me. I
>> would only suggest a slight modification:
>>
>> Can we use
>>
>> <CTK-SUPERBUILD>/VTK-src
>> <CTK-SUPERBUILD>/VTK-tmp
>>
>> instead of
>>
>>
>> <CTK-SUPERBUILD>/VTK-cmake/src
>> <CTK-SUPERBUILD>/VTK-cmake/tmp
>>
>> ?
>>
>> Thanks for taking care of this,
>>
>> Sascha
>>
>>
>> On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
>>
>> Hi Folks,
>>
>> Using CTK as an external project in more and more project, the path length
>> could be an issue on windows platform.
>> Indeed, the path length on windows is limited to 260 characters. [1]
>>
>> *What motivates this change:*
>>
>> Such problem could arise, if, for example, your project is build in folder
>> like:
>>
>> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>>
>>
>> "YourProject" relying also on Superbuild and using CTK as an external
>> project .. will fail to build for some obscure reason.
>>
>>
>> *Current CTK organization:*
>>
>> Currently the project are organized as described below:
>>
>>  <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
>>  <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
>> ...
>>  <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
>>  <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
>> ...
>>  <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
>>  <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
>> ...
>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
>> ...
>>  <CTK-SUPERBUILD>/CTK-build
>>
>>
>> *Solution proposed:*
>>
>> With some minor changes, the structure would like:
>>
>>  <CTK-SUPERBUILD>/CTK-build
>>  <CTK-SUPERBUILD>/VTK
>>  <CTK-SUPERBUILD>/VTK-build
>>  <CTK-SUPERBUILD>/VTK-cmake/src
>>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>>  <CTK-SUPERBUILD>/VTK
>>  <CTK-SUPERBUILD>/DCMTK-build
>>  <CTK-SUPERBUILD>/DCMTK-cmake/src
>>  <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>>
>> Pros:
>>   - Doing so will decrease the average length of external project path
>> associated with CTK.
>>   - If needed, make the "cleaning" of external project easier "rm VTK*"
>> instead of "cd" in each CMakeExternals sub folders ..
>>
>> *Action plan:*
>>
>> I plan to implement and test this change this coming week.
>>
>> That improvment shouldn't cause any issue, but If it happens to be a
>> problem within your project and you require some time to figure out a fix or
>> would like to contact me. Please, do it before the end of the week :)
>>
>> Next week, following your comments I will then integrate the change to CTK
>> master.
>>
>> Thanks
>> Jc
>>
>> [1]
>> http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>>
>> --
>> +1 919 869 8849
>>
>>
>>
>> _______________________________________________
>> 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/20110411/97e0fc9c/attachment.htm>

From jchris.fillionr at kitware.com  Mon Apr 11 17:16:23 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Mon, 11 Apr 2011 13:16:23 -0400
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTimdkURS6Th1KF9iQFsE7PZajvikdg@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
	<4DA32C77.5070002@dkfz-heidelberg.de>
	<BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
	<BANLkTimdkURS6Th1KF9iQFsE7PZajvikdg@mail.gmail.com>
Message-ID: <BANLkTinPX+K9zFHKC0vbsZeHMa3uaJj_9Q@mail.gmail.com>

To answer Steve question, VTK-cmake folder is just placeholder that will
contain everything related VTK external project which are neither source or
build.

More exactly ...

<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-build
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-configure
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-done
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-download
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-gitinfo.txt
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-install
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-mkdir
<CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-patch

<CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-cfgcmd.txt
<CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-cfgcmd.txt.in
<CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-gitclone.cmake

Thanks
Jc


On Mon, Apr 11, 2011 at 1:09 PM, Steve Pieper <pieper at ibility.net> wrote:

> I'd also vote for the case where "VTK" means source directory (instead of
> using VTK-src).
>
> BTW, what goes in VTK-cmake/src ?  All I see now is timestamps and tmp
> files...
>
> -Steve
>
>
> On Mon, Apr 11, 2011 at 12:59 PM, Jean-Christophe Fillion-Robin <
> jchris.fillionr at kitware.com> wrote:
>
>> Hi Sasha,
>>
>> To clarify, when I wrote:
>>
>>  <CTK-SUPERBUILD>/VTK-build
>>  <CTK-SUPERBUILD>/VTK-cmake/src
>>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>>  <CTK-SUPERBUILD>/VTK
>>
>> It means:
>>
>>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>>  <CTK-SUPERBUILD>/VTK-cmake         # Directory where CMake store
>> timestamps, source ...
>>  <CTK-SUPERBUILD>/VTK               # Source directory
>>
>>
>>
>> Or should we use structure like this one instead:
>>
>>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>>  <CTK-SUPERBUILD>/VTK-cmake        # Directory where CMake store
>> timestamps, source ...
>>  <CTK-SUPERBUILD>/VTK-src                    # Source directory
>>
>>
>> What do you think ?
>>
>> I would prefer option 1) since I am more use to it ... where the source
>> directory match the project name.
>>
>> Thanks
>> Jc
>>
>> On Mon, Apr 11, 2011 at 12:29 PM, Sascha Zelzer <
>> s.zelzer at dkfz-heidelberg.de> wrote:
>>
>>>  Hi Jc,
>>>
>>> we use a similar structure for external projects in MITK, so +1 from me.
>>> I would only suggest a slight modification:
>>>
>>> Can we use
>>>
>>> <CTK-SUPERBUILD>/VTK-src
>>> <CTK-SUPERBUILD>/VTK-tmp
>>>
>>> instead of
>>>
>>>
>>> <CTK-SUPERBUILD>/VTK-cmake/src
>>> <CTK-SUPERBUILD>/VTK-cmake/tmp
>>>
>>> ?
>>>
>>> Thanks for taking care of this,
>>>
>>> Sascha
>>>
>>>
>>> On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
>>>
>>> Hi Folks,
>>>
>>> Using CTK as an external project in more and more project, the path
>>> length could be an issue on windows platform.
>>> Indeed, the path length on windows is limited to 260 characters. [1]
>>>
>>> *What motivates this change:*
>>>
>>> Such problem could arise, if, for example, your project is build in
>>> folder like:
>>>
>>> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>>>
>>>
>>> "YourProject" relying also on Superbuild and using CTK as an external
>>> project .. will fail to build for some obscure reason.
>>>
>>>
>>> *Current CTK organization:*
>>>
>>> Currently the project are organized as described below:
>>>
>>>  <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
>>>  <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
>>> ...
>>>  <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
>>>  <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
>>> ...
>>>  <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
>>>  <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
>>> ...
>>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
>>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
>>> ...
>>>  <CTK-SUPERBUILD>/CTK-build
>>>
>>>
>>> *Solution proposed:*
>>>
>>> With some minor changes, the structure would like:
>>>
>>>  <CTK-SUPERBUILD>/CTK-build
>>>  <CTK-SUPERBUILD>/VTK
>>>  <CTK-SUPERBUILD>/VTK-build
>>>  <CTK-SUPERBUILD>/VTK-cmake/src
>>>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>>>  <CTK-SUPERBUILD>/VTK
>>>  <CTK-SUPERBUILD>/DCMTK-build
>>>  <CTK-SUPERBUILD>/DCMTK-cmake/src
>>>  <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>>>
>>> Pros:
>>>   - Doing so will decrease the average length of external project path
>>> associated with CTK.
>>>   - If needed, make the "cleaning" of external project easier "rm VTK*"
>>> instead of "cd" in each CMakeExternals sub folders ..
>>>
>>> *Action plan:*
>>>
>>> I plan to implement and test this change this coming week.
>>>
>>> That improvment shouldn't cause any issue, but If it happens to be a
>>> problem within your project and you require some time to figure out a fix or
>>> would like to contact me. Please, do it before the end of the week :)
>>>
>>> Next week, following your comments I will then integrate the change to
>>> CTK master.
>>>
>>> Thanks
>>> Jc
>>>
>>> [1]
>>> http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>>>
>>> --
>>> +1 919 869 8849
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>


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

From pieper at ibility.net  Mon Apr 11 17:18:30 2011
From: pieper at ibility.net (Steve Pieper)
Date: Mon, 11 Apr 2011 13:18:30 -0400
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTinPX+K9zFHKC0vbsZeHMa3uaJj_9Q@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
	<4DA32C77.5070002@dkfz-heidelberg.de>
	<BANLkTin+QUo89bPd0=t18-wojq=g8D9_8w@mail.gmail.com>
	<BANLkTimdkURS6Th1KF9iQFsE7PZajvikdg@mail.gmail.com>
	<BANLkTinPX+K9zFHKC0vbsZeHMa3uaJj_9Q@mail.gmail.com>
Message-ID: <BANLkTi=FszqZqaOj+2RNQkFRNEKd8w4gKA@mail.gmail.com>

Okay - I see - the stamp are in the src directory - looks good.

And thanks for doing the re-org!
-Steve

On Mon, Apr 11, 2011 at 1:16 PM, Jean-Christophe Fillion-Robin <
jchris.fillionr at kitware.com> wrote:

>
> To answer Steve question, VTK-cmake folder is just placeholder that will
> contain everything related VTK external project which are neither source or
> build.
>
> More exactly ...
>
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-build
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-configure
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-done
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-download
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-gitinfo.txt
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-install
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-mkdir
> <CTK-SUPERBUILD>/VTK-cmake/src/VTK-stamp/VTK-patch
>
> <CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-cfgcmd.txt
> <CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-cfgcmd.txt.in
> <CTK-SUPERBUILD>/VTK-cmake/tmp/VTK-gitclone.cmake
>
> Thanks
> Jc
>
>
>
> On Mon, Apr 11, 2011 at 1:09 PM, Steve Pieper <pieper at ibility.net> wrote:
>
>> I'd also vote for the case where "VTK" means source directory (instead of
>> using VTK-src).
>>
>> BTW, what goes in VTK-cmake/src ?  All I see now is timestamps and tmp
>> files...
>>
>> -Steve
>>
>>
>> On Mon, Apr 11, 2011 at 12:59 PM, Jean-Christophe Fillion-Robin <
>> jchris.fillionr at kitware.com> wrote:
>>
>>> Hi Sasha,
>>>
>>> To clarify, when I wrote:
>>>
>>>  <CTK-SUPERBUILD>/VTK-build
>>>  <CTK-SUPERBUILD>/VTK-cmake/src
>>>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>>>  <CTK-SUPERBUILD>/VTK
>>>
>>> It means:
>>>
>>>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>>>  <CTK-SUPERBUILD>/VTK-cmake         # Directory where CMake store
>>> timestamps, source ...
>>>  <CTK-SUPERBUILD>/VTK               # Source directory
>>>
>>>
>>>
>>> Or should we use structure like this one instead:
>>>
>>>  <CTK-SUPERBUILD>/VTK-build         # Build directory
>>>  <CTK-SUPERBUILD>/VTK-cmake        # Directory where CMake store
>>> timestamps, source ...
>>>  <CTK-SUPERBUILD>/VTK-src                    # Source directory
>>>
>>>
>>> What do you think ?
>>>
>>> I would prefer option 1) since I am more use to it ... where the source
>>> directory match the project name.
>>>
>>> Thanks
>>> Jc
>>>
>>> On Mon, Apr 11, 2011 at 12:29 PM, Sascha Zelzer <
>>> s.zelzer at dkfz-heidelberg.de> wrote:
>>>
>>>>  Hi Jc,
>>>>
>>>> we use a similar structure for external projects in MITK, so +1 from me.
>>>> I would only suggest a slight modification:
>>>>
>>>> Can we use
>>>>
>>>> <CTK-SUPERBUILD>/VTK-src
>>>> <CTK-SUPERBUILD>/VTK-tmp
>>>>
>>>> instead of
>>>>
>>>>
>>>> <CTK-SUPERBUILD>/VTK-cmake/src
>>>> <CTK-SUPERBUILD>/VTK-cmake/tmp
>>>>
>>>> ?
>>>>
>>>> Thanks for taking care of this,
>>>>
>>>> Sascha
>>>>
>>>>
>>>> On 04/11/2011 06:21 PM, Jean-Christophe Fillion-Robin wrote:
>>>>
>>>> Hi Folks,
>>>>
>>>> Using CTK as an external project in more and more project, the path
>>>> length could be an issue on windows platform.
>>>> Indeed, the path length on windows is limited to 260 characters. [1]
>>>>
>>>> *What motivates this change:*
>>>>
>>>> Such problem could arise, if, for example, your project is build in
>>>> folder like:
>>>>
>>>> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>>>>
>>>>
>>>> "YourProject" relying also on Superbuild and using CTK as an external
>>>> project .. will fail to build for some obscure reason.
>>>>
>>>>
>>>> *Current CTK organization:*
>>>>
>>>> Currently the project are organized as described below:
>>>>
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Build/VTK
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
>>>> ...
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Source/VTK
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
>>>> ...
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Download/VTK
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
>>>> ...
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
>>>>  <CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
>>>> ...
>>>>  <CTK-SUPERBUILD>/CTK-build
>>>>
>>>>
>>>> *Solution proposed:*
>>>>
>>>> With some minor changes, the structure would like:
>>>>
>>>>  <CTK-SUPERBUILD>/CTK-build
>>>>  <CTK-SUPERBUILD>/VTK
>>>>  <CTK-SUPERBUILD>/VTK-build
>>>>  <CTK-SUPERBUILD>/VTK-cmake/src
>>>>  <CTK-SUPERBUILD>/VTK-cmake/tmp
>>>>  <CTK-SUPERBUILD>/VTK
>>>>  <CTK-SUPERBUILD>/DCMTK-build
>>>>  <CTK-SUPERBUILD>/DCMTK-cmake/src
>>>>  <CTK-SUPERBUILD>/DCMTK-cmake/tmp
>>>>
>>>> Pros:
>>>>   - Doing so will decrease the average length of external project path
>>>> associated with CTK.
>>>>   - If needed, make the "cleaning" of external project easier "rm VTK*"
>>>> instead of "cd" in each CMakeExternals sub folders ..
>>>>
>>>> *Action plan:*
>>>>
>>>> I plan to implement and test this change this coming week.
>>>>
>>>> That improvment shouldn't cause any issue, but If it happens to be a
>>>> problem within your project and you require some time to figure out a fix or
>>>> would like to contact me. Please, do it before the end of the week :)
>>>>
>>>> Next week, following your comments I will then integrate the change to
>>>> CTK master.
>>>>
>>>> Thanks
>>>> Jc
>>>>
>>>> [1]
>>>> http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>>>>
>>>> --
>>>> +1 919 869 8849
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>
>
> --
> +1 919 869 8849
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20110411/40862173/attachment.htm>

From stephen.aylward at kitware.com  Mon Apr 11 17:22:57 2011
From: stephen.aylward at kitware.com (Stephen Aylward)
Date: Mon, 11 Apr 2011 13:22:57 -0400
Subject: [Ctk-developers] Coming changes in External project organization
In-Reply-To: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
References: <BANLkTinqXrLDkugngTOmgLqerHk+t0dNyA@mail.gmail.com>
Message-ID: <BANLkTi=6Voq8mztEjrQ3OV0S70iZEWLBoA@mail.gmail.com>

+1

We use this structure in TubeTK

s

On Mon, Apr 11, 2011 at 12:21 PM, Jean-Christophe Fillion-Robin
<jchris.fillionr at kitware.com> wrote:
> Hi Folks,
>
> Using CTK as an external project in more and more project, the path length
> could be an issue on windows platform.
> Indeed, the path length on windows is limited to 260 characters. [1]
>
> What motivates this change:
>
> Such problem could arise, if, for example, your project is build in folder
> like:
>
> "c:/Dashboards/Nightly/YourProject-Superbuild-Qt-PythonQt-With-Tcl-NoCLI-nightly"
>
> "YourProject" relying also on Superbuild and using CTK as an external
> project .. will fail to build for some obscure reason.
>
>
> Current CTK organization:
>
> Currently the project are organized as described below:
>
> ?<CTK-SUPERBUILD>/CMakeExternals/Build/VTK
> ?<CTK-SUPERBUILD>/CMakeExternals/Build/DCMTK
> ...
> ?<CTK-SUPERBUILD>/CMakeExternals/Source/VTK
> ?<CTK-SUPERBUILD>/CMakeExternals/Source/DCMTK
> ...
> ?<CTK-SUPERBUILD>/CMakeExternals/Download/VTK
> ?<CTK-SUPERBUILD>/CMakeExternals/Download/DCMTK
> ...
> ?<CTK-SUPERBUILD>/CMakeExternals/Stamp/VTK
> ?<CTK-SUPERBUILD>/CMakeExternals/Stamp/DCMTK
> ...
> ?<CTK-SUPERBUILD>/CTK-build
>
>
> Solution proposed:
>
> With some minor changes, the structure would like:
>
> ?<CTK-SUPERBUILD>/CTK-build
> ?<CTK-SUPERBUILD>/VTK
> ?<CTK-SUPERBUILD>/VTK-build
> ?<CTK-SUPERBUILD>/VTK-cmake/src
> ?<CTK-SUPERBUILD>/VTK-cmake/tmp
> ?<CTK-SUPERBUILD>/VTK
> ?<CTK-SUPERBUILD>/DCMTK-build
> ?<CTK-SUPERBUILD>/DCMTK-cmake/src
> ?<CTK-SUPERBUILD>/DCMTK-cmake/tmp
>
> Pros:
> ? - Doing so will decrease the average length of external project path
> associated with CTK.
> ? - If needed, make the "cleaning" of external project easier "rm VTK*"
> instead of "cd" in each CMakeExternals sub folders ..
>
> Action plan:
>
> I plan to implement and test this change this coming week.
>
> That improvment shouldn't cause any issue, but If it happens to be a problem
> within your project and you require some time to figure out a fix or would
> like to contact me. Please, do it before the end of the week :)
>
> Next week, following your comments I will then integrate the change to CTK
> master.
>
> Thanks
> Jc
>
> [1] http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx#maxpath
>
> --
> +1 919 869 8849
>
>
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>
>



-- 

==============================
Stephen R. Aylward, Ph.D.
Director of Medical Imaging Research
Kitware, Inc. - North Carolina Office
http://www.kitware.com
stephen.aylward (Skype)
(919) 969-6990 x300


From ppacch at yahoo.com  Tue Apr 12 09:04:09 2011
From: ppacch at yahoo.com (Pierre Pacchioni)
Date: Tue, 12 Apr 2011 02:04:09 -0700 (PDT)
Subject: [Ctk-developers] Compilation under Windows
Message-ID: <730065.6693.qm@web161512.mail.bf1.yahoo.com>

Hello,I'm trying to compile commontk under windows XP.I followed the instructions and I got an error with "git". Git is correctly installed on my system and I also set the GIT_EXECUTABLE variable
-- Building for: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008 -- works-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working CXX compiler using: Visual Studio 9 2008-- Check for working CXX compiler using: Visual Studio 9 2008 -- works-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Looking for Q_WS_X11-- Looking for Q_WS_X11 - not found.-- Looking for Q_WS_WIN-- Looking for Q_WS_WIN - found-- Looking for Q_WS_QWS-- Looking for Q_WS_QWS - not found.-- Looking for Q_WS_MAC-- Looking for Q_WS_MAC - not found.-- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)-- Generated: E:/workspace/c++/CTK/DGraphInput-alldep.txt-- Generated: E:/workspace/c++/CTK/DGraphInput-alldep-withext.txt-- Generated: E:/workspace/c++/CTK/DGraphInput.txt-- Generated: E:/workspace/c++/CTK/Project.xml-- Could NOT find
 Git (missing: ?GIT_EXECUTABLE)CMake Error at e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):??error: could not find git for clone of CTKDataCall Stack (most recent call first):??e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464 (_ep_add_download_command)??CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)??SuperBuild.cmake:144 (INCLUDE)??CMakeLists.txt:568 (INCLUDE)
git is installed:E:\workspace\c++\CTK>gitusage: git [--version] [--exec-path[=<path>]] [--html-path]?? ? ? ? ? [-p|--paginate|--no-pager] [--no-replace-objects]?? ? ? ? ? [--bare] [--git-dir=<path>] [--work-tree=<path>]?? ? ? ? ? [-c name=value] [--help]?? ? ? ? ? <command> [<args>]
The most commonly used git commands are:?? add ? ? ? ?Add file contents to the index?? bisect ? ? Find by binary search the change that introduced a bug?? branch ? ? List, create, or delete branches?? checkout ? Checkout a branch or paths to the working tree?? clone ? ? ?Clone a repository into a new directory?? commit ? ? Record changes to the repository?? diff ? ? ? Show changes between commits, commit and working tree, etc?? fetch ? ? ?Download objects and refs from another repository?? grep ? ? ? Print lines matching a pattern?? init ? ? ? Create an empty git repository or reinitialize an existing one?? log ? ? ? ?Show commit logs?? merge ? ? ?Join two or more development histories together?? mv ? ? ? ? Move or rename a file, a directory, or a symlink?? pull ? ? ? Fetch from and merge with another repository or a local branch?? push ? ? ? Update remote refs along with associated
 objects?? rebase ? ? Forward-port local commits to the updated upstream head?? reset ? ? ?Reset current HEAD to the specified state?? rm ? ? ? ? Remove files from the working tree and from the index?? show ? ? ? Show various types of objects?? status ? ? Show the working tree status?? tag ? ? ? ?Create, list, delete or verify a tag object signed with GPG
See 'git help <command>' for more information on a specific command.
What did I miss here??
On my pc?Windows XPE:\workspace\c++\CTK-superbuild>git --versiongit version 1.7.4.msysgit.0
E:\workspace\c++\CTK-superbuild>cmake --versioncmake version 2.8.4
Qt: 4.6.3
Thanks for your helpPierre.

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

From jchris.fillionr at kitware.com  Tue Apr 12 12:58:10 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Tue, 12 Apr 2011 08:58:10 -0400
Subject: [Ctk-developers] Compilation under Windows
In-Reply-To: <730065.6693.qm@web161512.mail.bf1.yahoo.com>
References: <730065.6693.qm@web161512.mail.bf1.yahoo.com>
Message-ID: <BANLkTinn7uyiNke+JgbO6hD35mYihbD3yw@mail.gmail.com>

Dear Pierre,

Thanks for your interest into CTK :)

Could you attach the files:
  - E:\workspace\c++\CTK-superbuild\CMakeCache.txt
  - E:\workspace\c++\CTK-superbuild\CTK-build/CMakeCache.txt

Out of curiosity, does the problem happen if you clone and build into
"E:\Workspace"  directly without the "c++"  subfolder?

Thanks
Jc

On Tue, Apr 12, 2011 at 5:04 AM, Pierre Pacchioni <ppacch at yahoo.com> wrote:

> Hello,
> I'm trying to compile commontk under windows XP.
> I followed the instructions and I got an error with "git". Git is correctly
> installed on my system and I also set the GIT_EXECUTABLE variable
>
> -- Building for: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008 -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler using: Visual Studio 9 2008
> -- Check for working CXX compiler using: Visual Studio 9 2008 -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Looking for Q_WS_X11
> -- Looking for Q_WS_X11 - not found.
> -- Looking for Q_WS_WIN
> -- Looking for Q_WS_WIN - found
> -- Looking for Q_WS_QWS
> -- Looking for Q_WS_QWS - not found.
> -- Looking for Q_WS_MAC
> -- Looking for Q_WS_MAC - not found.
> -- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)
> -- Generated: E:/workspace/c++/CTK/DGraphInput-alldep.txt
> -- Generated: E:/workspace/c++/CTK/DGraphInput-alldep-withext.txt
> -- Generated: E:/workspace/c++/CTK/DGraphInput.txt
> -- Generated: E:/workspace/c++/CTK/Project.xml
> -- Could NOT find Git (missing:  GIT_EXECUTABLE)
> CMake Error at e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):
>   error: could not find git for clone of CTKData
> Call Stack (most recent call first):
>   e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464
> (_ep_add_download_command)
>   CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)
>   SuperBuild.cmake:144 (INCLUDE)
>   CMakeLists.txt:568 (INCLUDE)
>
> git is installed:
> E:\workspace\c++\CTK>git
> usage: git [--version] [--exec-path[=<path>]] [--html-path]
>            [-p|--paginate|--no-pager] [--no-replace-objects]
>            [--bare] [--git-dir=<path>] [--work-tree=<path>]
>            [-c name=value] [--help]
>            <command> [<args>]
>
> The most commonly used git commands are:
>    add        Add file contents to the index
>    bisect     Find by binary search the change that introduced a bug
>    branch     List, create, or delete branches
>    checkout   Checkout a branch or paths to the working tree
>    clone      Clone a repository into a new directory
>    commit     Record changes to the repository
>    diff       Show changes between commits, commit and working tree, etc
>    fetch      Download objects and refs from another repository
>    grep       Print lines matching a pattern
>    init       Create an empty git repository or reinitialize an existing
> one
>    log        Show commit logs
>    merge      Join two or more development histories together
>    mv         Move or rename a file, a directory, or a symlink
>    pull       Fetch from and merge with another repository or a local
> branch
>    push       Update remote refs along with associated objects
>    rebase     Forward-port local commits to the updated upstream head
>    reset      Reset current HEAD to the specified state
>    rm         Remove files from the working tree and from the index
>    show       Show various types of objects
>    status     Show the working tree status
>    tag        Create, list, delete or verify a tag object signed with GPG
>
> See 'git help <command>' for more information on a specific command.
>
> What did I miss here?
>
> On my pc
> Windows XP
> E:\workspace\c++\CTK-superbuild>git --version
> git version 1.7.4.msysgit.0
>
> E:\workspace\c++\CTK-superbuild>cmake --version
> cmake version 2.8.4
>
> Qt: 4.6.3
>
> Thanks for your help
> Pierre.
>
>
>
> _______________________________________________
> 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/20110412/fb9be05e/attachment.htm>

From ppacch at yahoo.com  Tue Apr 12 13:22:45 2011
From: ppacch at yahoo.com (Pierre Pacchioni)
Date: Tue, 12 Apr 2011 06:22:45 -0700 (PDT)
Subject: [Ctk-developers] Compilation under Windows
Message-ID: <715936.59808.qm@web161508.mail.bf1.yahoo.com>

Hello JC,I tried without the c++ but it doesn't work either.At the end of the mail I put the complete trace from the git clone to the compilation (following the wiki instructions). I also attached the?E:\workspace\DCNS\CTK-superbuild\CMakeCache.txtThere is no file in the?E:\workspace\CTK-superbuild\CTK-build directory:
E:\workspace\DCNS\CTK-superbuild>cd CTK-build
E:\workspace\DCNS\CTK-superbuild\CTK-build>dir?Volume in drive E has no label.?Volume Serial Number is 3313-E672
?Directory of E:\workspace\DCNS\CTK-superbuild\CTK-build
04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?.04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?..04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?bin
ThanksPierre.
The complete trace of what I did from the clone to the compilation:
E:\workspace\DCNS>git clone http://github.com/commontk/CTK.gitCloning into CTK...remote: Counting objects: 20059, done.remote: Compressing objects: 100% (5819/5819), done.remote: Total 20059 (delta 14985), reused 18975 (delta 14014)Receiving objects: 100% (20059/20059), 4.70 MiB | 160 KiB/s, done.Resolving deltas: 100% (14985/14985), done.
E:\workspace\DCNS>dir?Volume in drive E has no label.?Volume Serial Number is 3313-E672
?Directory of E:\workspace\DCNS
04/12/2011 ?03:11 PM ? ?<DIR> ? ? ? ? ?.04/12/2011 ?03:11 PM ? ?<DIR> ? ? ? ? ?..04/12/2011 ?03:12 PM ? ?<DIR> ? ? ? ? ?CTK01/16/2011 ?06:09 PM ? ?<DIR> ? ? ? ? ?gsoap-2.8?? ? ? ? ? ? ? 0 File(s) ? ? ? ? ? ? ?0 bytes?? ? ? ? ? ? ? 4 Dir(s) ?93,668,347,904 bytes free
E:\workspace\DCNS>mkdir CTK-superbuild
E:\workspace\DCNS>cd CTK-superbuild
E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK-- Building for: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008 -- works-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working CXX compiler using: Visual Studio 9 2008-- Check for working CXX compiler using: Visual Studio 9 2008 -- works-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Looking for Q_WS_X11-- Looking for Q_WS_X11 - not found.-- Looking for Q_WS_WIN-- Looking for Q_WS_WIN - found-- Looking for Q_WS_QWS-- Looking for Q_WS_QWS - not found.-- Looking for Q_WS_MAC-- Looking for Q_WS_MAC - not found.-- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt-- Generated:
 E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml-- Could NOT find Git (missing: ?GIT_EXECUTABLE)CMake Error at e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):??error: could not find git for clone of CTKDataCall Stack (most recent call first):??e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464 (_ep_add_download_command)??CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)??SuperBuild.cmake:144 (INCLUDE)??CMakeLists.txt:568 (INCLUDE)

-- Configuring incomplete, errors occurred!
E:\workspace\DCNS\CTK-superbuild>


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

From jchris.fillionr at kitware.com  Tue Apr 12 13:45:55 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Tue, 12 Apr 2011 09:45:55 -0400
Subject: [Ctk-developers] Compilation under Windows
In-Reply-To: <715936.59808.qm@web161508.mail.bf1.yahoo.com>
References: <715936.59808.qm@web161508.mail.bf1.yahoo.com>
Message-ID: <BANLkTinzZ=xDV0f5M1E-sNQ6X62cSkQ7Ag@mail.gmail.com>

Hi,

Looking at CMakeCache.txt, the module FindGit failed to discover the
location of your installed git :(


[...]
//git command line client
GIT_EXECUTABLE:FILEPATH=GIT_EXECUTABLE-NOTFOUND
[...]


>From "E:\workspace\DCNS\CTK-superbuild>" , try the following command:

cmake ..\CTK -DGIT_EXECUTABLE:FILEPATH="E:/path/to/git.cmd"


Note the use of "/" instead of "\" .. doing so should avoid escaping issue ...

Let me know if that works ..

Jc

On Tue, Apr 12, 2011 at 9:22 AM, Pierre Pacchioni <ppacch at yahoo.com> wrote:

> Hello JC,
> I tried without the c++ but it doesn't work either.
> At the end of the mail I put the complete trace from the git clone to the
> compilation (following the wiki instructions). I also attached the
> E:\workspace\DCNS\CTK-superbuild\CMakeCache.txt
> There is no file in the E:\workspace\CTK-superbuild\CTK-build directory:
>
> E:\workspace\DCNS\CTK-superbuild>cd CTK-build
>
> E:\workspace\DCNS\CTK-superbuild\CTK-build>dir
>  Volume in drive E has no label.
>  Volume Serial Number is 3313-E672
>
>  Directory of E:\workspace\DCNS\CTK-superbuild\CTK-build
>
> 04/12/2011  03:13 PM    <DIR>          .
> 04/12/2011  03:13 PM    <DIR>          ..
> 04/12/2011  03:13 PM    <DIR>          bin
>
> Thanks
> Pierre.
>
> The complete trace of what I did from the clone to the compilation:
>
> E:\workspace\DCNS>git clone http://github.com/commontk/CTK.git
> Cloning into CTK...
> remote: Counting objects: 20059, done.
> remote: Compressing objects: 100% (5819/5819), done.
> remote: Total 20059 (delta 14985), reused 18975 (delta 14014)
> Receiving objects: 100% (20059/20059), 4.70 MiB | 160 KiB/s, done.
> Resolving deltas: 100% (14985/14985), done.
>
> E:\workspace\DCNS>dir
>  Volume in drive E has no label.
>  Volume Serial Number is 3313-E672
>
>  Directory of E:\workspace\DCNS
>
> 04/12/2011  03:11 PM    <DIR>          .
> 04/12/2011  03:11 PM    <DIR>          ..
> 04/12/2011  03:12 PM    <DIR>          CTK
> 01/16/2011  06:09 PM    <DIR>          gsoap-2.8
>                0 File(s)              0 bytes
>                4 Dir(s)  93,668,347,904 bytes free
>
> E:\workspace\DCNS>mkdir CTK-superbuild
>
> E:\workspace\DCNS>cd CTK-superbuild
>
> E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK
> -- Building for: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008 -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler using: Visual Studio 9 2008
> -- Check for working CXX compiler using: Visual Studio 9 2008 -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Looking for Q_WS_X11
> -- Looking for Q_WS_X11 - not found.
> -- Looking for Q_WS_WIN
> -- Looking for Q_WS_WIN - found
> -- Looking for Q_WS_QWS
> -- Looking for Q_WS_QWS - not found.
> -- Looking for Q_WS_MAC
> -- Looking for Q_WS_MAC - not found.
> -- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt
> -- Generated:
> E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml
> -- Could NOT find Git (missing:  GIT_EXECUTABLE)
> CMake Error at e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):
>   error: could not find git for clone of CTKData
> Call Stack (most recent call first):
>   e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464
> (_ep_add_download_command)
>   CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)
>   SuperBuild.cmake:144 (INCLUDE)
>   CMakeLists.txt:568 (INCLUDE)
>
>
> -- Configuring incomplete, errors occurred!
>
> E:\workspace\DCNS\CTK-superbuild>
>
>
>
>


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

From ppacch at yahoo.com  Tue Apr 12 14:02:46 2011
From: ppacch at yahoo.com (Pierre Pacchioni)
Date: Tue, 12 Apr 2011 07:02:46 -0700 (PDT)
Subject: [Ctk-developers] Compilation under Windows
Message-ID: <345507.33945.qm@web161513.mail.bf1.yahoo.com>

Hello JC,Thanks it works now:E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK -DGIT_EXECUTABLE:FILEPATH="E:/Program Files/Git/bin/git.exe"-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml-- Found Git: E:/Program Files/Git/bin/git.exe-- Configuring done-- Generating done-- Build files have been written to: E:/workspace/DCNS/CTK-superbuild
E:\workspace\DCNS\CTK-superbuild>
Strange, the variable and the path were correctly set. Anyway I can move forward now. I'm really interested by the plugin system you/commontk put in place and I'll investigate if and how I can use it in my Qt application.Thanks again for your helpPierre.
--- On Tue, 4/12/11, Pierre Pacchioni <ppacch at yahoo.com> wrote:

From: Pierre Pacchioni <ppacch at yahoo.com>
Subject: Re: [Ctk-developers] Compilation under Windows
To: jchris.fillionr at kitware.com
Cc: ctk-developers at commontk.org
Date: Tuesday, April 12, 2011, 9:22 AM

Hello JC,I tried without the c++ but it doesn't work either.At the end of the mail I put the complete trace from the git clone to the compilation (following the wiki instructions). I also attached the?E:\workspace\DCNS\CTK-superbuild\CMakeCache.txtThere is no file in the?E:\workspace\CTK-superbuild\CTK-build directory:
E:\workspace\DCNS\CTK-superbuild>cd CTK-build
E:\workspace\DCNS\CTK-superbuild\CTK-build>dir?Volume in drive E has no label.?Volume Serial Number is 3313-E672
?Directory of E:\workspace\DCNS\CTK-superbuild\CTK-build
04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?.04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?..04/12/2011 ?03:13 PM ? ?<DIR> ? ? ? ? ?bin
ThanksPierre.
The complete trace of what I did from the clone to the compilation:
E:\workspace\DCNS>git clone http://github.com/commontk/CTK.gitCloning into CTK...remote: Counting objects: 20059, done.remote: Compressing objects: 100% (5819/5819), done.remote: Total 20059 (delta 14985), reused 18975 (delta 14014)Receiving objects: 100% (20059/20059), 4.70 MiB | 160 KiB/s,
 done.Resolving deltas: 100% (14985/14985), done.
E:\workspace\DCNS>dir?Volume in drive E has no label.?Volume Serial Number is 3313-E672
?Directory of E:\workspace\DCNS
04/12/2011 ?03:11 PM ? ?<DIR> ? ? ? ? ?.04/12/2011 ?03:11 PM ? ?<DIR> ? ? ? ? ?..04/12/2011 ?03:12 PM ? ?<DIR> ? ? ? ? ?CTK01/16/2011 ?06:09 PM ? ?<DIR> ? ? ? ? ?gsoap-2.8?? ? ? ? ? ? ? 0 File(s) ? ? ? ? ? ? ?0 bytes?? ? ? ? ? ? ? 4 Dir(s) ?93,668,347,904 bytes free
E:\workspace\DCNS>mkdir CTK-superbuild
E:\workspace\DCNS>cd CTK-superbuild
E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK-- Building for: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008-- Check for working C compiler using: Visual Studio 9 2008 -- works-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working CXX compiler using: Visual Studio 9 2008-- Check for working CXX compiler using: Visual Studio 9 2008 -- works-- Detecting CXX compiler ABI info-- Detecting CXX compiler ABI info - done-- Looking for Q_WS_X11-- Looking for Q_WS_X11 - not found.-- Looking for Q_WS_WIN-- Looking for Q_WS_WIN -
 found-- Looking for Q_WS_QWS-- Looking for Q_WS_QWS - not found.-- Looking for Q_WS_MAC-- Looking for Q_WS_MAC - not found.-- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt-- Generated:
 E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt-- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml-- Could NOT find Git (missing: ?GIT_EXECUTABLE)CMake Error at e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):??error: could not find git for clone of CTKDataCall Stack (most recent call first):??e:/Program Files/CMake 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464 (_ep_add_download_command)??CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)??SuperBuild.cmake:144 (INCLUDE)??CMakeLists.txt:568 (INCLUDE)

-- Configuring incomplete, errors occurred!
E:\workspace\DCNS\CTK-superbuild>


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

From jchris.fillionr at kitware.com  Tue Apr 12 14:09:18 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Tue, 12 Apr 2011 10:09:18 -0400
Subject: [Ctk-developers] Compilation under Windows
In-Reply-To: <345507.33945.qm@web161513.mail.bf1.yahoo.com>
References: <345507.33945.qm@web161513.mail.bf1.yahoo.com>
Message-ID: <BANLkTinQE=-gX9m4=jBmPjAn9umTPi=WcA@mail.gmail.com>

Excellent :)

Regarding the plugin framework, you will find more information here:

   http://www.commontk.org/index.php/Documentation#Plugin_Framework


http://www.commontk.org/index.php/Documentation/CTK_Plugin_Framework:_Introduction

Any comments or suggestions to improve our documentation  / code are very
welcome.

Thanks
Jc


On Tue, Apr 12, 2011 at 10:02 AM, Pierre Pacchioni <ppacch at yahoo.com> wrote:

> Hello JC,
> Thanks it works now:
> E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK
> -DGIT_EXECUTABLE:FILEPATH="E:/Program Files/Git/bin/git.exe"
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt
> -- Generated:
> E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml
> -- Found Git: E:/Program Files/Git/bin/git.exe
> -- Configuring done
> -- Generating done
> -- Build files have been written to: E:/workspace/DCNS/CTK-superbuild
>
> E:\workspace\DCNS\CTK-superbuild>
>
> Strange, the variable and the path were correctly set. Anyway I can move
> forward now. I'm really interested by the plugin system you/commontk put in
> place and I'll investigate if and how I can use it in my Qt application.
> Thanks again for your help
> Pierre.
>
> --- On *Tue, 4/12/11, Pierre Pacchioni <ppacch at yahoo.com>* wrote:
>
>
> From: Pierre Pacchioni <ppacch at yahoo.com>
> Subject: Re: [Ctk-developers] Compilation under Windows
> To: jchris.fillionr at kitware.com
> Cc: ctk-developers at commontk.org
> Date: Tuesday, April 12, 2011, 9:22 AM
>
>
> Hello JC,
> I tried without the c++ but it doesn't work either.
> At the end of the mail I put the complete trace from the git clone to the
> compilation (following the wiki instructions). I also attached the
> E:\workspace\DCNS\CTK-superbuild\CMakeCache.txt
> There is no file in the E:\workspace\CTK-superbuild\CTK-build directory:
>
> E:\workspace\DCNS\CTK-superbuild>cd CTK-build
>
> E:\workspace\DCNS\CTK-superbuild\CTK-build>dir
>  Volume in drive E has no label.
>  Volume Serial Number is 3313-E672
>
>  Directory of E:\workspace\DCNS\CTK-superbuild\CTK-build
>
> 04/12/2011  03:13 PM    <DIR>          .
> 04/12/2011  03:13 PM    <DIR>          ..
> 04/12/2011  03:13 PM    <DIR>          bin
>
> Thanks
> Pierre.
>
> The complete trace of what I did from the clone to the compilation:
>
> E:\workspace\DCNS>git clone http://github.com/commontk/CTK.git
> Cloning into CTK...
> remote: Counting objects: 20059, done.
> remote: Compressing objects: 100% (5819/5819), done.
> remote: Total 20059 (delta 14985), reused 18975 (delta 14014)
> Receiving objects: 100% (20059/20059), 4.70 MiB | 160 KiB/s, done.
> Resolving deltas: 100% (14985/14985), done.
>
> E:\workspace\DCNS>dir
>  Volume in drive E has no label.
>  Volume Serial Number is 3313-E672
>
>  Directory of E:\workspace\DCNS
>
> 04/12/2011  03:11 PM    <DIR>          .
> 04/12/2011  03:11 PM    <DIR>          ..
> 04/12/2011  03:12 PM    <DIR>          CTK
> 01/16/2011  06:09 PM    <DIR>          gsoap-2.8
>                0 File(s)              0 bytes
>                4 Dir(s)  93,668,347,904 bytes free
>
> E:\workspace\DCNS>mkdir CTK-superbuild
>
> E:\workspace\DCNS>cd CTK-superbuild
>
> E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK
> -- Building for: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008
> -- Check for working C compiler using: Visual Studio 9 2008 -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working CXX compiler using: Visual Studio 9 2008
> -- Check for working CXX compiler using: Visual Studio 9 2008 -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Looking for Q_WS_X11
> -- Looking for Q_WS_X11 - not found.
> -- Looking for Q_WS_WIN
> -- Looking for Q_WS_WIN - found
> -- Looking for Q_WS_QWS
> -- Looking for Q_WS_QWS - not found.
> -- Looking for Q_WS_MAC
> -- Looking for Q_WS_MAC - not found.
> -- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt
> -- Generated:
> E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt
> -- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml
> -- Could NOT find Git (missing:  GIT_EXECUTABLE)
> CMake Error at e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):
>   error: could not find git for clone of CTKData
> Call Stack (most recent call first):
>   e:/Program Files/CMake
> 2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464
> (_ep_add_download_command)
>   CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)
>   SuperBuild.cmake:144 (INCLUDE)
>   CMakeLists.txt:568 (INCLUDE)
>
>
> -- Configuring incomplete, errors occurred!
>
> E:\workspace\DCNS\CTK-superbuild>
>
>
>
>


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

From s.zelzer at dkfz-heidelberg.de  Tue Apr 12 14:17:54 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Tue, 12 Apr 2011 16:17:54 +0200
Subject: [Ctk-developers] Compilation under Windows
In-Reply-To: <BANLkTinQE=-gX9m4=jBmPjAn9umTPi=WcA@mail.gmail.com>
References: <345507.33945.qm@web161513.mail.bf1.yahoo.com>
	<BANLkTinQE=-gX9m4=jBmPjAn9umTPi=WcA@mail.gmail.com>
Message-ID: <4DA45F12.8090505@dkfz-heidelberg.de>

Hi Pierre,

I've also been working on integrating the CTK PluginFramework into our 
toolkit and by doing so I improved some CTK CMake macros/functions to 
make it easier to integrate the framework in external projects. I hope 
to be able to push the changes during the next days, so if you run into 
some issues until then don't hesitate to contact us.

Thanks,
Sascha

On 04/12/2011 04:09 PM, Jean-Christophe Fillion-Robin wrote:
> Excellent :)
>
> Regarding the plugin framework, you will find more information here:
>
> http://www.commontk.org/index.php/Documentation#Plugin_Framework
>
> http://www.commontk.org/index.php/Documentation/CTK_Plugin_Framework:_Introduction
>
> Any comments or suggestions to improve our documentation  / code are 
> very welcome.
>
> Thanks
> Jc
>
>
> On Tue, Apr 12, 2011 at 10:02 AM, Pierre Pacchioni <ppacch at yahoo.com 
> <mailto:ppacch at yahoo.com>> wrote:
>
>     Hello JC,
>     Thanks it works now:
>     E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK
>     -DGIT_EXECUTABLE:FILEPATH="E:/Program Files/Git/bin/git.exe"
>     -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt
>     -- Generated:
>     E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt
>     -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt
>     -- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml
>     -- Found Git: E:/Program Files/Git/bin/git.exe
>     -- Configuring done
>     -- Generating done
>     -- Build files have been written to: E:/workspace/DCNS/CTK-superbuild
>
>     E:\workspace\DCNS\CTK-superbuild>
>
>     Strange, the variable and the path were correctly set. Anyway I
>     can move forward now. I'm really interested by the plugin system
>     you/commontk put in place and I'll investigate if and how I can
>     use it in my Qt application.
>     Thanks again for your help
>     Pierre.
>
>     --- On *Tue, 4/12/11, Pierre Pacchioni /<ppacch at yahoo.com
>     <mailto:ppacch at yahoo.com>>/*wrote:
>
>
>         From: Pierre Pacchioni <ppacch at yahoo.com
>         <mailto:ppacch at yahoo.com>>
>         Subject: Re: [Ctk-developers] Compilation under Windows
>         To: jchris.fillionr at kitware.com
>         <mailto:jchris.fillionr at kitware.com>
>         Cc: ctk-developers at commontk.org
>         <mailto:ctk-developers at commontk.org>
>         Date: Tuesday, April 12, 2011, 9:22 AM
>
>
>         Hello JC,
>         I tried without the c++ but it doesn't work either.
>         At the end of the mail I put the complete trace from the git
>         clone to the compilation (following the wiki instructions). I
>         also attached the E:\workspace\DCNS\CTK-superbuild\CMakeCache.txt
>         There is no file in the E:\workspace\CTK-superbuild\CTK-build
>         directory:
>
>         E:\workspace\DCNS\CTK-superbuild>cd CTK-build
>
>         E:\workspace\DCNS\CTK-superbuild\CTK-build>dir
>          Volume in drive E has no label.
>          Volume Serial Number is 3313-E672
>
>          Directory of E:\workspace\DCNS\CTK-superbuild\CTK-build
>
>         04/12/2011  03:13 PM <DIR>          .
>         04/12/2011  03:13 PM <DIR>          ..
>         04/12/2011  03:13 PM <DIR>          bin
>
>         Thanks
>         Pierre.
>
>         The complete trace of what I did from the clone to the
>         compilation:
>
>         E:\workspace\DCNS>git clone http://github.com/commontk/CTK.git
>         Cloning into CTK...
>         remote: Counting objects: 20059, done.
>         remote: Compressing objects: 100% (5819/5819), done.
>         remote: Total 20059 (delta 14985), reused 18975 (delta 14014)
>         Receiving objects: 100% (20059/20059), 4.70 MiB | 160 KiB/s, done.
>         Resolving deltas: 100% (14985/14985), done.
>
>         E:\workspace\DCNS>dir
>          Volume in drive E has no label.
>          Volume Serial Number is 3313-E672
>
>          Directory of E:\workspace\DCNS
>
>         04/12/2011  03:11 PM <DIR>          .
>         04/12/2011  03:11 PM <DIR>          ..
>         04/12/2011  03:12 PM <DIR>          CTK
>         01/16/2011  06:09 PM <DIR>          gsoap-2.8
>                        0 File(s)              0 bytes
>                        4 Dir(s)  93,668,347,904 bytes free
>
>         E:\workspace\DCNS>mkdir CTK-superbuild
>
>         E:\workspace\DCNS>cd CTK-superbuild
>
>         E:\workspace\DCNS\CTK-superbuild>cmake ..\CTK
>         -- Building for: Visual Studio 9 2008
>         -- Check for working C compiler using: Visual Studio 9 2008
>         -- Check for working C compiler using: Visual Studio 9 2008 --
>         works
>         -- Detecting C compiler ABI info
>         -- Detecting C compiler ABI info - done
>         -- Check for working CXX compiler using: Visual Studio 9 2008
>         -- Check for working CXX compiler using: Visual Studio 9 2008
>         -- works
>         -- Detecting CXX compiler ABI info
>         -- Detecting CXX compiler ABI info - done
>         -- Looking for Q_WS_X11
>         -- Looking for Q_WS_X11 - not found.
>         -- Looking for Q_WS_WIN
>         -- Looking for Q_WS_WIN - found
>         -- Looking for Q_WS_QWS
>         -- Looking for Q_WS_QWS - not found.
>         -- Looking for Q_WS_MAC
>         -- Looking for Q_WS_MAC - not found.
>         -- Found Qt-Version 4.6.3 (using E:/Qt/4.6.3/bin/qmake.exe)
>         -- Generated:
>         E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep.txt
>         -- Generated:
>         E:/workspace/DCNS/CTK-superbuild/DGraphInput-alldep-withext.txt
>         -- Generated: E:/workspace/DCNS/CTK-superbuild/DGraphInput.txt
>         -- Generated: E:/workspace/DCNS/CTK-superbuild/Project.xml
>         -- Could NOT find Git (missing:  GIT_EXECUTABLE)
>         CMake Error at e:/Program Files/CMake
>         2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1055 (message):
>           error: could not find git for clone of CTKData
>         Call Stack (most recent call first):
>           e:/Program Files/CMake
>         2.8/share/cmake-2.8/Modules/ExternalProject.cmake:1464
>         (_ep_add_download_command)
>           CMakeExternals/CTKData.cmake:19 (ExternalProject_Add)
>           SuperBuild.cmake:144 (INCLUDE)
>           CMakeLists.txt:568 (INCLUDE)
>
>
>         -- Configuring incomplete, errors occurred!
>
>         E:\workspace\DCNS\CTK-superbuild>
>
>
>
>
>
>
> -- 
> +1 919 869 8849
>

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

From s.zelzer at dkfz-heidelberg.de  Tue Apr 12 14:28:18 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Tue, 12 Apr 2011 16:28:18 +0200
Subject: [Ctk-developers] Documentation of CMake macros and functions
Message-ID: <4DA46182.6010609@dkfz-heidelberg.de>

Hi Folks,

I have always been a little bit annoyed by the lack of documentation for 
custom CMake macros and functions (both in our own projects and in CTK).

Doxygen supports the idea of so called "input filters" which take an 
input file and transform it into code which Doxygen can understand and 
parse. I wrote such an input filter for CMake files (see 
https://github.com/saschazelzer/CMakeDoxygenFilter/) and we are using it 
now in MITK. It allows you to document your CMake macros/functions 
inline using all of Doxygens commands.

For example, it looks like this: 
http://docs.mitk.org/nightly-qt4/namespaceCMake.html#aed923b6189222cc8f9800cbc3486d7f5
(we certainly still have a lot to do concerning the documentation of our 
macros... :-) )

I would like to integrate this stuff into CTK, any comments/suggestions?


Thanks,

Sascha


From jchris.fillionr at kitware.com  Tue Apr 12 14:39:54 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Tue, 12 Apr 2011 10:39:54 -0400
Subject: [Ctk-developers] Documentation of CMake macros and functions
In-Reply-To: <4DA46182.6010609@dkfz-heidelberg.de>
References: <4DA46182.6010609@dkfz-heidelberg.de>
Message-ID: <BANLkTikdxfLLjmzzLGo60i4FnFDWHK6MXw@mail.gmail.com>

You rocks :)  +1

We should definitively create the project: commontk/CMakeDoxygenFilter

Do you think you could some sort of simple unit test.
This would :
 - allow  us to make sure the filter is working
 - provide people with an example

Should the project CMakeDoxygenFilter be an external project of CTK if
doxygen is installed on the machine ?

How doxygen can be extended ? Should the filter be added to the path ?
Installed ?

Thanks
Jc

On Tue, Apr 12, 2011 at 10:28 AM, Sascha Zelzer <s.zelzer at dkfz-heidelberg.de
> wrote:

> Hi Folks,
>
> I have always been a little bit annoyed by the lack of documentation for
> custom CMake macros and functions (both in our own projects and in CTK).
>
> Doxygen supports the idea of so called "input filters" which take an input
> file and transform it into code which Doxygen can understand and parse. I
> wrote such an input filter for CMake files (see
> https://github.com/saschazelzer/CMakeDoxygenFilter/) and we are using it
> now in MITK. It allows you to document your CMake macros/functions inline
> using all of Doxygens commands.
>
> For example, it looks like this:
> http://docs.mitk.org/nightly-qt4/namespaceCMake.html#aed923b6189222cc8f9800cbc3486d7f5
> (we certainly still have a lot to do concerning the documentation of our
> macros... :-) )
>
> I would like to integrate this stuff into CTK, any comments/suggestions?
>
>
> Thanks,
>
> Sascha
> _______________________________________________
> 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/20110412/967892da/attachment.htm>

From s.zelzer at dkfz-heidelberg.de  Tue Apr 12 15:37:28 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Tue, 12 Apr 2011 17:37:28 +0200
Subject: [Ctk-developers] Documentation of CMake macros and functions
In-Reply-To: <BANLkTikdxfLLjmzzLGo60i4FnFDWHK6MXw@mail.gmail.com>
References: <4DA46182.6010609@dkfz-heidelberg.de>
	<BANLkTikdxfLLjmzzLGo60i4FnFDWHK6MXw@mail.gmail.com>
Message-ID: <4DA471B8.2090104@dkfz-heidelberg.de>

On 04/12/2011 04:39 PM, Jean-Christophe Fillion-Robin wrote:
> You rocks :)  +1
>
> We should definitively create the project: commontk/CMakeDoxygenFilter

Yes, we could do that. But we will probably not need a direct dependency 
to it (see comments below).

>
> Do you think you could some sort of simple unit test.
> This would :
>  - allow  us to make sure the filter is working
>  - provide people with an example

Good point. There is an example for a doxygen config file in the README.

>
> Should the project CMakeDoxygenFilter be an external project of CTK if 
> doxygen is installed on the machine ?
>
> How doxygen can be extended ? Should the filter be added to the path ? 
> Installed ?

The project contains a CMake function 
(https://github.com/saschazelzer/CMakeDoxygenFilter/blob/master/FunctionCMakeDoxygenFilterCompile.cmake) 
which is intended to be copied to the using project (CTK) and which 
should download the source code (it is just one cpp file) and compile it 
with TRY_COMPILE. This way, the documentation could be generated without 
building CTK first. Due to missing SSL support in CURL which ships with 
CMake (on Windows), downloading files from github is not possible (same 
issue as with the CDash driver script...). For MITK I copied the CMake 
function *and* the source code to MITK (I don't expect the source code 
to change very often).

After configuring CTK, the executable will have been built in the binary 
tree and Doxyfile.txt.in config file will be configured to contain a 
reference to the executable.

I don't know if we should invest the extra effort of creating another 
external project dependency to avoid the copying of the source file...

Thanks,
Sascha

>
> Thanks
> Jc
>
> On Tue, Apr 12, 2011 at 10:28 AM, Sascha Zelzer 
> <s.zelzer at dkfz-heidelberg.de <mailto:s.zelzer at dkfz-heidelberg.de>> wrote:
>
>     Hi Folks,
>
>     I have always been a little bit annoyed by the lack of
>     documentation for custom CMake macros and functions (both in our
>     own projects and in CTK).
>
>     Doxygen supports the idea of so called "input filters" which take
>     an input file and transform it into code which Doxygen can
>     understand and parse. I wrote such an input filter for CMake files
>     (see https://github.com/saschazelzer/CMakeDoxygenFilter/) and we
>     are using it now in MITK. It allows you to document your CMake
>     macros/functions inline using all of Doxygens commands.
>
>     For example, it looks like this:
>     http://docs.mitk.org/nightly-qt4/namespaceCMake.html#aed923b6189222cc8f9800cbc3486d7f5
>     (we certainly still have a lot to do concerning the documentation
>     of our macros... :-) )
>
>     I would like to integrate this stuff into CTK, any
>     comments/suggestions?
>
>
>     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/20110412/ab354e22/attachment.htm>

From mathieu.malaterre at gmail.com  Fri Apr 22 19:35:39 2011
From: mathieu.malaterre at gmail.com (Mathieu Malaterre)
Date: Fri, 22 Apr 2011 21:35:39 +0200
Subject: [Ctk-developers] CMake Error at
	Libs/ModuleDescription/CMakeLists.txt:55
	(ctkMacroGetTargetLibraries):
Message-ID: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>

Hi there,

  I am trying to build CTK (fresh rebuild). Does anyone knows why I am
getting the following error:

...
-- Found Threads: TRUE
-- Looking for bfd.h
-- Looking for bfd.h - found
-- CTKCore: libbfd is available [/usr/lib/libbfd.so]
CMake Error at Libs/ModuleDescription/CMakeLists.txt:55
(ctkMacroGetTargetLibraries):
  Unknown CMake command "ctkMacroGetTargetLibraries".


-- Configuring incomplete, errors occurred!
...


  I am using SuperBuild:ON

Thanks
-- 
Mathieu


From jchris.fillionr at kitware.com  Fri Apr 22 19:52:17 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Fri, 22 Apr 2011 15:52:17 -0400
Subject: [Ctk-developers] CMake Error at
 Libs/ModuleDescription/CMakeLists.txt:55 (ctkMacroGetTargetLibraries):
In-Reply-To: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>
References: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>
Message-ID: <BANLkTi=Ty+eZ+Hm6aVNvk3f2p6xd7EKjug@mail.gmail.com>

Hi Mathieu,

Which options are you using ?

I did the following and it compiles fine:

jchris at karakoram:~/Projects $ cd CTK
jchris at karakoram:~/Projects/CTK [? master] $ git pull commontk master
>From github.com:commontk/CTK
 * branch            master     -> FETCH_HEAD
Already up-to-date.
jchris at karakoram:~/Projects/CTK [? master] $ cd ../CTK-Test-build/
jchris at karakoram:~/Projects/CTK-Test-build $ rm -rf *
jchris at karakoram:~/Projects/CTK-Test-build $ *cmake
-DQT_QMAKE_EXECUTABLE:FILEPATH=/home/jchris/Projects/qtsdk-2010.05/qt/bin/qmake
../CTK*

[...]
-- Configuring done
*-- Generating done*
-- Build files have been written to: /home/jchris/Projects/CTK-Test-build
jchris at karakoram:~/Projects/CTK-Test-build $ *make -j5*

[...]

[100%] Built target CTKPluginFrameworkCppTests
[ 75%] No install step for 'CTK-build'
[ 75%] Completed 'CTK-build'
*[100%] Built target CTK-build*


Thanks
Jc




On Fri, Apr 22, 2011 at 3:35 PM, Mathieu Malaterre <
mathieu.malaterre at gmail.com> wrote:

> Hi there,
>
>  I am trying to build CTK (fresh rebuild). Does anyone knows why I am
> getting the following error:
>
> ...
> -- Found Threads: TRUE
> -- Looking for bfd.h
> -- Looking for bfd.h - found
> -- CTKCore: libbfd is available [/usr/lib/libbfd.so]
> CMake Error at Libs/ModuleDescription/CMakeLists.txt:55
> (ctkMacroGetTargetLibraries):
>  Unknown CMake command "ctkMacroGetTargetLibraries".
>
>
> -- Configuring incomplete, errors occurred!
> ...
>
>
>  I am using SuperBuild:ON
>
> Thanks
> --
> Mathieu
> _______________________________________________
> 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/20110422/b7b2c0a1/attachment.htm>

From jchris.fillionr at kitware.com  Fri Apr 22 21:51:29 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Fri, 22 Apr 2011 17:51:29 -0400
Subject: [Ctk-developers] Proposes changes - Directory renaming, removing,
	etc ...
Message-ID: <BANLkTikPz8vho4N-BNP3nE5N-4mKN91k=Q@mail.gmail.com>

Hi Folks,

Hope everything is going well :)

I will perform the following change:

  A) Comment the line adding CTK/Libs/ModuleDescription to CTK build system.
This later one doesn't compile

.. and I would like to perform the following changes:

 1) Delete CTK/Plugins/org.commontk.cli ("Interface that allows to discover
and manage CLI modules")
       => description is "Interface that allows to discover and manage CLI
modules"  (see servicedescriptor.xml)
       => Is that used ? Seems all classes are empty

 2) Rename CTK/Libs/PluginFramework  into CTK/Libs/Plugin/Framework

 3) Move CTK/Libs/ModuleDescription into more specialized subfolder
CTK/Libs/Plugin/Description
       => Classes would be rename into:
ctkPluginDescription[ExecutionInterface, Parameter, ParameterGroup... ]

Note also that:
   Enabling CTK_LIB_PluginDescription and CTK_LIB_PluginFramework could be
enabled independently


 4) Move plugin "CTK/Plugins/org_commontk_slicermodule" into for example
github.com/slicer/org_slicer_module  or some other project hosted on
github.com/slicer that could host all plugin and library specific to slicer.

Thanks
Jc



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

From jchris.fillionr at kitware.com  Fri Apr 22 22:01:05 2011
From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin)
Date: Fri, 22 Apr 2011 18:01:05 -0400
Subject: [Ctk-developers] CMake Error at
 Libs/ModuleDescription/CMakeLists.txt:55 (ctkMacroGetTargetLibraries):
In-Reply-To: <BANLkTi=Ty+eZ+Hm6aVNvk3f2p6xd7EKjug@mail.gmail.com>
References: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>
	<BANLkTi=Ty+eZ+Hm6aVNvk3f2p6xd7EKjug@mail.gmail.com>
Message-ID: <BANLkTi=FYk4ayHZrteYmwhY1ZN=dFJCBMQ@mail.gmail.com>

Hi Mathieu,

Thanks again for reporting the issue :)

Following commit
6f6fbb743<https://github.com/commontk/CTK/commit/6f6fbb743d8685565d1ed7cb631755b9dd1b9896>you
shouldn't experience problem building CTK from scratch.

To prevent similar problem from happening, I propose we add the following
options:
   CTK_LIBS_BUILD_ALL
   CTK_PLUGINS_BUILD_ALL
   CTK_APPLICATIONS_BUILD_ALL
   CTK_BUILD_ALL

These options will be added so that dashboard maintainers could easily
enable and test the complete toolkit.

Should there options be advanced ?

Thanks
Jc


On Fri, Apr 22, 2011 at 3:52 PM, Jean-Christophe Fillion-Robin <
jchris.fillionr at kitware.com> wrote:

> Hi Mathieu,
>
> Which options are you using ?
>
> I did the following and it compiles fine:
>
> jchris at karakoram:~/Projects $ cd CTK
> jchris at karakoram:~/Projects/CTK [? master] $ git pull commontk master
> From github.com:commontk/CTK
>  * branch            master     -> FETCH_HEAD
> Already up-to-date.
> jchris at karakoram:~/Projects/CTK [? master] $ cd ../CTK-Test-build/
> jchris at karakoram:~/Projects/CTK-Test-build $ rm -rf *
> jchris at karakoram:~/Projects/CTK-Test-build $ *cmake
> -DQT_QMAKE_EXECUTABLE:FILEPATH=/home/jchris/Projects/qtsdk-2010.05/qt/bin/qmake
> ../CTK*
>
> [...]
> -- Configuring done
> *-- Generating done*
> -- Build files have been written to: /home/jchris/Projects/CTK-Test-build
> jchris at karakoram:~/Projects/CTK-Test-build $ *make -j5*
>
> [...]
>
> [100%] Built target CTKPluginFrameworkCppTests
> [ 75%] No install step for 'CTK-build'
> [ 75%] Completed 'CTK-build'
> *[100%] Built target CTK-build*
>
>
> Thanks
> Jc
>
>
>
>
>
> On Fri, Apr 22, 2011 at 3:35 PM, Mathieu Malaterre <
> mathieu.malaterre at gmail.com> wrote:
>
>> Hi there,
>>
>>  I am trying to build CTK (fresh rebuild). Does anyone knows why I am
>> getting the following error:
>>
>> ...
>> -- Found Threads: TRUE
>> -- Looking for bfd.h
>> -- Looking for bfd.h - found
>> -- CTKCore: libbfd is available [/usr/lib/libbfd.so]
>> CMake Error at Libs/ModuleDescription/CMakeLists.txt:55
>> (ctkMacroGetTargetLibraries):
>>  Unknown CMake command "ctkMacroGetTargetLibraries".
>>
>>
>> -- Configuring incomplete, errors occurred!
>> ...
>>
>>
>>  I am using SuperBuild:ON
>>
>> Thanks
>> --
>> Mathieu
>> _______________________________________________
>> Ctk-developers mailing list
>> Ctk-developers at commontk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers
>>
>
>
>
> --
> +1 919 869 8849
>
>


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

From s.zelzer at dkfz-heidelberg.de  Mon Apr 25 08:54:29 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Mon, 25 Apr 2011 10:54:29 +0200
Subject: [Ctk-developers] CMake Error at
 Libs/ModuleDescription/CMakeLists.txt:55 (ctkMacroGetTargetLibraries):
In-Reply-To: <BANLkTi=FYk4ayHZrteYmwhY1ZN=dFJCBMQ@mail.gmail.com>
References: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>	<BANLkTi=Ty+eZ+Hm6aVNvk3f2p6xd7EKjug@mail.gmail.com>
	<BANLkTi=FYk4ayHZrteYmwhY1ZN=dFJCBMQ@mail.gmail.com>
Message-ID: <4DB536C5.30606@dkfz-heidelberg.de>

Hi Jc,

these options are really important and we should have added them much 
earlier, so +1 from me!

Thanks,

Sascha

On 04/23/2011 12:01 AM, Jean-Christophe Fillion-Robin wrote:
> Hi Mathieu,
>
> Thanks again for reporting the issue :)
>
> Following commit 6f6fbb743 
> <https://github.com/commontk/CTK/commit/6f6fbb743d8685565d1ed7cb631755b9dd1b9896> 
> you shouldn't experience problem building CTK from scratch.
>
> To prevent similar problem from happening, I propose we add the 
> following options:
>    CTK_LIBS_BUILD_ALL
>    CTK_PLUGINS_BUILD_ALL
>    CTK_APPLICATIONS_BUILD_ALL
>    CTK_BUILD_ALL
>
> These options will be added so that dashboard maintainers could easily 
> enable and test the complete toolkit.
>
> Should there options be advanced ?
>
> Thanks
> Jc
>
>
> On Fri, Apr 22, 2011 at 3:52 PM, Jean-Christophe Fillion-Robin 
> <jchris.fillionr at kitware.com <mailto:jchris.fillionr at kitware.com>> wrote:
>
>     Hi Mathieu,
>
>     Which options are you using ?
>
>     I did the following and it compiles fine:
>
>     jchris at karakoram:~/Projects $ cd CTK
>     jchris at karakoram:~/Projects/CTK [? master] $ git pull commontk master
>     From github.com:commontk/CTK
>      * branch            master     -> FETCH_HEAD
>     Already up-to-date.
>     jchris at karakoram:~/Projects/CTK [? master] $ cd ../CTK-Test-build/
>     jchris at karakoram:~/Projects/CTK-Test-build $ rm -rf *
>     jchris at karakoram:~/Projects/CTK-Test-build $ *cmake
>     -DQT_QMAKE_EXECUTABLE:FILEPATH=/home/jchris/Projects/qtsdk-2010.05/qt/bin/qmake
>     ../CTK*
>
>     [...]
>     -- Configuring done
>     *-- Generating done*
>     -- Build files have been written to:
>     /home/jchris/Projects/CTK-Test-build
>     jchris at karakoram:~/Projects/CTK-Test-build $ *make -j5*
>
>     [...]
>
>     [100%] Built target CTKPluginFrameworkCppTests
>     [ 75%] No install step for 'CTK-build'
>     [ 75%] Completed 'CTK-build'
>     *[100%] Built target CTK-build*
>
>
>     Thanks
>     Jc
>
>
>
>
>
>     On Fri, Apr 22, 2011 at 3:35 PM, Mathieu Malaterre
>     <mathieu.malaterre at gmail.com <mailto:mathieu.malaterre at gmail.com>>
>     wrote:
>
>         Hi there,
>
>          I am trying to build CTK (fresh rebuild). Does anyone knows
>         why I am
>         getting the following error:
>
>         ...
>         -- Found Threads: TRUE
>         -- Looking for bfd.h
>         -- Looking for bfd.h - found
>         -- CTKCore: libbfd is available [/usr/lib/libbfd.so]
>         CMake Error at Libs/ModuleDescription/CMakeLists.txt:55
>         (ctkMacroGetTargetLibraries):
>          Unknown CMake command "ctkMacroGetTargetLibraries".
>
>
>         -- Configuring incomplete, errors occurred!
>         ...
>
>
>          I am using SuperBuild:ON
>
>         Thanks
>         --
>         Mathieu
>         _______________________________________________
>         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 <tel:%2B1%20919%20869%208849>
>
>
>
>
> -- 
> +1 919 869 8849
>

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

From s.zelzer at dkfz-heidelberg.de  Mon Apr 25 09:39:26 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Mon, 25 Apr 2011 11:39:26 +0200
Subject: [Ctk-developers] Proposes changes - Directory renaming, removing,
 etc ...
In-Reply-To: <BANLkTikPz8vho4N-BNP3nE5N-4mKN91k=Q@mail.gmail.com>
References: <BANLkTikPz8vho4N-BNP3nE5N-4mKN91k=Q@mail.gmail.com>
Message-ID: <4DB5414E.4040102@dkfz-heidelberg.de>

Hi,

On 04/22/2011 11:51 PM, Jean-Christophe Fillion-Robin wrote:
> Hi Folks,
>
> Hope everything is going well :)
>
> I will perform the following change:
>
>   A) Comment the line adding CTK/Libs/ModuleDescription to CTK build 
> system. This later one doesn't compile
>
> .. and I would like to perform the following changes:
>
>  1) Delete CTK/Plugins/org.commontk.cli ("Interface that allows to 
> discover and manage CLI modules")
>        => description is "Interface that allows to discover and manage 
> CLI modules"  (see servicedescriptor.xml)
>        => Is that used ? Seems all classes are empty

Let's remove it. I never had time to finish it and would do it slightly 
different now anyway.

>
>  2) Rename CTK/Libs/PluginFramework  into CTK/Libs/Plugin/Framework
>
>  3) Move CTK/Libs/ModuleDescription into more specialized subfolder 
> CTK/Libs/Plugin/Description
>        => Classes would be rename into: 
> ctkPluginDescription[ExecutionInterface, Parameter, ParameterGroup... ]
>
> Note also that:
>    Enabling CTK_LIB_PluginDescription and CTK_LIB_PluginFramework 
> could be enabled independently
>

I think I understand what you are aiming for, but I am not really happy 
with the generic names. And if the two libraries are called 
"CTKPluginFramework" and "CTKPluginDescription", the names suggest a 
relationship where actually no relationship exists between the two 
(except that they both provide some kine of "extension mechanism").

What about:

CTK/Libs/ExtensionMechanisms/PluginFramework  ( will be called 
libCTKPluginFramework.so )
CTK/Libs/ExtensionMechanisms/CommandLineModule ( will be called 
libCTKCommandLineModule.so )

and rename the files to ctkCommandLineModule[ExecutionInterface, 
Parameter, ParameterGroup... ] ?

Let's also see what J2 and Xavier think.

>
>  4) Move plugin "CTK/Plugins/org_commontk_slicermodule" into for 
> example github.com/slicer/org_slicer_module 
> <http://github.com/slicer/org_slicer_module>  or some other project 
> hosted on github.com/slicer <http://github.com/slicer> that could host 
> all plugin and library specific to slicer.
>

I think for the CTK "Core Team", it would make things easier if 
org_commontk_slicermodule would stay where it is, for the time being 
(what would be your motivation for moving it?). I am thinking about 
possible refactorings and test and integration scenarios (other toolkits 
like MITK trying to use the org_commontk_slicermodule plugin). Until the 
code is "stable" the current form allows us to modify and test it more 
easily.


Thanks for cleaning up, and Happy Easter (to all who celebrate it) :-)

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

From mathieu.malaterre at gmail.com  Tue Apr 26 15:58:44 2011
From: mathieu.malaterre at gmail.com (Mathieu Malaterre)
Date: Tue, 26 Apr 2011 17:58:44 +0200
Subject: [Ctk-developers] CMake Error at
 Libs/ModuleDescription/CMakeLists.txt:55 (ctkMacroGetTargetLibraries):
In-Reply-To: <BANLkTi=FYk4ayHZrteYmwhY1ZN=dFJCBMQ@mail.gmail.com>
References: <BANLkTiki0VD7WWkHrzqsBzcHd+m2AGiH5g@mail.gmail.com>
	<BANLkTi=Ty+eZ+Hm6aVNvk3f2p6xd7EKjug@mail.gmail.com>
	<BANLkTi=FYk4ayHZrteYmwhY1ZN=dFJCBMQ@mail.gmail.com>
Message-ID: <BANLkTin96+xrTrK9wwB2AMNxeMEPBDOP8g@mail.gmail.com>

Hi JC

On Sat, Apr 23, 2011 at 12:01 AM, Jean-Christophe Fillion-Robin
<jchris.fillionr at kitware.com> wrote:
> Hi Mathieu,
>
> Thanks again for reporting the issue :)
>
> Following commit 6f6fbb743 you shouldn't experience problem building CTK
> from scratch.
>
> To prevent similar problem from happening, I propose we add the following
> options:
> ?? CTK_LIBS_BUILD_ALL
> ?? CTK_PLUGINS_BUILD_ALL
> ?? CTK_APPLICATIONS_BUILD_ALL
> ?? CTK_BUILD_ALL

This looks great but where is the documentation for setting up a
dashbaord machine ? I am looking at:

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

thanks again
-- 
Mathieu


From benoit.bleuze at inria.fr  Wed Apr 27 08:53:46 2011
From: benoit.bleuze at inria.fr (Benoit Bleuze)
Date: Wed, 27 Apr 2011 10:53:46 +0200 (CEST)
Subject: [Ctk-developers] CTK Hackfest in Europe: INRIA's proposal
In-Reply-To: <1633362088.744638.1303894407620.JavaMail.root@zmbs4.inria.fr>
Message-ID: <1714698113.744644.1303894426561.JavaMail.root@zmbs4.inria.fr>


Greetings to all! 


I don't have access to the other mailing list (the non developer's one), so if anyone who has access to it think it is advisable to diffuse this e-mail also to that other list, please do so. 


We already talked about INRIA's will to host a hackfest, and I have the pleasure to announce you that we precised our idea a little. 
I met the dkfz people last week in Nice, and already told them about the idea, and it's been received quite positively, and so I am doing the same proposition to a wider audience. 


We are organising an imaging workshop (among the VPH community) not so dissimilar to the one that preceded the hack fest back in Barcelona last year in our premises in Sophia Antipolis. 
Only this one will be centered around the interoperability of imaging tools. Of course interacting through CTK would be a way to answer that problem. 
And that would be a perfect occasion to squeeze a CTK hackfest right after it. Due to the publicity needed for the workshop, it cannot be done before summer, and Summer is a no go for many people, 
September and October have been deemed to busy because of the start of the academic year, and so November came out as a reasonable month. We were think of first or second week of November. 
Something like : and of first week for our workshop, and the following week for the hackfest, so that people wishing to attend both could do so. 
Of course, would some of you like even to attend the workshop, you would be very much welcome. 


My questions are the following: 
1- Are you all in favour of this happening in principle? 
2- Are the dates ok for you all, since initially it was supposed that a hack fest would be organised sooner in the year? 
3- Any remark or advice? 


I would like to add that last Friday we applied for a grant (a VPH seed exemplar project) for getting one person working on the interoperability of our (UPF, CNRS and INRIA's) imaging tools. 
And this proposal mentioned a possible interoperability using CTK as a translation layer (either using plugins, or message bus, or application hosting). The content of the workshop I mentioned already 
will depend on the success of the proposal, but the workshop will happen whatever the outcome. 
The only thing is that the work would be much more advanced if some engineer worked on interoperability full time in the 3 months prior to the workshop. 
If we can put together this workshop, the grant and the hackfest, real good things can happen to CTK. 


I am looking forward to seeing your opinion on this, 
Best wishes, 
Benoit. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ctk-developers/attachments/20110427/1f2dc897/attachment.htm>

From pieper at ibility.net  Wed Apr 27 21:55:58 2011
From: pieper at ibility.net (Steve Pieper)
Date: Wed, 27 Apr 2011 17:55:58 -0400
Subject: [Ctk-developers] CTK Hackfest in Europe: INRIA's proposal
In-Reply-To: <1714698113.744644.1303894426561.JavaMail.root@zmbs4.inria.fr>
References: <1633362088.744638.1303894407620.JavaMail.root@zmbs4.inria.fr>
	<1714698113.744644.1303894426561.JavaMail.root@zmbs4.inria.fr>
Message-ID: <BANLkTikUrVfOBGxqgH7011FUtiJd6sW9SQ@mail.gmail.com>

Hi Benoit - I'd love to attend such an event!

This is the right list for any discussion - so far ctk has been a hackers
organization, so the developers list is where all the action is :)

Your timing makes sense.  If we need an event sooner, we could consider
another US event in summertime.

Anyone else have thoughts or suggestions?

-Steve



On Wed, Apr 27, 2011 at 4:53 AM, Benoit Bleuze <benoit.bleuze at inria.fr>wrote:

> Greetings to all!
>
> I don't have access to the other mailing list (the non developer's one), so
> if anyone who has access to it think it is advisable to diffuse this e-mail
> also to that other list, please do so.
>
> We already talked about INRIA's will to host a hackfest, and I have the
> pleasure to announce you that we precised our idea a little.
> I met the dkfz people last week in Nice, and already told them about the
> idea, and it's been received quite positively, and so I am doing the same
> proposition to a wider audience.
>
> We are organising an imaging workshop (among the VPH community) not so
> dissimilar to the one that preceded the hack fest back in Barcelona last
> year in our premises in Sophia Antipolis.
> Only this one will be centered around the interoperability of imaging
> tools. Of course interacting through CTK would be a way to answer that
> problem.
> And that would be a perfect occasion to squeeze a CTK hackfest right after
> it. Due to the publicity needed for the workshop, it cannot be done before
> summer, and Summer is a no go for many people,
> September and October have been deemed to busy because of the start of the
> academic year, and so November came out as a reasonable month. We were think
> of first or second week of November.
> Something like : and of first week for our workshop, and the following week
> for the hackfest, so that people wishing to attend both could do so.
> Of course, would some of you like even to attend the workshop, you would be
> very much welcome.
>
> My questions are the following:
> 1- Are you all in favour of this happening in principle?
> 2- Are the dates ok for you all, since initially it was supposed that a
> hack fest would be organised sooner in the year?
> 3- Any remark or advice?
>
> I would like to add that last Friday we applied for a grant (a VPH seed
> exemplar project) for getting one person working on the interoperability of
> our (UPF, CNRS and INRIA's) imaging tools.
> And this proposal mentioned a possible interoperability using CTK as a
> translation layer (either using plugins, or message bus, or application
> hosting). The content of the workshop I mentioned already
> will depend on the success of the proposal, but the workshop will happen
> whatever the outcome.
> The only thing is that the work would be much more advanced if some
> engineer worked on interoperability full time in the 3 months prior to the
> workshop.
> If we can put together this workshop, the grant and the hackfest, real good
> things can happen to CTK.
>
> I am looking forward to seeing your opinion on this,
> Best wishes,
> Benoit.
>
> _______________________________________________
> 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/20110427/c7c4c116/attachment.htm>

From benoit.bleuze at inria.fr  Thu Apr 28 14:38:51 2011
From: benoit.bleuze at inria.fr (Benoit Bleuze)
Date: Thu, 28 Apr 2011 16:38:51 +0200 (CEST)
Subject: [Ctk-developers] Fwd:  CTK Hackfest in Europe: INRIA's proposal
In-Reply-To: <C9DEECF9.7590%h.p.meinzer@dkfz-heidelberg.de>
Message-ID: <1776432836.768186.1304001531837.JavaMail.root@zmbs4.inria.fr>


I am forwarding this e-mail to the list because only the cc-ed contacts received it.
Pitt/Pete/Piet/Peter, could you check that you are sending this e-mail with the same address you used when registering to the list?
I had the same problem on Tuesday when I tried to send this e-mail, and received no answer from any one, I checked the list's administration page,
and since our addresses at INRIA have changed in the past months my e-mail was silently rejected, I updated my address in the mailing list's settings and all was good as new.

The more hackfests the better I would say.
And I don't know if the breathtaking view and a catholic institutions are imperatives for you to find a reason to come, 
but we will host it on INRIA premises which don't have either of these crucial prerequisites, but the a good view is never far in the area.

Ben.


----- Forwarded Message -----
> From: "Meinzer Hans-Peter" <h.p.meinzer at dkfz-heidelberg.de>
> To: pieper at bwh.harvard.edu, "Benoit Bleuze" <benoit.bleuze at inria.fr>
> Cc: ctk-developers at commontk.org
> Sent: Thursday, 28 April, 2011 10:11:45 AM
> Subject: Re: [Ctk-developers] CTK Hackfest in Europe: INRIA's proposal
> Hi,
> 
> I just was in Nice for a meeting on standardized datasets and
> evaluation of algorithms. The solution to that is CTK with some small
> extentions. We were at a catholic study center which I can deeply
> recommend, the view is breathtaking.
> I suggest this hackfest PLUS another in summer in the US.
> Perhaps I can find a reason to join.
> 
> Pitt/Pete/Piet/Peter
> 
> Von: Steve Pieper <pieper at ibility.net<mailto:pieper at ibility.net>>
> Antworten an: "pieper at bwh.harvard.edu<mailto:pieper at bwh.harvard.edu>"
> <pieper at bwh.harvard.edu<mailto:pieper at bwh.harvard.edu>>
> Datum: Wed, 27 Apr 2011 23:55:58 +0200
> An: Benoit Bleuze
> <benoit.bleuze at inria.fr<mailto:benoit.bleuze at inria.fr>>
> Cc: "ctk-developers at commontk.org<mailto:ctk-developers at commontk.org>"
> <ctk-developers at commontk.org<mailto:ctk-developers at commontk.org>>
> Betreff: Re: [Ctk-developers] CTK Hackfest in Europe: INRIA's proposal
> 
> Hi Benoit - I'd love to attend such an event!
> 
> This is the right list for any discussion - so far ctk has been a
> hackers organization, so the developers list is where all the action
> is :)
> 
> Your timing makes sense. If we need an event sooner, we could consider
> another US event in summertime.
> 
> Anyone else have thoughts or suggestions?
> 
> -Steve
> 
> 
> 
> On Wed, Apr 27, 2011 at 4:53 AM, Benoit Bleuze
> <benoit.bleuze at inria.fr<mailto:benoit.bleuze at inria.fr>> wrote:
> Greetings to all!
> 
> I don't have access to the other mailing list (the non developer's
> one), so if anyone who has access to it think it is advisable to
> diffuse this e-mail also to that other list, please do so.
> 
> We already talked about INRIA's will to host a hackfest, and I have
> the pleasure to announce you that we precised our idea a little.
> I met the dkfz people last week in Nice, and already told them about
> the idea, and it's been received quite positively, and so I am doing
> the same proposition to a wider audience.
> 
> We are organising an imaging workshop (among the VPH community) not so
> dissimilar to the one that preceded the hack fest back in Barcelona
> last year in our premises in Sophia Antipolis.
> Only this one will be centered around the interoperability of imaging
> tools. Of course interacting through CTK would be a way to answer that
> problem.
> And that would be a perfect occasion to squeeze a CTK hackfest right
> after it. Due to the publicity needed for the workshop, it cannot be
> done before summer, and Summer is a no go for many people,
> September and October have been deemed to busy because of the start of
> the academic year, and so November came out as a reasonable month. We
> were think of first or second week of November.
> Something like : and of first week for our workshop, and the following
> week for the hackfest, so that people wishing to attend both could do
> so.
> Of course, would some of you like even to attend the workshop, you
> would be very much welcome.
> 
> My questions are the following:
> 1- Are you all in favour of this happening in principle?
> 2- Are the dates ok for you all, since initially it was supposed that
> a hack fest would be organised sooner in the year?
> 3- Any remark or advice?
> 
> I would like to add that last Friday we applied for a grant (a VPH
> seed exemplar project) for getting one person working on the
> interoperability of our (UPF, CNRS and INRIA's) imaging tools.
> And this proposal mentioned a possible interoperability using CTK as a
> translation layer (either using plugins, or message bus, or
> application hosting). The content of the workshop I mentioned already
> will depend on the success of the proposal, but the workshop will
> happen whatever the outcome.
> The only thing is that the work would be much more advanced if some
> engineer worked on interoperability full time in the 3 months prior to
> the workshop.
> If we can put together this workshop, the grant and the hackfest, real
> good things can happen to CTK.
> 
> I am looking forward to seeing your opinion on this,
> Best wishes,
> Benoit.
> 
> _______________________________________________
> 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


From s.zelzer at dkfz-heidelberg.de  Fri Apr 29 14:26:50 2011
From: s.zelzer at dkfz-heidelberg.de (Sascha Zelzer)
Date: Fri, 29 Apr 2011 16:26:50 +0200
Subject: [Ctk-developers] Documentation of CMake macros and functions
In-Reply-To: <4DA46182.6010609@dkfz-heidelberg.de>
References: <4DA46182.6010609@dkfz-heidelberg.de>
Message-ID: <4DBACAAA.4050305@dkfz-heidelberg.de>

Hi,

I just pushed the necessary changes for having CMake macros documented 
via Doxygen. You should be able to have a look at the doxygen output 
tomorrow, when the documentation has been regenerated.

Feel free to start writing outstanding documentation of your CMake code ;-)

- Sascha

On 04/12/2011 04:28 PM, Sascha Zelzer wrote:
> Hi Folks,
>
> I have always been a little bit annoyed by the lack of documentation for
> custom CMake macros and functions (both in our own projects and in CTK).
>
> Doxygen supports the idea of so called "input filters" which take an
> input file and transform it into code which Doxygen can understand and
> parse. I wrote such an input filter for CMake files (see
> https://github.com/saschazelzer/CMakeDoxygenFilter/) and we are using it
> now in MITK. It allows you to document your CMake macros/functions
> inline using all of Doxygens commands.
>
> For example, it looks like this:
> http://docs.mitk.org/nightly-qt4/namespaceCMake.html#aed923b6189222cc8f9800cbc3486d7f5
> (we certainly still have a lot to do concerning the documentation of our
> macros... :-) )
>
> I would like to integrate this stuff into CTK, any comments/suggestions?
>
>
> Thanks,
>
> Sascha
> _______________________________________________
> Ctk-developers mailing list
> Ctk-developers at commontk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers