Re: [CMake] cmake for cygwin

2010-10-26 Thread Bill Hoffman
On 10/26/2010 9:58 PM, Yaakov (Cygwin/X) wrote: On Tue, 2010-10-26 at 17:53 -0400, Bill Hoffman wrote: Backwards compatibility may not be important to you, but to CMake it is very important. When a developer chooses to use CMake, I want to respect that choice, and work as hard as I can to make

Re: [CMake] cmake for cygwin

2010-10-26 Thread Yaakov (Cygwin/X)
On Tue, 2010-10-26 at 17:53 -0400, Bill Hoffman wrote: > Backwards compatibility may not be important to you, but to CMake it is > very important. When a developer chooses to use CMake, I want to > respect that choice, and work as hard as I can to make sure I don't > break that code. CMake ha

[CMake] CMake hangs on new install

2010-10-26 Thread Phil Smith
This is driving me nuts, and it's almost certainly something dumb. One of my CMake users lost a hard drive and had to reimage. Now she's installed CMake 2.8 and it LOOKS like it's all OK, but any attempt to do a CMake hangs because the attempt to compile CMakeCCompilerId.c winds up passing a bu

Re: [CMake] cmake for cygwin

2010-10-26 Thread Bill Hoffman
So, I think the only way to fix this is to create a new policy. The policy will warn all cygwin builds that CMake is no longer defining WIN32 on cygwin. As with all policies, if a project has the minimum required CMake set to the version of CMake that implements the policy the new behavior wi

Re: [CMake] A question about cache variables

2010-10-26 Thread Michael Hertling
On 10/26/2010 08:47 PM, mina adel wrote: > > > Hi All, > I have a problem with cache variables in cmake. > > I want to check the combiler for a certain flag -C99 flag. So, I used the > following statement > CHECK_C_COMPILER_FLAG("-C99" FLAG_OK) > > The problem is that we I ran cmake for the fi

[CMake] A question about cache variables

2010-10-26 Thread mina adel
Hi All, I have a problem with cache variables in cmake. I want to check the combiler for a certain flag -C99 flag. So, I used the following statement CHECK_C_COMPILER_FLAG("-C99" FLAG_OK) The problem is that we I ran cmake for the first time it said that c99 is not found and set the FLAG_OK

[CMake] A question about cache variables

2010-10-26 Thread mina adel
Hi All, I have a problem with cache variables in cmake. I want to check the combiler for a certain flag -C99 flag. So, I used the following statement CHECK_C_COMPILER_FLAG("-C99" FLAG_OK) The problem is that we I ran cmake for the first time it said that c99 is not found and set the FLAG_OK v

Re: [CMake] cmake for cygwin

2010-10-26 Thread Yaakov (Cygwin/X)
On Tue, 2010-10-26 at 08:15 -0400, Bill Hoffman wrote: > At the end of the day, CMake should be following the majority of the > cygwin applications. However, I really don't want to break the code of > the people that have spent the time to get applications working on > cygwin with CMake over th

[CMake] Problem with custom target dependencies on VS2010

2010-10-26 Thread Ben Medina
Hi all, In our builds, we use custom targets to copy library headers to an include directory from which clients of the library then #include from. This works for VS2008 but is broken in VS2010 (using CMake 2.8.3 rc3). Here is a small example: --- CMakeLists.txt: -

Re: [CMake] cmake for cygwin

2010-10-26 Thread Bill Hoffman
On 10/24/2010 11:52 PM, Yaakov (Cygwin/X) wrote: On Fri, 2010-10-22 at 13:12 +, Rolf Eike Beer wrote: So this is only different from what other build tools or whatever do. But it is well known behaviour, it is documented, and it can't be changed for backward compatibility anyway. The only

Re: [CMake] include command

2010-10-26 Thread Michael Wild
Please always also reply to the list, such that other people can profit from the discussion. I can't tell you whether you should keep the lines or comment them out, that really depends on what they do and whether the code relies on them. You'll have to give a bit more information... Michael

Re: [CMake] CMake with CPack - unresolved libraries

2010-10-26 Thread Marcin Czenko
Hi Eric, I checked the link you sent me. It explains everything. Everything works perfectly now. Thanks for your help. Kind Regards, Marcin On 10/25/2010 10:35 PM, marcin.cze...@sioux.eu wrote: You may try to use full RPATH: http://www.cmake.org/Wiki/CMake_RPATH_handling However I have

Re: [CMake] CTest: use 'make -k' instead of 'make -i'

2010-10-26 Thread Marcel Loose
On Mon, 2010-10-25 at 17:30 +0200, Michael Wild wrote: > On 25. Oct, 2010, at 17:14 , Tyler Roscoe wrote: > > > On Mon, Oct 25, 2010 at 04:54:41PM +0200, Michael Wild wrote: > >> On 25. Oct, 2010, at 16:45 , Marcel Loose wrote: > >>> Wouldn't it make more sense to use 'make -k' instead? > >> > >

Re: [CMake] CTest: use 'make -k' instead of 'make -i'

2010-10-26 Thread Marcel Loose
On Mon, 2010-10-25 at 16:54 +0200, Michael Wild wrote: > On 25. Oct, 2010, at 16:45 , Marcel Loose wrote: > > > Hi all, > > > > I noticed that 'ctest -DExperimentalBuild' returns with an exit status > > 0, even if compiler errors occur. I think that is caused by the fact > > that 'make -i' is use

Re: [CMake] include command

2010-10-26 Thread Michael Wild
On 26. Oct, 2010, at 1:02 , sipxuser sipx wrote: > Dear all, > > I'm a newbie of cmake, and have some troubles in using the 'include' > command. I've already include the searching path into the env veriable PATH. > But each time running cmake, I always get follow error messages: > > CMake Erro