[CMake] Cmake v2.8.0 ported to OS/2 - a question on DLL creation

[Paul Smedley]

Hi All,

Whilst it still needs more testing and the diffs definitely need 
tidying up, I've created an OS/2 port of cmake 2.8.0 - which is 
available for download from my site at http://os2ports.smedley.info

The actual diffs + os2.cmake file can be downloaded from 
http://smedley.info/cmake-2.8.0-os2-patches.zip 

One question - OS/2 has a limitation for shared libraries that they 
must have 8.3 filenames - can anyone think of a way to make this 
happen automagically in cmake?

I was thinking of some kind of check for shared library name > 8 
charaters long, then mangle a new name using some combination of the 
first xxx characters of the requested name, and the last yyy 
characters of the requested name to try and make sure the DLL name is 
unique.

Any suggestions?

-- 
Cheers,

Paul.

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] fftw-3.2.2 linking porblems to CMake 2.6

[Lucian Goron]

hello,

I use the ubuntu 9.04 jaunty jackalope along with other open source C++
libraries.
Recently I discovered the* fftw-3.2.2* libraries, but trying linking it is
harder then I thought.
Basically, I have to link these libraries *-lfftw3 -lm *but I do not know
how ?

Has somebody encountered this problem before ? *
*
Thank you in advance.*
*
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Compiler Test Failing on Windows 7

[Joe L]

Trying to open the solution file (trycompile generated) didn't work by double 
clicking on it, so I searched about that and found this:
http://www.pluralsight.com/community/blogs/matt/archive/2007/05/21/47446.aspx

this comment is the one that solved that for me:
"It works when you set both 
Launcher (C:\Program Files\Common Files\Microsoft
Shared\MSEnv\VSLauncher.exe) and IDE(C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE\devenv.exe) to run as administrator. 
(Right click .exe and select Propertries -> Compatibility, and choose Run as 
Administrator) 

Hope this helps.
"

After doing this I thought to set cmake as 'run as admin', and that seemed to 
get everything to generate as it should.

Thanks,
Joe





From: Bill Hoffman 
To: David Cole 
Cc: cmake@cmake.org
Sent: Tue, January 5, 2010 3:01:47 PM
Subject: Re: [CMake] Compiler Test Failing on Windows 7

David Cole wrote:
> On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler  > wrote:
> 
> Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L:
>  >   C:/Program Files (x86)/CMake
>  >  2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62
>  >  (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT)
> 
> You might want to avoid instal cmake in a path with spaces.
> I install software with unix layout to "C:\local"
> 
> 
> Nonsense. CMake works fine in a directory that has spaces in its name. We 
> wouldn't make the default installation directory on Windows have spaces in it 
> if it did have problems...
> 
> There must be something else going on here.
> 
> 

This has nothing to do with copy file not working.  The copy file is not 
working because no executable was generated for some reason.  You should look 
in CMakeError.log and CMakeOutput.log.  If that fails to show anything, then 
run cmake --debug-trycompile, then go into the CMakeFiles directory and run the 
build tool by hand and figure out why it is not producing executable files.

-Bill

-- Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake



  ___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] fftw-3.2.2 linking porblems to CMake 2.6

[Ryan Pavlik]

You should be able to do something like:

find_library(FFTW_LIBRARY
NAMES fftw3 fftw)
set(FFTW_LIBRARIES "${FFTW_LIBRARY}")
if(UNIX AND NOT WIN32)
find_library(FFTW_libm_LIBRARY
NAMES m)
list(APPEND FFTW_LIBRARIES "${FFTW_libm_LIBRARY}")
endif()

target_link_libraries(yourtargetname ${FFTW_LIBRARIES})

Ryan


On 01/06/2010 05:33 AM, Lucian Goron wrote:

hello,

I use the ubuntu 9.04 jaunty jackalope along with other open source 
C++ libraries.
Recently I discovered the/ fftw-3.2.2/ libraries, but trying linking 
it is harder then I thought.
Basically, I have to link these libraries /-lfftw3 -lm /but I do not 
know how ?


Has somebody encountered this problem before ? /
/
Thank you in advance./
/


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


--
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University

rpav...@iastate.edu
http://academic.cleardefinition.com
Internal VRAC/HCI Site: http://tinyurl.com/rpavlik

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Compiler Test Failing on Windows 7

[David Cole]

So it actually *was* a permissions issue after all...


On Wed, Jan 6, 2010 at 8:56 AM, Joe L  wrote:

