Re: [CMake] Why does cmake 2.4.0 (beta) compile header files?

At 05:27 PM 4/20/2006, Jan Woetzel wrote: >Jan Woetzel wrote: > Why does CMake version 2.4.0 cause VS7 to compile header files? >Sorry, my fault - that`s a different problem than mine. >- only Makefilw generators generate targets for .hh files here, >- VS7 is correctly ignoring them on build bu

Re: Fwd: [CMake] Why does cmake 2.4.0 (beta) compile header files?

Sort of funny, but the fix for the same name object file in two directories is the source of the problem. I have checked in a fix. Thanks for the report. -Bill At 05:43 PM 4/20/2006, Phillip Hellewell wrote: >Oops, I forgot to send this to the whole list instead of just to Brad. > >Phillip >

RE: [CMake] Visual Studio problem with many/long additional library paths

> > It would be helpful (at least in my case) to be able to turn off the > > production of the "OutDir" directories in this list, I just haven't > > gotten around to figuring out how. Is there a simple way to control > > this? > > Both directories are always added. This is hard-coded in the VS7

Re: [CMake] Why does cmake 2.4.0 (beta) compile header files?

Jan Woetzel wrote: Why does CMake version 2.4.0 cause VS7 to compile header files? Sorry, my fault - that`s a different problem than mine. - only Makefilw generators generate targets for .hh files here, - VS7 is correctly ignoring them on build but listing them in teh project files. See m

Re: [CMake] Why does cmake 2.4.0 (beta) compile header files?

Brad King wrote: Phillip Hellewell wrote: Why does CMake version 2.4.0 cause VS7 to compile header files? I cannot duplicate this problem. Please post a minimal example that Same problem here at least with ".hh" header file extension. See my reopened bug report 3737: http://www.cmake.

Re: [CMake] Why does cmake 2.4.0 (beta) compile header files?

Phillip Hellewell wrote: Why does CMake version 2.4.0 cause VS7 to compile header files? That's really weird. I don't even understand what it means to compile a header file, but sure enough, it is doing it. I think VS7 is dumb for trying to compile a header file, but I know it never had this

[CMake] Why does cmake 2.4.0 (beta) compile header files?

Why does CMake version 2.4.0 cause VS7 to compile header files?That's really weird.  I don't even understand what it means to compile a header file, but sure enough, it is doing it.  I think VS7 is dumb for trying to compile a header file, but I know it never had this problem with older versions of

Re: [CMake] Error adding rule for c:/dev/blah/../blah/CMakeLists.txt

On 4/20/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: I have checked in a fix that works for this example.-BillThanks.  That was fast!I'll try it out when the next build (2.4.1 I'm guessing) gets made.Phillip ___ CMake mailing list CMake@cmake.org htt

Re: [CMake] RE: UseLATEX.cmake macros

On 4/20/06, Moreland, Kenneth <[EMAIL PROTECTED]> wrote: > > > Well, I am at a loss as to what your problem can be. I am using the same > version of cmake and have successfully used UseLATEX.cmake on two different > platforms. > > Furthermore, the first two errors that you are getting are in part

RE: [CMake] RE: UseLATEX.cmake macros

Title: RE: [CMake] RE: UseLATEX.cmake macros Well, I am at a loss as to what your problem can be.  I am using the same version of cmake and have successfully used UseLATEX.cmake on two different platforms. Furthermore, the first two errors that you are getting are in part of UseLATEX.cmake t

Re: [CMake] Visual Studio problem with many/long additional library paths

At 04:02 PM 4/20/2006, Kristian Nielsen wrote: >Brad King <[EMAIL PROTECTED]> writes: > >> libraries are found by the linker. I've just modified the VS7 >> generator to use for each link directory either a relative path or a >> full path, whichever is shorter. This should minimize the string >> l

Re: [CMake] Visual Studio problem with many/long additional library paths

Brad King <[EMAIL PROTECTED]> writes: > libraries are found by the linker. I've just modified the VS7 > generator to use for each link directory either a relative path or a > full path, whichever is shorter. This should minimize the string > length. These changes will be included in the upcomin

Re: [CMake] Error adding rule for c:/dev/blah/../blah/CMakeLists.txt

At 12:16 PM 4/20/2006, Phillip Hellewell wrote: >On 4/19/06, William A. Hoffman <[EMAIL PROTECTED]> >wrote: >Can you create a small example that shows this problem? > >-Bill > > >Ok, here it is. When you try to run CMake version 2.4.0 with VS7 generator on >myproj, you

