On 05/25/2011 11:40 PM, aaron_wri...@selinc.com wrote:
> I use mc.exe to generate an *.rc file and some headers for my program.
> The *.rc file is listed as an output of a custom command and as a source
> to an executable. During configuration CMake tells me it can't find a
> source file and lists
I use mc.exe to generate an *.rc file and some headers for my program. The
*.rc file is listed as an output of a custom command and as a source to an
executable. During configuration CMake tells me it can't find a source
file and lists the *.rc file. I've check the generated property of the
*.r
I've made some progress on debugging this issue. The ITK installation
I'm using was actually built as 32-bit libraries. The 64-bit machine
I used before defaulted to building/running as 32-bits. Now they're
being built as 64-bits, which is causing these issues.
Can I specify something in
On Wednesday 25 May 2011, David Cole wrote:
> I am happy to announce that CMake 2.8.5 has entered the release
> candidate stage! You can find the source and binaries here:
> http://www.cmake.org/files/v2.8/?C=M;O=D
>
> Following is the list of changes in this release. Please try this version
> of
I am happy to announce that CMake 2.8.5 has entered the release
candidate stage! You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Following is the list of changes in this release. Please try this version
of CMake on your projects and report any issues to the list
Johan,
I do not think there's a built-in way to make these warnings into errors...
It would be easy enough to do, but it's not there right now.
One reason is that most projects were developed with the understanding that
${uninitialized_variable} resolves to empty. Many projects even depend on
thi
On 05/25/2011 08:18 AM, sind...@gmail.com wrote:
> I also like your suggestion of having all source files in one directory
They don't actually have to be in one directory. You only need to name
them from one directory. For example:
add_executable(myMain
exe/mymain.f90
lib1/lib1.f90
Dear Brad,
Thanks for your thorough explanation, I wasn't aware that the
dependency scanning only worked within a single target, it makes sense now.
Currently I am using a UNIX Make files for building but we're moving to
CMake to have the application run on Windows as well. I have a