> Trying to open the solution file (trycompile generated) didn't work by
> double clicking on it, so I searched about that and found this:
>
> http://www.pluralsight.com/community/blogs/matt/archive/2007/05/21/47446.aspx
>
> this comment is the one that solved that for me:
> "It works when you set both
> Launcher (C:\Program Files\Common Files\Microsoft
> Shared\MSEnv\VSLauncher.exe) and IDE(C:\Program Files\Microsoft Visual
> Studio 8\Common7\IDE\devenv.exe) to run as administrator.
> (Right click .exe and select Propertries -> Compatibility, and choose Run
> as Administrator)
>
> Hope this helps. "
>
> After doing this I thought to set cmake as 'run as admin', and that seemed
> to get everything to generate as it should.
>
> Thanks,
> Joe
>
> --
> *From:* Bill Hoffman 
> *To:* David Cole 
> *Cc:* cmake@cmake.org
> *Sent:* Tue, January 5, 2010 3:01:47 PM
>
> *Subject:* Re: [CMake] Compiler Test Failing on Windows 7
>
> David Cole wrote:
> > On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler <
> p...@hendrik-sattler.de > wrote:
> >
> >Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L:
> >  >  C:/Program Files (x86)/CMake
> >  >  2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62
> >  >  (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT)
> >
> >You might want to avoid instal cmake in a path with spaces.
> >I install software with unix layout to "C:\local"
> >
> >
> > Nonsense. CMake works fine in a directory that has spaces in its name. We
> wouldn't make the default installation directory on Windows have spaces in
> it if it did have problems...
> >
> > There must be something else going on here.
> >
> >
>
> This has nothing to do with copy file not working.  The copy file is not
> working because no executable was generated for some reason.  You should
> look in CMakeError.log and CMakeOutput.log.  If that fails to show anything,
> then run cmake --debug-trycompile, then go into the CMakeFiles directory and
> run the build tool by hand and figure out why it is not producing executable
> files.
>
> -Bill
>
> -- Bill Hoffman
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065
> bill.hoff...@kitware.com
> http://www.kitware.com
> 518 881-4905 (Direct)
> 518 371-3971 x105
> Fax (518) 371-4573
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] mingw crosscompile error: invalid option `macosx-version-min=10.5' ?

[Claus Klein]

Hi Alex,

The problem occurs always when I run cmake again, no matter of Windows  
or Windows-gcc is used.

But I found in CMakeCache.txt this UNINITIALIZED values.

claus-kleins-macbook-pro:build clausklein$ grep UNINITIALIZED  
CMakeCache.txt

CMAKE_CROSSCOMPILING:UNINITIALIZED=1
CMAKE_SYSTEM_NAME:UNINITIALIZED=Windows-gcc
claus-kleins-macbook-pro:build clausklein$

Perhaps this his the reason?

Claus

On 04.01.2010, at 19:22, Alexander Neundorf wrote:


On Sunday 03 January 2010, Claus Klein wrote:

I have problems to crosscompile on MAC-OS for MinGW.
How kann I prevent this strange compiler flag on a Darwin Plattform?

Thanks

Claus
-

cmake -DCMAKE_C_COMPILER=i386-mingw32-gcc -DCMAKE_CXX_COMPILER=i386-
mingw32-g++ --debug-trycompile --debug-output -
DCMAKE_SYSTEM_NAME=Windows-gcc ..


CMAKE_SYSTEM_NAME should be set to "Windows", not "Windows-gcc",  
because there

is not operating system "Windows-gcc" in cmake (it tries to load
Modules/Platform/${CMAKE_SYSTEM_NAME}.cmake).

In this case it should not load Darwin.cmake at all.

Does it work better if you do this ?

Alex


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] [BUG?] Setting environment variables with embedded blanks does not work with VERBATIM

[Alan W. Irwin]

On 2010-01-03 11:44-0800 Alan W. Irwin wrote:


[...]
COMMAND DUMMY=${CMAKE_CURRENT_BINARY_DIR} printenv DUMMY

This works fine if there are no embedded blanks in CMAKE_CURRENT_BINARY_DIR,
and the bash result of the above cmake COMMAND in a custom target is

DUMMY=/home/software/plplot_svn/HEAD/build_dir/examples printenv DUMMY

with the expected output

/home/software/plplot_svn/HEAD/build_dir/examples

However, if CMAKE_CURRENT_BINARY_DIR has an embedded blank, e.g.,

/home/software/plplot svn/HEAD/build_dir/examples

then the resulting generated command is

"DUMMY=/home/software/plplot svn/HEAD/build_dir/examples" printenv DUMMY

which gives the bash error

/bin/sh: DUMMY=/home/software/plplot svn/HEAD/build_dir/examples: No such
file or directory

because bash does not like quotes around variable assignment statements.

To solve this issue, VERBATIM should simply put the quotes around everything
after the equal sign when there are embedded blanks, e.g.,

DUMMY="/home/software/plplot svn/HEAD/build_dir/examples" printenv DUMMY

which I have verified works fine on the bash command line.  If the CMake
developers here agree that is a VERBATIM bug, I will write up the
appropriate bug report in the cmake bug tracker to keep track of the issue.


Response, please?

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__

Linux-powered Science
__
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake v2.8.0 ported to OS/2 - a question on DLL creation

[Bill Hoffman]

Paul Smedley wrote:

Hi All,

Whilst it still needs more testing and the diffs definitely need 
tidying up, I've created an OS/2 port of cmake 2.8.0 - which is 
available for download from my site at http://os2ports.smedley.info


The actual diffs + os2.cmake file can be downloaded from 
http://smedley.info/cmake-2.8.0-os2-patches.zip 

One question - OS/2 has a limitation for shared libraries that they 
must have 8.3 filenames - can anyone think of a way to make this 
happen automagically in cmake?


I was thinking of some kind of check for shared library name > 8 
charaters long, then mangle a new name using some combination of the 
first xxx characters of the requested name, and the last yyy 
characters of the requested name to try and make sure the DLL name is 
unique.


That might work   Another possibility is to leave this up to the 
project.  CMake could just warn and say you need to set a OUTPUT name on 
target N for this to work on OS/2.   I would imagine that there would be 
other changes for a project if you were porting to OS/2.



This is interesting work, I would be interested in incorporating it into 
CMake if you were willing to run a nightly OS/2 dashboard.  Would you be 
willing to do that?


-Bill

--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] [BUG?] Setting environment variables with embedded blanks does not work with VERBATIM

[Brad King]

On 1/3/2010 2:44 PM, Alan W. Irwin wrote:

The PLplot test system assumes bash (either normal bash or win-bash) is
available and uses environment variables specified on the command line.


CMake does not assume this.  We generate portable shell syntax.


To solve this issue, VERBATIM should simply put the quotes around
everything after the equal sign when there are embedded blanks, e.g.,

DUMMY="/home/software/plplot svn/HEAD/build_dir/examples" printenv DUMMY


The command has no special knowledge of this shell syntax extension.
There is now way for it to know how to do this.

VERBATIM is documented to quote each argument so that it parses into
an argv[] array exactly.  It is doing that.  This is not a bug.


is there some better way (other than the
above clumsy non-VERBATIM workaround) to deal with embedded blanks in bash
variable assignment statements?


VERBATIM COMMAND env DUMMY=${CMAKE_CURRENT_BINARY_DIR} printenv DUMMY
 ^^^ more portable version of syntax

-Brad
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake v2.8.0 ported to OS/2 - a question on DLL creation

[Bill Hoffman]

Bill Hoffman wrote:

Paul Smedley wrote:

Hi All,

Whilst it still needs more testing and the diffs definitely need 
tidying up, I've created an OS/2 port of cmake 2.8.0 - which is 
available for download from my site at http://os2ports.smedley.info


The actual diffs + os2.cmake file can be downloaded from 
http://smedley.info/cmake-2.8.0-os2-patches.zip
One question - OS/2 has a limitation for shared libraries that they 
must have 8.3 filenames - can anyone think of a way to make this 
happen automagically in cmake?


I was thinking of some kind of check for shared library name > 8 
charaters long, then mangle a new name using some combination of the 
first xxx characters of the requested name, and the last yyy 
characters of the requested name to try and make sure the DLL name is 
unique.


That might work   Another possibility is to leave this up to the 
project.  CMake could just warn and say you need to set a OUTPUT name on 
target N for this to work on OS/2.   I would imagine that there would be 
other changes for a project if you were porting to OS/2.


I wonder if you could use the same 8.3 mapping that windows uses?  Is 
there a library for that?



--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Mediawiki CMake syntax highlighting

[David Cole]

It has been put on the Kitware public wikis this morning... (includes the
CMake, VTK, ParaView, ITK wikis)

Please try it out and let us know if you see anything funky about it.


Thanks,
David Cole
Kitware, Inc.


On Tue, Jan 5, 2010 at 11:31 PM, David Doria  wrote:

> On Mon, Nov 30, 2009 at 8:17 AM, David Cole 
> wrote:
> > I forwarded it along... We'll see if it works good and let you know.
> >
>
> Just following up - any luck with this?
>
> Thanks,
>
> David
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] CMAKE_EXE_LINKER_FLAGS not a list?

[Gregory Peele ARA/CFD]

Hey all,

When tracking down why some custom linker flags weren't working right, I 
realized that CMAKE_EXE_LINKER flags (and its cousins for shared libraries) are 
not semicolon delimited lists but rather treat the flags as a single 
space-delimited string.  I also saw the closed bug report at 
http://public.kitware.com/Bug/view.php?id=7476 related to this issue.

I have adjusted my CMakeLists to work correctly given this behavior, but I'm 
wondering why this is the case, as the variable is semantically a list of 
linker arguments and I would intuitively expect the LIST commands to work 
properly with it.  Is it because it eventually gets stored in a target property 
which does not support list values?

Thanks,
Gregory Peele, Jr.
Applied Research Associates, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] mingw crosscompile error: invalid option `macosx-version-min=10.5' ?

[Alexander Neundorf]

On Wednesday 06 January 2010, Claus Klein wrote:
> Hi Alex,
>
> The problem occurs always when I run cmake again, no matter of Windows
> or Windows-gcc is used.
> But I found in CMakeCache.txt this UNINITIALIZED values.
>
> claus-kleins-macbook-pro:build clausklein$ grep UNINITIALIZED
> CMakeCache.txt
> CMAKE_CROSSCOMPILING:UNINITIALIZED=1
> CMAKE_SYSTEM_NAME:UNINITIALIZED=Windows-gcc
> claus-kleins-macbook-pro:build clausklein$
>
> Perhaps this his the reason?

