Hi Darren,
Let me address first one of the issues that seems to
be making harder to track the real underlying problem.
The fact that ITK builds on Mac always
start to build from scratch.
We have observed this behavior in the continuous
builds in Mac Minis in the Dashboard:
htt
On Tue, Aug 25, 2009 at 2:11 PM, James Bigler wrote:
> This is code that is up for inclusion into the CMake Modules directory.
>
> FindCUDA does several things.
>
> 1. It locates all the build tools found in the NVIDIA CUDA toolkit and SDK.
> 2. It provides common options used to control CUDA code
Brad King wrote:
Luis Ibanez wrote:
If you have got this to work in your local build, please feel free
to commit the changes to ITK. In that way we can test them early
enough before the release of ITK 3.10.
[snip]
Brad for pointing me to this). I'm using CMake 2.6.1 - I THIN
Hi Rupert,
If you have got this to work in your local build, please feel free
to commit the changes to ITK. In that way we can test them early
enough before the release of ITK 3.10.
Please note that currently we only have one build testing an
installed version of ITK. This is done by building t
On a side note:
One of the (many) nice things about Open Source is that credits can
be identified in an objective manner. A pragmatic way of identifying the
developers of an open source system is to simply look at CVS logs.
There are several tools out there that harvest CVS logs and analyze
them.
Hi Gaetan,
I agree that it is an interesting feature to be able to run several tests
simultaneously.
It is true that *the large majority* of ITK tests do not depend on the
output from
previous tests. There are however some exceptions, for example, the hole
filling
filters apply their computation
Hi Fu,
You will find a paper on the use of ITK + MFC in the
Insight Journal:
http://insight-journal.org/dspace/handle/1926/479
"How to use ITK and MFC"
by Yong Su
If you find this paper useful, we will appreciate if
you add reviews to the paper.
In order to participate of the Open