Re: [CMake] Visual Studio problem with many/long additional library paths

Karr, David A (Titan) @ TITAN wrote: From: Kristian Nielsen <[EMAIL PROTECTED]> This generates the following long line in mysqld.vcproj: I have not yet encountered the line length limit in Visual Studio, but I have found the length of the directory list makes it hard sometimes to debug problems

Re: [CMake] .net 2005 and Qt4 issues

Michael T. Wagner schrieb: Hi there, I had the same problem, seems to be a problem when mixing DLLs with and without embedded manifest info - using the debug version of the qt-libs for the debug build worked for me. (i dont remember if i also recompiled the libs with embedded manifest info)

Re: [CMake] RE: UseLATEX.cmake macros

On 4/20/06, Moreland, Kenneth <[EMAIL PROTECTED]> wrote: > The first error is because you are not building out-of-source. The rest > of the errors are a mystery to me. I'm not getting them. It looks like > CMake is incorrectly resolving a bunch of variables as empty (which > would also explain t

[CMake] Visual Studio problem with many/long additional library paths

> From: Kristian Nielsen <[EMAIL PROTECTED]> > > A cmakelists.txt file of mine contains the following: > > ADD_EXECUTABLE(mysqld ../sql-common/client.c ...) > TARGET_LINK_LIBRARIES(mysqld heap myisam myisammrg mysys yassl zlib dbug > yassl > taocrypt strings vio regex wsock3

Re: [CMake] .net 2005 and Qt4 issues

Hi there, I had the same problem, seems to be a problem when mixing DLLs with and without embedded manifest info - using the debug version of the qt-libs for the debug build worked for me. (i dont remember if i also recompiled the libs with embedded manifest info) Greetings, Mike John Hagu

Re: [CMake] RE: UseLATEX.cmake macros

On 4/19/06, Moreland, Kenneth <[EMAIL PROTECTED]> wrote: > Beber, > > I've posted an update for UseLATEX.cmake on the Wiki that should fix > your problem. Let me know if you have other issues. Thanks, But ... cmake failed : ~/pfe-cmake % cmake . -- Check for working C compiler: gcc -- Check for

RE: [CMake] RE: UseLATEX.cmake macros

The first error is because you are not building out-of-source. The rest of the errors are a mystery to me. I'm not getting them. It looks like CMake is incorrectly resolving a bunch of variables as empty (which would also explain the first error if you really are building out-of-source). What v

Re: [CMake] Coverage -- What is happening when you run a binary more than once?

Hi Kent, It looks like it accumulates the values (it does not seem to overwrite). Andy Kent Williams wrote: For the NIfTI regression tests, we run a binary for each ADD_TEST -- i.e. we build, e.g. a program called nifti1_test. Then each test is of the form ADD_TEST(exampletest $(NIF

[CMake] Coverage -- What is happening when you run a binary more than once?

For the NIfTI regression tests, we run a binary for each ADD_TEST -- i.e. we build, e.g. a program called nifti1_test. Then each test is of the form ADD_TEST(exampletest $(NIFTIUTILS_BINARY_DIR}/nifti1_test --testname exampletest) There are about 10 different executions of nifti1_test eve

Re: [CMake] .net 2005 and Qt4 issues

At 05:00 AM 4/20/2006, John Hague wrote: >Hi all. Am brand new to CMake, so please bear (or bare) with me... > > >I've just built CVS CMake (2.5), and used it to generate a .Net 2005 solution >for the smallest Qt4 app in the world. All configs (Debug, MinSizeRel, >Release, RelWithDebInfo) build

Re: [CMake] .net 2005 and Qt4 issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Hague wrote: > Hi all. Am brand new to CMake, so please bear (or bare) with me... > > I've just built CVS CMake (2.5), and used it to generate a .Net 2005 solution > for the smallest Qt4 app in the world. All configs (Debug, MinSizeRel, > Relea

[CMake] .net 2005 and Qt4 issues

Hi all. Am brand new to CMake, so please bear (or bare) with me... I've just built CVS CMake (2.5), and used it to generate a .Net 2005 solution for the smallest Qt4 app in the world. All configs (Debug, MinSizeRel, Release, RelWithDebInfo) build absolutely fine, but my Debug config build fails

Re: [CMake] Something similar to 'make zip'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > Hello, > > does cmake provide a build-target like 'make zip', i.e. put all sources > and include files within in one package esp. excluding any binary files > like object-files, libs etc.? > > Thanks in advance, > > Greeti