You need to start from a fresh build tree from scratch.
And you need to use "Windows" as system name, otherwise it cannot work.

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMAKE_EXE_LINKER_FLAGS not a list?

[David Cole]

On Wed, Jan 6, 2010 at 2:18 PM, Gregory Peele ARA/CFD wrote:

>  Hey all,
>
>
>
> When tracking down why some custom linker flags weren't working right, I
> realized that CMAKE_EXE_LINKER flags (and its cousins for shared libraries)
> are not semicolon delimited lists but rather treat the flags as a single
> space-delimited string.  I also saw the closed bug report at
> http://public.kitware.com/Bug/view.php?id=7476 related to this issue.
>
>
>
> I have adjusted my CMakeLists to work correctly given this behavior, but
> I'm wondering why this is the case, as the variable is semantically a list
> of linker arguments and I would intuitively expect the LIST commands to work
> properly with it.  Is it because it eventually gets stored in a target
> property which does not support list values?
>
>
>
> Thanks,
>
> Gregory Peele, Jr.
>
> Applied Research Associates, Inc.
>


No special reason behind this quirk of behavior. It's just historical
remnants. Has to be kept the same for now for backwards compatibility.

If we were doing it over again, it would probably be a list.


HTH,
David
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] using cmake on windows - query on existing targets

[Chauhan, Vikas]

Hi, 

I am quite new to using cmake and at the moment I am trying to find my
way through it. 
I was wondering how we can query different targets on windows when using
cmake. 
For example: I may have a set of separate directories(each containing a
project) and from the top level root directory, I want to selectively
build a subset of projects.

How can I do it on the command line ? Also, can I query the list of
targets/projects from the command line?

Regards,
Vikas  

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Compiler Test Failing on Windows 7

[Gregory Peele ARA/CFD]

Let's stress that the source and binary directories of this build are readable 
and writable to Joe's account.  It is NOT a file permission issue for any files 
in our build tree.  If CMake or Visual Studio generate files outside of our 
source or binary tree all bets are off of course.

Given that Microsoft heavily recommends running Visual Studio 2005 as 
Administrator in both Vista and Windows 7 - it nags you each time you launch if 
you don't - and it also fails for Joe on non-CMake-generated solutions, I 
suspect the real problem is a bug in Visual Studio 2005 on Windows 7.

Has anyone on this list successfully built projects using Visual Studio 2005 on 
Windows 7 without marking CMake and Visual Studio to run as Administrator?  
Presumably what happens if CMake is not marked to run as Administrator, when it 
attempts the try-compile stage, it does not honor the "run as Administrator" 
marking on devenv or vcbuild or whatever process it uses, and then Visual 
Studio 2005 does naughty things and fails.

Given that we have a workaround we don't need to follow up any further, but if 
this is a general problem for anyone on Windows 7 there should probably be a 
bug report on it, right?

Gregory Peele, Jr.
Applied Research Associates, Inc.

From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
David Cole
Sent: Wednesday, January 06, 2010 10:34 AM
To: Joe L
Cc: cmake@cmake.org; Bill Hoffman
Subject: Re: [CMake] Compiler Test Failing on Windows 7

So it actually *was* a permissions issue after all...

On Wed, Jan 6, 2010 at 8:56 AM, Joe L 
mailto:superist_...@yahoo.com>> wrote:
Trying to open the solution file (trycompile generated) didn't work by double 
clicking on it, so I searched about that and found this:
http://www.pluralsight.com/community/blogs/matt/archive/2007/05/21/47446.aspx

this comment is the one that solved that for me:
"It works when you set both
Launcher (C:\Program Files\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe) 
and IDE(C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe) to 
run as administrator.
(Right click .exe and select Propertries -> Compatibility, and choose Run as 
Administrator)

Hope this helps. "

After doing this I thought to set cmake as 'run as admin', and that seemed to 
get everything to generate as it should.

Thanks,
Joe


From: Bill Hoffman mailto:bill.hoff...@kitware.com>>
To: David Cole mailto:david.c...@kitware.com>>
Cc: cmake@cmake.org
Sent: Tue, January 5, 2010 3:01:47 PM

Subject: Re: [CMake] Compiler Test Failing on Windows 7

David Cole wrote:
> On Tue, Jan 5, 2010 at 12:38 PM, Hendrik Sattler 
> mailto:p...@hendrik-sattler.de> 
> >> wrote:
>
>Am Dienstag 05 Januar 2010 14:09:00 schrieb Joe L:
>  >  C:/Program Files (x86)/CMake
>  >  2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:62
>  >  (CMAKE_DETERMINE_COMPILER_ABI) CMakeLists.txt:3 (PROJECT)
>
>You might want to avoid instal cmake in a path with spaces.
>I install software with unix layout to "C:\local"
>
>
> Nonsense. CMake works fine in a directory that has spaces in its name. We 
> wouldn't make the default installation directory on Windows have spaces in it 
> if it did have problems...
>
> There must be something else going on here.
>
>

This has nothing to do with copy file not working.  The copy file is not 
working because no executable was generated for some reason.  You should look 
in CMakeError.log and CMakeOutput.log.  If that fails to show anything, then 
run cmake --debug-trycompile, then go into the CMakeFiles directory and run the 
build tool by hand and figure out why it is not producing executable files.

-Bill

-- Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.kitware.com
518 881-4905 (Direct)
518 371-3971 x105
Fax (518) 371-4573
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using cmake on windows - query on existing targets

[John Drescher]

I am going to only answer 1 part of this.

> For example: I may have a set of separate directories(each containing a
> project) and from the top level root directory, I want to selectively build
> a subset of projects.
>
> How can I do it on the command line ?

I do this with a batch file. Each project configures an install.bat.in
file which generates a install.bat in a Build sudirectory of the
projects Build tree.

Here is an example for a project called LungAnalysis

Here is the install.bat.in
[x:\]type X:\CMakeBased\Qt\LungAnalysis\install.bat.in
devenv @project_binary_...@\@project_n...@.sln /build
@RELEASE_BUILD_NAME@ /project PACKAGE

Now the install.bat
[x:\]type X:\32Bit\VC.80\Qt\LungAnalysis\Batch\install.bat
devenv X:/32Bit/VC.80/Qt/LungAnalysis\LungAnalysis.sln /build
RelWithDebInfo /project PACKAGE

So then in a the root folder for the build trees for 32 bit vc2005
projects folder I have:

[x:\32bit\vc.80]type install_la.bat
call Lung\CT_Imaging\Batch\install.bat
call Lung\BZ_Airway\Batch\install.bat
call Lung\SCP_LS\Batch\install.bat
call Lung\JPU_Lobe\Batch\install.bat
call Qt\QtbasicUtils\Batch\install.bat
call Qt\LungAnalysis\Batch\install.bat

This builds all dependencies for the project by calling each projects
install.bat script.

I know this probably could be done in a more cross platform way but
this was pretty easy to implement on the platform I develop the most.
When I build on linux (not that often) I build each project manually.

John

John
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CMAKE_EXE_LINKER_FLAGS not a list?

[Gregory Peele ARA/CFD]

David,

Thanks for the info, I understand how that can happen sometimes.  Can this 
quirk be explicitly mentioned in the help documentation so that people like me 
aren't caught by surprise?  Actually I just noticed that 
CMAKE_SHARED_LINKER_FLAGS and CMAKE_MODULE_LINKER_FLAGS aren't in the official 
2.8 help documentation at all.

