[CMake] Relation between .vcproj and .vcproj.cmake

Hi. I'm wondering, could someone kindly explain the relationship between the .vcproj and .vcproj.cmake files (in the MSVC build environment)? I understand that the .vcproj is the actual project file as used by the MSVC IDE, but what is the purpose of the .vcproj.cmake file (which I notice is

Re: [CMake] Relation between .vcproj and .vcproj.cmake

At 10:10 AM 6/23/2006, Steve Johns wrote: Hi. I'm wondering, could someone kindly explain the relationship between the .vcproj and .vcproj.cmake files (in the MSVC build environment)? I understand that the .vcproj is the actual project file as used by the MSVC IDE, but what is the purpose of

Re: [CMake] Relation between .vcproj and .vcproj.cmake

Steve Johns wrote: I'm wondering, could someone kindly explain the relationship between the .vcproj and .vcproj.cmake files (in the MSVC build environment)? I understand that the .vcproj is the actual project file as used by the MSVC IDE, but what is the purpose of the .vcproj.cmake file

Re: [CMake] Relation between .vcproj and .vcproj.cmake

The .cmake version is an implementation detail of getting VS to re-run CMake at the proper time to regenerate projects. -Brad Hello, We don't use the auto-regeneration feature. Is there a variable in CMake to automatically delete this file ? Sylvain

Re: [CMake] Relation between .vcproj and .vcproj.cmake

At 10:51 AM 6/23/2006, Sylvain Benner wrote: The .cmake version is an implementation detail of getting VS to re-run CMake at the proper time to regenerate projects. -Brad Hello, We don't use the auto-regeneration feature. Is there a variable in CMake to automatically delete this file ? No, it

[CMake] Cmake MacOSX Question

Cmake Experts, I am running into a problem with static libraries and conflicting frameworks on MacOSX. I need to statically build my own version of tcl and tk with X11 bindings and link it to my application. The problem is that the linker is preferring to bind to the Tcl.framework and

RE: [CMake] cmake 2.2 / 2.4 differences?

Is there a list of important changes between 2.2 / 2.4? (also when exactly was 2.4 released?) Bill did send out and email with the major changes I believe with the 2.4.2 announcement as well as earlier ones. (e.g. must be in the cmake ml archive) This also in relation to the official book :

RE: [CMake] cmake 2.2 / 2.4 differences?

At 11:26 AM 6/23/2006, Ken Martin wrote: Is there a list of important changes between 2.2 / 2.4? (also when exactly was 2.4 released?) I have updated the News web page. Thanks for the reminder. :) -Bill ___ CMake mailing list CMake@cmake.org

Re: [CMake] Cmake MacOSX Question

Hans J. Johnson wrote: Cmake Experts, I am running into a problem with static libraries and conflicting frameworks on MacOSX. I need to statically build my own version of tcl and tk with X11 bindings and link it to my application. The problem is that the linker is preferring to bind to the

Re: [CMake] Cmake MacOSX Question

Brad, Here is the output. I am still perplexed as to why the tcl and tk libraries from the framework (or /usr/lib) are being included. /usr/bin/c++-bind_at_load -O2 -ftemplate-depth-50 -no-cpp-precomp -Wno-long-double -ftemplate-depth-50 -no-cpp-precomp -Wno-long-double -DNO_ITK_TCL -O3

Re: [CMake] Cmake MacOSX Question

I think there are symlinks to the tcl/tk stuff in /usr/lib or some other system area, they link to the framework version. -Bill At 01:38 PM 6/23/2006, Hans J. Johnson wrote: Brad, Here is the output. I am still perplexed as to why the tcl and tk libraries from the framework (or /usr/lib)

Re: [CMake] Cmake MacOSX Question

Bill, There are simlinks to the libraries in /usr/lib that link to the libraries, but /usr/lib is not on my link line, and is supposed to be looked at after all the -L directories are searched. Hans On 6/23/06 12:45 PM, William A. Hoffman [EMAIL PROTECTED] wrote: I think there are symlinks

Re: [CMake] Linking and CMakelists.txt

The changes are processed by CMake immediately and the project files are regenerated. However, VS 7.1 does not seem to reliably reload the new project files always. Try exiting VS and running CMake by hand and then reloading the project in VS after editing a file. Brad, Thanks for that