Thanks,
Gregory Peele, Jr.
Applied Research Associates, Inc.

From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, January 06, 2010 2:30 PM
To: Gregory Peele ARA/CFD
Cc: cmake@cmake.org
Subject: Re: [CMake] CMAKE_EXE_LINKER_FLAGS not a list?

On Wed, Jan 6, 2010 at 2:18 PM, Gregory Peele ARA/CFD 
mailto:gpe...@ara.com>> wrote:
Hey all,

When tracking down why some custom linker flags weren't working right, I 
realized that CMAKE_EXE_LINKER flags (and its cousins for shared libraries) are 
not semicolon delimited lists but rather treat the flags as a single 
space-delimited string.  I also saw the closed bug report at 
http://public.kitware.com/Bug/view.php?id=7476 related to this issue.

I have adjusted my CMakeLists to work correctly given this behavior, but I'm 
wondering why this is the case, as the variable is semantically a list of 
linker arguments and I would intuitively expect the LIST commands to work 
properly with it.  Is it because it eventually gets stored in a target property 
which does not support list values?

Thanks,
Gregory Peele, Jr.
Applied Research Associates, Inc.


No special reason behind this quirk of behavior. It's just historical remnants. 
Has to be kept the same for now for backwards compatibility.

If we were doing it over again, it would probably be a list.


HTH,
David

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] Fwd: Compiler Test Failing on Windows 7

[John Drescher]

On Wed, Jan 6, 2010 at 2:49 PM, Gregory Peele ARA/CFD  wrote:
> Let's stress that the source and binary directories of this build are
> readable and writable to Joe's account.  It is NOT a file permission issue
> for any files in our build tree.  If CMake or Visual Studio generate files
> outside of our source or binary tree all bets are off of course.
>
>
>
> Given that Microsoft heavily recommends running Visual Studio 2005 as
> Administrator in both Vista and Windows 7 - it nags you each time you launch
> if you don't - and it also fails for Joe on non-CMake-generated solutions, I
> suspect the real problem is a bug in Visual Studio 2005 on Windows 7.
>
>
>
> Has anyone on this list successfully built projects using Visual Studio 2005
> on Windows 7 without marking CMake and Visual Studio to run as
> Administrator?  Presumably what happens if CMake is not marked to run as
> Administrator, when it attempts the try-compile stage, it does not honor the
> "run as Administrator" marking on devenv or vcbuild or whatever process it
> uses, and then Visual Studio 2005 does naughty things and fails.
>

I am pretty sure I do that on a VM install of Win7 RC1. I was using
2005 but now I moved to 2008. I have not experienced this issue and I
am not logged in as the Admin however I am using family networking on
the VM.

John
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Mediawiki CMake syntax highlighting

[David Doria]

On Wed, Jan 6, 2010 at 1:16 PM, David Cole  wrote:
> It has been put on the Kitware public wikis this morning... (includes the
> CMake, VTK, ParaView, ITK wikis)
> Please try it out and let us know if you see anything funky about it.
>
> Thanks,
> David Cole
> Kitware, Inc.
>
> On Tue, Jan 5, 2010 at 11:31 PM, David Doria  wrote:
>>
>> On Mon, Nov 30, 2009 at 8:17 AM, David Cole 
>> wrote:
>> > I forwarded it along... We'll see if it works good and let you know.
>> >
>>
>> Just following up - any luck with this?
>>
>> Thanks,
>>
>> David
>
>

Excellent, it seems to work fine for the basic parts of cmake that I
commonly use. Thanks!

For anyone else interested, a comparison is here (I'll remove the
duplicate text-only in a few days):
http://www.vtk.org/Wiki/Distance_between_two_points

Looks much better to me! And no additional effort is required (i.e.
the manual syntax highlighting that was happening on many of the
Paraview pages)!

Thanks,

David D.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] mingw crosscompile error: invalid option `macosx-version-min=10.5' ?

[Claus Klein]

Yes, I did it again and again with rm -rf build.
Same result!

As I said: "The problem occurs always when I run cmake again, no  
matter of Windows or Windows-gcc is used."


Claus

On 06.01.2010, at 20:23, Alexander Neundorf wrote:


On Wednesday 06 January 2010, Claus Klein wrote:

Hi Alex,

The problem occurs always when I run cmake again, no matter of  
Windows

or Windows-gcc is used.
But I found in CMakeCache.txt this UNINITIALIZED values.

claus-kleins-macbook-pro:build clausklein$ grep UNINITIALIZED
CMakeCache.txt
CMAKE_CROSSCOMPILING:UNINITIALIZED=1
CMAKE_SYSTEM_NAME:UNINITIALIZED=Windows-gcc
claus-kleins-macbook-pro:build clausklein$

Perhaps this his the reason?


You need to start from a fresh build tree from scratch.
And you need to use "Windows" as system name, otherwise it cannot  
work.


Alex


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] [BUG?] Setting environment variables with embedded blanks does not work with VERBATIM

[Alan W. Irwin]

On 2010-01-06 12:48-0500 Brad King wrote:


VERBATIM COMMAND env DUMMY=${CMAKE_CURRENT_BINARY_DIR} printenv DUMMY
^^^ more portable version of syntax


Thanks very much for that suggestion for increasing shell syntax
portability. I just didn't have enough cross-shell experience to realize
dropping the "env" was a bashism.  Now you have drawn my attention to env, I
see it is well documented in man pages, "Unix in a Nutshell", etc., and I
see also that a VERBATIM add_custom_command works perfectly with the
"env" syntax.

Thanks, again!

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__

Linux-powered Science
__
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using cmake on windows - query on existing targets

[Alexander Neundorf]

On Wednesday 06 January 2010, Chauhan, Vikas wrote:
> Hi,
>
> I am quite new to using cmake and at the moment I am trying to find my
> way through it.
> I was wondering how we can query different targets on windows when using
> cmake.
> For example: I may have a set of separate directories(each containing a
> project) and from the top level root directory, I want to selectively
> build a subset of projects.

in KDE we have the macro
macro_optional_add_subdirectory()
http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/MacroOptionalAddSubdirectory.cmake?revision=940658&view=markup

E.g. if you do 
macro_optional_add_subdirectory(project1)

the subdir project1/ will be added like with normal add_subdirectory(), but 
additionally you'll have a cmake option "BUILD_project1", which you can 
enable and disable, and when disabled, the directory will not be added.

> How can I do it on the command line ? Also, can I query the list of
> targets/projects from the command line?

E.g. with the approach above, you can use cmake-gui or ccmake to have a look 
at the available options.

Does that help ?

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Compiler Test Failing on Windows 7

[Gregory Peele ARA/CFD]

Hey all,

See next two posts below discussing Admin issues on Vista and 7 that we had 
meant to put on the list at large.
As always, I greatly appreciate the responsiveness and helpfulness of the CMake 
developers and the people on this list.

Gregory Peele, Jr.
Applied Research Associates, Inc.

From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, January 06, 2010 4:19 PM
To: Gregory Peele ARA/CFD
Subject: Re: [CMake] Compiler Test Failing on Windows 7

I had meant to send that last reply to "all" including the list do you 
think I should resend it to the list as well or just let it be?

Sorry for this hassle. I wish there was something that CMake could do to make 
this easier to diagnose when it does happen...

On Wed, Jan 6, 2010 at 3:06 PM, Gregory Peele ARA/CFD 
mailto:gpe...@ara.com>> wrote:
David,

I completely agree with you, especially as I come from a Linux development 
background.  I personally use Vista and do not run as Admin, despite 
Microsoft's recommendation.  Joe is our development team's guinea pig for 
Windows 7 and it literally does not work for him without running as Admin, for 
any solution, CMake or no.  So I'm guessing an operation that Visual Studio 
2005 performs that was not privileged in Vista was made privileged in Windows 
7.  Or some other oddity like that.  It's certainly very unexpected, but other 
people have reported the same problem on a web search.  That is why I want to 
find out if someone else has ever successfully done this.

Gregory Peele, Jr.
Applied Research Associates, Inc.

From: David Cole [mailto:david.c...@kitware.com]
Sent: Wednesday, January 06, 2010 2:58 PM
To: Gregory Peele ARA/CFD

Subject: Re: [CMake] Compiler Test Failing on Windows 7

Child processes of CMake will run with whatever credentials CMake is given. 
Admin or non-admin.

So if you need VS to run as administrator, then you also need to run CMake as 
admin.

I personally avoid running anything as admin (including VS 2005 on Vista) 
unless there is absolutely a reason for me to do so.

Building C++ code with Visual Studio does *not* require admin privileges.

Registering ActiveX controls and perhaps some SQL server-y stuff probably does 
need VS running with admin privileges.

So it depends on your situation.

Avoid admin if you can, use it if you must.


HTH,
David


On Wed, Jan 6, 2010 at 2:49 PM, Gregory Peele ARA/CFD 
mailto:gpe...@ara.com>> wrote:
Let's stress that the source and binary directories of this build are readable 
and writable to Joe's account.  It is NOT a file permission issue for any files 
in our build tree.  If CMake or Visual Studio generate files outside of our 
source or binary tree all bets are off of course.

Given that Microsoft heavily recommends running Visual Studio 2005 as 
Administrator in both Vista and Windows 7 - it nags you each time you launch if 
you don't - and it also fails for Joe on non-CMake-generated solutions, I 
suspect the real problem is a bug in Visual Studio 2005 on Windows 7.

Has anyone on this list successfully built projects using Visual Studio 2005 on 
Windows 7 without marking CMake and Visual Studio to run as Administrator?  
Presumably what happens if CMake is not marked to run as Administrator, when it 
attempts the try-compile stage, it does not honor the "run as Administrator" 
marking on devenv or vcbuild or whatever process it uses, and then Visual 
Studio 2005 does naughty things and fails.

Given that we have a workaround we don't need to follow up any further, but if 
this is a general problem for anyone on Windows 7 there should probably be a 
bug report on it, right?

Gregory Peele, Jr.
Applied Research Associates, Inc.

From: cmake-boun...@cmake.org 
[mailto:cmake-boun...@cmake.org] On Behalf Of 
David Cole
Sent: Wednesday, January 06, 2010 10:34 AM
To: Joe L
Cc: cmake@cmake.org; Bill Hoffman

Subject: Re: [CMake] Compiler Test Failing on Windows 7

So it actually *was* a permissions issue after all...

On Wed, Jan 6, 2010 at 8:56 AM, Joe L 
mailto:superist_...@yahoo.com>> wrote:
Trying to open the solution file (trycompile generated) didn't work by double 
clicking on it, so I searched about that and found this:
http://www.pluralsight.com/community/blogs/matt/archive/2007/05/21/47446.aspx

this comment is the one that solved that for me:
"It works when you set both
Launcher (C:\Program Files\Common Files\Microsoft Shared\MSEnv\VSLauncher.exe) 
and IDE(C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe) to 
run as administrator.
(Right click .exe and select Propertries -> Compatibility, and choose Run as 
Administrator)

Hope this helps. "

After doing this I thought to set cmake as 'run as admin', and that seemed to 
get everything to generate as it should.

Thanks,
Joe


From: Bill Hoffman mailto:bill.hoff...@kitware.com>>
To: David Cole 

[CMake] Visual Studio Release / Debug with different link dependencies?

[Gregory Peele ARA/CFD]

Hi all,

While I'm hitting this list today I want to ask a question about dealing with 
multiple build configurations in Visual Studio with badly behaved third-party 
libraries.

I would like to be able - in the same binary directory / generated Solution - 
to build both Debug and Release builds of my project.  Some of the targets in 
my project depend on third-party libraries that absolutely must be linked to 
the same MSVRT as my project due to misuse of memory resources.  This implies 
that my target has to have different TARGET_LINK_LIBRARIES settings for Release 
and Debug, but the configuration choice is not made until we are in the VS IDE, 
long after CMake has generated the project.  There are also reasons this is 
desirable even when not strictly required by bad behavior of the third-party 
library.

It's easy enough to update Find scripts to find both debug and release settings 
of the same library (a la OpenSceneGraph or Qt) and our third-party directory 
structure would support that, but I have no idea if it's possible to specify 
configuration-specific link dependencies for Visual Studio that are correctly 
honored in the IDE.

Right now we have separate binary directories for Release and Debug builds of 
the project.   It works, but this greatly frustrates those on our team who are 
accustomed to Visual Studio workflow in a single Solution - of course, me being 
historically a Linux developer I didn't think anything of it.  It also means 
that the Debug configuration in the Release binary directory produces broken 
code, and vice-versa, which frequently costs us about 30 minutes when we 
accidentally build the wrong configuration without noticing because the IDE 
always defaults to Debug after project generation.

Any thoughts?

Thanks,
Gregory Peele, Jr.
Applied Research Associates, Inc.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using cmake on windows - query on existing targets

[Chauhan, Vikas]

> -Original Message-
> From: John Drescher [mailto:dresche...@gmail.com]
> Sent: 06 January 2010 19:57
> To: Chauhan, Vikas; CMake mailing list
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
> 
> I am going to only answer 1 part of this.
> 
> > For example: I may have a set of separate directories(each
containing a
> > project) and from the top level root directory, I want to
selectively build
> > a subset of projects.
> >
> > How can I do it on the command line ?
> 
> I do this with a batch file. Each project configures an install.bat.in
> file which generates a install.bat in a Build sudirectory of the
> projects Build tree.
> 
> Here is an example for a project called LungAnalysis
> 
> Here is the install.bat.in
> [x:\]type X:\CMakeBased\Qt\LungAnalysis\install.bat.in
> devenv @project_binary_...@\@project_n...@.sln /build
> @RELEASE_BUILD_NAME@ /project PACKAGE
> 
> Now the install.bat
> [x:\]type X:\32Bit\VC.80\Qt\LungAnalysis\Batch\install.bat
> devenv X:/32Bit/VC.80/Qt/LungAnalysis\LungAnalysis.sln /build
> RelWithDebInfo /project PACKAGE
> 
> So then in a the root folder for the build trees for 32 bit vc2005
> projects folder I have:
> 
> [x:\32bit\vc.80]type install_la.bat
> call Lung\CT_Imaging\Batch\install.bat
> call Lung\BZ_Airway\Batch\install.bat
> call Lung\SCP_LS\Batch\install.bat
> call Lung\JPU_Lobe\Batch\install.bat
> call Qt\QtbasicUtils\Batch\install.bat
> call Qt\LungAnalysis\Batch\install.bat
> 
> This builds all dependencies for the project by calling each projects
> install.bat script.
> 
> I know this probably could be done in a more cross platform way but
> this was pretty easy to implement on the platform I develop the most.
> When I build on linux (not that often) I build each project manually.
> 
> John
> 
> John

Thanks, however I was looking to do it in a path independent way. For
example by just using the directory/vcproj name from top build
directory. Please do correct me if I have not understood correctly.

Thanks,
Vikas
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using cmake on windows - query on existing targets

[Chauhan, Vikas]

> -Original Message-
> From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
> Sent: 06 January 2010 21:24
> To: cmake@cmake.org
> Cc: Chauhan, Vikas
> Subject: Re: [CMake] using cmake on windows - query on existing
targets
> 
> On Wednesday 06 January 2010, Chauhan, Vikas wrote:
> > Hi,
> >
> > I am quite new to using cmake and at the moment I am trying to find
my
> > way through it.
> > I was wondering how we can query different targets on windows when
using
> > cmake.
> > For example: I may have a set of separate directories(each
containing a
> > project) and from the top level root directory, I want to
selectively
> > build a subset of projects.
> 
> in KDE we have the macro
> macro_optional_add_subdirectory()
>
http://websvn.kde.org/trunk/KDE/kdelibs/cmake/modules/MacroOptionalAddSu
> bdirectory.cmake?revision=940658&view=markup
> 
> E.g. if you do
> macro_optional_add_subdirectory(project1)
> 
> the subdir project1/ will be added like with normal
add_subdirectory(), but
> additionally you'll have a cmake option "BUILD_project1", which you
can
> enable and disable, and when disabled, the directory will not be
added.
> 
> > How can I do it on the command line ? Also, can I query the list of
> > targets/projects from the command line?
> 
> E.g. with the approach above, you can use cmake-gui or ccmake to have
a look
> at the available options.
> 
> Does that help ?
> 
I think this is what I wanted. I will try and let you know.
Thanks,
Vikas

> Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] using cmake on windows - query on existing targets

[John Drescher]

> Thanks, however I was looking to do it in a path independent way. For
> example by just using the directory/vcproj name from top build
> directory. Please do correct me if I have not understood correctly.
>
With that method there are no hardcoded paths in the batch files. The
paths were generated by CMake

In my CMakeLists.txt for each project I have

configure_file (
"${PROJECT_SOURCE_DIR}/install.bat.in"
"${PROJECT_BINARY_DIR}/Batch/install.bat"
)

Either way I would try the other method first.. My method is not
crossplatform compatible and also requires more work to setup...

John
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake v2.8.0 ported to OS/2 - a question on DLL creation

[Paul Smedley]

Hi Bill,

On Wed, 6 Jan 2010 17:43:44 UTC, Bill Hoffman 
 wrote:

> Paul Smedley wrote:
> > Whilst it still needs more testing and the diffs definitely need 
> > tidying up, I've created an OS/2 port of cmake 2.8.0 - which is 
> > available for download from my site at http://os2ports.smedley.info
> > 
> > The actual diffs + os2.cmake file can be downloaded from 
> > http://smedley.info/cmake-2.8.0-os2-patches.zip 
> > 
> > One question - OS/2 has a limitation for shared libraries that they 
> > must have 8.3 filenames - can anyone think of a way to make this 
> > happen automagically in cmake?
> > 
> > I was thinking of some kind of check for shared library name > 8 
> > charaters long, then mangle a new name using some combination of the 
> > first xxx characters of the requested name, and the last yyy 
> > characters of the requested name to try and make sure the DLL name is 
> > unique.
> > 
> That might work   Another possibility is to leave this up to the 
> project.  CMake could just warn and say you need to set a OUTPUT name on 
> target N for this to work on OS/2.   I would imagine that there would be 
> other changes for a project if you were porting to OS/2.
Well actually - building Scribus hasn't needed any changes to the 
project cmake files - which is why I'd like to do it from within cmake
:)

> This is interesting work, I would be interested in incorporating it into 
> CMake if you were willing to run a nightly OS/2 dashboard.  Would you be 
> willing to do that?

What's required in running a 'nightly OS/2 dashboard' if it's not too 
complex, I'd be willing ot look at doing it.  I'd love to get the OS/2
stuff into the cmake repository as it makes building future versions 
much easier withough having to muck around with patches :)

-- 
Cheers,

Paul.

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Visual Studio Release / Debug with different link dependencies?

[Tyler Roscoe]

On Wed, Jan 06, 2010 at 09:58:12PM +, Gregory Peele ARA/CFD wrote:
> I would like to be able - in the same binary directory / generated
> Solution - to build both Debug and Release builds of my project.  Some

Look at the debug and optimized flags to target_link_libraries().

tyler
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Cmake v2.8.0 ported to OS/2 - a question on DLL creation

[Paul Smedley]

Hi Bill,

On Wed, 6 Jan 2010 17:52:26 UTC, Bill Hoffman 
 wrote:

> Bill Hoffman wrote:
> > Paul Smedley wrote:
> >> Hi All,
> >>
> >> Whilst it still needs more testing and the diffs definitely need 
> >> tidying up, I've created an OS/2 port of cmake 2.8.0 - which is 
> >> available for download from my site at http://os2ports.smedley.info
> >>
> >> The actual diffs + os2.cmake file can be downloaded from 
> >> http://smedley.info/cmake-2.8.0-os2-patches.zip
> >> One question - OS/2 has a limitation for shared libraries that they 
> >> must have 8.3 filenames - can anyone think of a way to make this 
> >> happen automagically in cmake?
> >>
> >> I was thinking of some kind of check for shared library name > 8 
> >> charaters long, then mangle a new name using some combination of the 
> >> first xxx characters of the requested name, and the last yyy 
> >> characters of the requested name to try and make sure the DLL name is 
> >> unique.
> >>
> > That might work   Another possibility is to leave this up to the 
> > project.  CMake could just warn and say you need to set a OUTPUT name on 
> > target N for this to work on OS/2.   I would imagine that there would be 
> > other changes for a project if you were porting to OS/2.
> > 
> I wonder if you could use the same 8.3 mapping that windows uses?  Is 
> there a library for that?

Windows does 8.3 mapping? Can you point to this in the cmake source?  
I wasn't aware of any windows restrictions of DLL filenames.

-- 
Cheers,

Paul.

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Visual Studio Release / Debug with different link dependencies?

[Ryan Pavlik]

Gregory,

This should "just work" - have you tried it?  Inside of the binary 
directory, you'll note that there are "INTDIR" subdirectories named 
after the build configs.


Ryan

On 01/06/2010 03:58 PM, Gregory Peele ARA/CFD wrote:


Hi all,

While I'm hitting this list today I want to ask a question about 
dealing with multiple build configurations in Visual Studio with badly 
behaved third-party libraries.


I would like to be able - in the same binary directory / generated 
Solution - to build both Debug and Release builds of my project.  Some 
of the targets in my project depend on third-party libraries that 
absolutely must be linked to the same MSVRT as my project due to 
misuse of memory resources.  This implies that my target has to have 
different TARGET_LINK_LIBRARIES settings for Release and Debug, but 
the configuration choice is not made until we are in the VS IDE, long 
after CMake has generated the project.  There are also reasons this is 
desirable even when not strictly required by bad behavior of the 
third-party library.



It's easy enough to update Find scripts to find both debug and release 
settings of the same library (a la OpenSceneGraph or Qt) and our 
third-party directory structure would support that, but I have no idea 
if it's possible to specify configuration-specific link dependencies 
for Visual Studio that are correctly honored in the IDE.


Right now we have separate binary directories for Release and Debug 
builds of the project.   It works, but this greatly frustrates those 
on our team who are accustomed to Visual Studio workflow in a single 
Solution - of course, me being historically a Linux developer I didn't 
think anything of it.  It also means that the Debug configuration in 
the Release binary directory produces broken code, and vice-versa, 
which frequently costs us about 30 minutes when we accidentally build 
the wrong configuration without noticing because the IDE always 
defaults to Debug after project generation.


Any thoughts?

Thanks,

Gregory Peele, Jr.

Applied Research Associates, Inc.


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


--
Ryan Pavlik
HCI Graduate Student
Virtual Reality Applications Center
Iowa State University

rpav...@iastate.edu
http://academic.cleardefinition.com
Internal VRAC/HCI Site: http://tinyurl.com/rpavlik

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Visual Studio Release / Debug with different link dependencies?

[Gregory Peele ARA/CFD]

Wow, I feel pretty dumb now.   Somehow I just didn't notice those options to 
TARGET_LINK_LIBRARIES despite how many times I've looked at the documentation 
of that command.

Thanks guys!

Gregory Peele, Jr.
Applied Research Associates, Inc.

From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of 
Ryan Pavlik
Sent: Wednesday, January 06, 2010 5:05 PM
To: cmake@cmake.org
Subject: Re: [CMake] Visual Studio Release / Debug with different link 
dependencies?

Gregory,

This should "just work" - have you tried it?  Inside of the binary directory, 
you'll note that there are "INTDIR" subdirectories named after the build 
configs.

Ryan

On 01/06/2010 03:58 PM, Gregory Peele ARA/CFD wrote:
Hi all,

While I'm hitting this list today I want to ask a question about dealing with 
multiple build configurations in Visual Studio with badly behaved third-party 
libraries.

I would like to be able - in the same binary directory / generated Solution - 
to build both Debug and Release builds of my project.  Some of the targets in 
my project depend on third-party libraries that absolutely must be linked to 
the same MSVRT as my project due to misuse of memory resources.  This implies 
that my target has to have different TARGET_LINK_LIBRARIES settings for Release 
and Debug, but the configuration choice is not made until we are in the VS IDE, 
long after CMake has generated the project.  There are also reasons this is 
desirable even when not strictly required by bad behavior of the third-party 
library.

It's easy enough to update Find scripts to find both debug and release settings 
of the same library (a la OpenSceneGraph or Qt) and our third-party directory 
structure would support that, but I have no idea if it's possible to specify 
configuration-specific link dependencies for Visual Studio that are correctly 
honored in the IDE.

Right now we have separate binary directories for Release and Debug builds of 
the project.   It works, but this greatly frustrates those on our team who are 
accustomed to Visual Studio workflow in a single Solution - of course, me being 
historically a Linux developer I didn't think anything of it.  It also means 
that the Debug configuration in the Release binary directory produces broken 
code, and vice-versa, which frequently costs us about 30 minutes when we 
accidentally build the wrong configuration without noticing because the IDE 
always defaults to Debug after project generation.

Any thoughts?

Thanks,
Gregory Peele, Jr.
Applied Research Associates, Inc.





___

Powered by www.kitware.com



Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html



Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ



Follow this link to subscribe/unsubscribe:

http://www.cmake.org/mailman/listinfo/cmake



--

Ryan Pavlik

HCI Graduate Student

Virtual Reality Applications Center

Iowa State University



rpav...@iastate.edu

http://academic.cleardefinition.com

Internal VRAC/HCI Site: http://tinyurl.com/rpavlik
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

[CMake] error while stage install of crosscompiled binaries

[Claus Klein]

Hi

i want to install a cross compiled (build host is a MAC OS X) project  
to a temporary state dir to get an archive to distribute the binaries.
The target is win32 (mingw), compiled to be installed at c:/usr as  
CMAKE_INSTALL_PREFIX.

This prefix is used while compile the binaries, so I can't change it.

I think, that when I use DESTDIR while "make DESTDIR=/tmp/cmake   
install", the device (C:) should be removed before to use it as part  
of a path like this:


STRING(REGEX REPLACE "[A-Za-z:/]" "" CMAKE_INSTALL_PREFIX "$ 
{CMAKE_INSTALL_PREFIX}")


head cmake_install.cmake
# Install script for directory: /Users/clausklein/Workspace/c/libsmi/ 
trunk

#
# Set the install prefix
IF(NOT DEFINED CMAKE_INSTALL_PREFIX)
  SET(CMAKE_INSTALL_PREFIX "C:/usr")
ENDIF(NOT DEFINED CMAKE_INSTALL_PREFIX)
STRING(REGEX REPLACE "/$" "" CMAKE_INSTALL_PREFIX "$ 
{CMAKE_INSTALL_PREFIX}")

. . . .

As you can see,  PREFIX is appended to DESDIR without modification.  
which is wrong in this special case.
I am not sure if the file is wrong generated or called with wrong  
parameters?



Any ideas about this?

//regards

Claus
--

This happens on my Mac Os X:
claus-kleins-macbook-pro:build clausklein$ make DESTDIR=/tmp/cmake  
install

[ 30%] Built target smi
[ 34%] Built target smidiff
[ 87%] Built target smidump
[ 90%] Built target smilint
[ 94%] Built target smiquery
[100%] Built target smixlate
Install the project...
-- Install configuration: "Release"
CMake Error at cmake_install.cmake:31 (FILE):
  file cannot create directory:
  /tmp/cmake/Users/clausklein/Workspace/c/libsmi/trunk/build/C:/usr/ 
lib/pkgconfig.

  Maybe need administrative privileges.


make: *** [install] Error 1


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] CUDA, CMAKE, and an attempt to build nbody

[Brian Davis]

On Tue, Jan 5, 2010 at 12:23 PM, James Bigler  wrote:

>
>
>> I ask my self two questions:
>>
>> 1) Why is CUDA_NVCC_FLAGS not set to some default build setting that would
>> just work out of the box? - I get the answer to this question when I turn on
>> CUDA_VERBOSE_BUILD_MODE - It is being set under the hood.
>>
>
> I guess I don't understand your question.  The CUDA_NVCC_FLAGS are the
> flags used by all targets all the time.  Occasionally additional flags are
> added (such as -fPIC on certain systems as well as other flags) that make it
> work based on your individual project configuration.  It does work out of
> the box for many applications.
>

I am trying to remember what the issue here was.  I think it was that I
could not see all the build settings AND (this is important) at the time I
was using the dcmtk library and adding it to my project using
add_subdirectroy( whereever/dcmtk ).  DCMTK appears to force cmake backwards
compatibility version which if used with FindCuda messes up the build.  At
least this is what I was experiencing. I am patching dcmtk with:

diff -rupN dcmtk-3.5.4-original/CMakeLists.txt dcmtk-3.5.4/CMakeLists.txt
--- dcmtk-3.5.4-original/CMakeLists.txt2010-01-04 10:05:14.426524200
-0600
+++ dcmtk-3.5.4/CMakeLists.txt2010-01-02 10:38:17.792807400 -0600
@@ -8,9 +8,9 @@ ENDIF(NOT WIN32)

 # check required version of CMake
 CMAKE_MINIMUM_REQUIRED(VERSION 2.0)
-IF(CMAKE_BACKWARDS_COMPATIBILITY GREATER 2.0.6)
-  SET(CMAKE_BACKWARDS_COMPATIBILITY 2.0.6 CACHE STRING "Latest version of
CMake when this project was released." FORCE)
-ENDIF(CMAKE_BACKWARDS_COMPATIBILITY GREATER 2.0.6)
+#IF(CMAKE_BACKWARDS_COMPATIBILITY GREATER 2.0.6)
+#  SET(CMAKE_BACKWARDS_COMPATIBILITY 2.0.6 CACHE STRING "Latest version of
CMake when this project was released." FORCE)
+#ENDIF(CMAKE_BACKWARDS_COMPATIBILITY GREATER 2.0.6)

 # default build type
 SET(CMAKE_BUILD_TYPE RELEASE)


This question turned out as I wrote the email to be a rhetorical question /
documentation of my experience.  CUDA_NVCC_FLAGS does not appear in the
CMakeCache.txt (and I was expecting it to).  CUDA_NVCC_FLAGS and friends in
CMakeCache.txt:


//Semi-colon delimit multiple arguments.
CUDA_NVCC_FLAGS:STRING=

//Semi-colon delimit multiple arguments.
CUDA_NVCC_FLAGS_DEBUG:STRING=

//Semi-colon delimit multiple arguments.
CUDA_NVCC_FLAGS_MINSIZEREL:STRING=

//Semi-colon delimit multiple arguments.
CUDA_NVCC_FLAGS_RELEASE:STRING=

//Semi-colon delimit multiple arguments.
CUDA_NVCC_FLAGS_RELWITHDEBINFO:STRING=




>
>> 2) There is a CUDA_TOOLKIT_INCLUDE, but no CUDA_SDK_INCLUDE (or _LIB)...
>> why? (this would prevent ${CUDA_SDK_ROOT_DIR}/common/inc - see below)
>>
>>
> As you found out the include directories for the CUDA SDK are not supported
> by FindCUDA.  Those libraries and headers are designed to be used by the
> SDK, and not particularly by external packages.  That doesn't prevent you
> from doing so, but it was decided that because the CUDA SDK won't maintain
> backward compatibility and is only designed for the SDK that external use
> would not be supported by FindCUDA.  As a compromise I chose to have as a
> bare minimum a path to the SDK be supported for those who wished to poke in
> the SDK to find things such as libraries or header files.  There is
> documentation in the help files and in the FindCUDA.cmake file as well as
> examples of what to do with the CUDA_SDK_ROOT_DIR variable.
>
>

Yes it looks as though from 2.2 to 2.3 and 3.0_Beta_1 they (NVIDIA) added a
/C/ directory in the sdk and moved  bin, common, etc there.  If I could only
create a ClairVoyantFindCUDA to know of future changes such as these.

So lets say that I take CMake compresed as a zip file
cmake-2.8.0-win32-x86.zip and make it a part of my repository tree.  Not
installed in Windows using installer in an attempt to make the build
computer not dependent on anything except the source control tool
(subversion) and Visual Studio.  I also take the CUDA SDK and CUDA Toolkit
and put it in my tree after installing on build computer and ziping contents
at C:\cuda and C:\Nvidia Corporation\.  Then I uninstall the sdk and
toolkit.  After preforming a clean install on a machine and diffing the
directory before and after. This *might* be possible with the follwing
exception:

01/06/2010  11:53 AM   151,552 nvRegDev.dll

So I was also experiencing, just today, that I am unable to get FindCUDA
working with PATHS specified or HINTS (if I am using it correctly):

find_package( PATHS paths... NO_DEFAULT_PATH)

>From FindCuda (with cmake now in my build tree so I can patch it):

  # Search in the CUDA_BIN_PATH first.
  find_path(CUDA_TOOLKIT_ROOT_DIR
NAMES nvcc nvcc.exe
PATHS ENV CUDA_BIN_PATH
DOC "Toolkit location."
NO_DEFAULT_PATH
)
  # Now search default paths
  find_path(CUDA_TOOLKIT_ROOT_DIR
NAMES nvcc nvcc.exe
PATHS /usr/local/bin
  /usr/local/cuda/bin
DOC "Toolkit location."
)

Following the advice from
http:

Re: [CMake] [New Module] FindCUDA

[Luke Parkinson]

Hello Everyone,

I apologise in advance if this is the wrong way to revive an old topic, but I 
wasn't sure how to reply to old threads in the mailing list and I'm new to this 
list.  I'm part of a team of developers looking at integrating CUDA into the 
Insight Toolkit (http://www.itk.org/). People subscribing to the mailing list 
over there might have heard from my colleague.  

Thanks to James Bigler and his FindCUDA.cmake module, we have been able to get 
CUDA and ITK to link into the executable, but we're having a similar problem to 
the previous post (included below just in case).  I have created several 'build 
environments' using this module with my own modifications that include the SDK 
(as an aside, can anyone point me in the direction of code that integrates C++ 
and CUDA without using cutil.h or cutil_inline.h?).  It works brilliantly with 
just the CUDA SDK, and the SDK plus our own C++ CUDA utility programs, but when 
we include the ITK in the configuration, building gives errors exactly like 
those above.  I've attached my modifications to the FindCUDA.cmake module (with 
a diff), and the 'CMakeLists.txt's we're using in the root and source 
directories.

We got the original FindCUDA.cmake from the svn repository, and based our code 
on the driver examples. When we add our own CUDA/C++ code (files omitted as 
code is still under development, permission is required), we get the same 
errors as mentioned previously, along the lines of 'warning: comparison between 
signed and unsigned integer expressions'.

Just including ITK (without our own code, using the provided driver code 
examples)
[Attached the corresponding files as ITKOnly_FindCUDA.cmake, 
ITKOnly_root_CMakeLists.txt, ITKOnly_src_CMakeLists.txt]
> make
[ 16%] Building NVCC (Device) object bin/./cuda_compile_generated_test_bin.cu.o
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
Scanning dependencies of target cuda_compile_example
[ 33%] Building CXX object bin/CMakeFiles/cuda_compile_example.dir/main.cc.o
Linking CXX executable cuda_compile_example
[ 33%] Built target cuda_compile_example
[ 50%] Building NVCC (Device) object bin/./test_lib_generated_test_lib.cu.o
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
Scanning dependencies of target test_lib
Linking CXX shared library libtest_lib.so
[ 50%] Built target test_lib
Scanning dependencies of target lib_example
[ 66%] Building CXX object bin/CMakeFiles/lib_example.dir/main_for_lib.cc.o
Linking CXX executable lib_example
[ 66%] Built target lib_example
[ 83%] Building NVCC (Device) object bin/./test_generated_test_bin.cu.o
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
cc1: warning: command line option "-Wno-deprecated" is valid for 
C++/Java/ObjC++ but not for C
cc1: warning: command line option "-ftemplate-depth-50" is valid for C++/ObjC++ 
but not for C
Scanning dependencies of target test
[100%] Building CXX object bin/CMakeFiles/test.dir/main.cc.o
Linking CXX executable test
[100%] Built target test

Any ideas or suggestions would be helpful.  This isn't crippling (only 
warnings), but it is annoying and could lead to problems later on if it has to 
do with how the CMake module deals with C/C++ code.  I also noticed with that 
same module that there are a few variables that don't seem to do anything.  The 
example I found was CUDA_INCLUDE_DIRECTORIES (deprecated by 
CUDA_INCLUDE_DIRS?).  I assume that svn version was the most up-to-date, please 
let me know if I am wrong.

Thank you for your help,

Luke

PS - The old thread is included below for context:

On Wed, Aug 26, 2009 at 2:36 PM, Luis Ibanez wrote:
> 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 compilation.
>> 3. It provides macros that setup the build rules to convert CUDA files
>> into object code or PTX files.
>> 4. It maintains source level dependencies.  If you change a file that
>> a CUDA file depends on, it will cause the CUDA file to recompile.
>>
>> Attached