Does anyone else have the problem that Visual Studio will only detect a
modified project and prompt to reload it ONCE. After that, you will not
get prompted again (even when you build ALL_BUILD or run cmake outside
of visual studio, or whatever. Cmake is working correctly and is
rebuilding
Does anyone else have the problem that Visual Studio will only detect a
modified project and prompt to reload it ONCE. After that, you will not
get prompted again (even when you build ALL_BUILD or run cmake outside
of visual studio, or whatever. Cmake is working correctly and is
rebuilding the
Sylvain
In Tools--Options--Environment--Keyboard set a shortcut for this 2
commands :
Project.ReloadProject
Project.UnloadProject
I'm used to set Alt+shift+R and Alt+shift+U
Thanks. I've just added them to my Keyboard mapping. I'd never thought
of doing this. Given me some ideas for other
I can rename the files, but as it happens I tried this experiement for a
single file and it did no good.
Is there a reason why the experiment would fail on a single file, but be
expected to work if they were all renamed to lowercase?
I think this may have been a bug in CMake 2.2. It will be
Once it is implemented properly you could do something like
SET(NRC206_SRCS ADDINT.C ...)
SET_SOURCE_FILES_PROPERTIES(${NRC206_SRCS} PROPERTIES COMPILE_LANGUAGE C)
ADD_LIBRARY(NRC206 ${NRC206_SRCS})
to override the default choice of compile language for capital .C
extensions. I'm not sure
Steve Johns wrote:
Once it is implemented properly you could do something like
SET(NRC206_SRCS ADDINT.C ...)
SET_SOURCE_FILES_PROPERTIES(${NRC206_SRCS} PROPERTIES COMPILE_LANGUAGE C)
ADD_LIBRARY(NRC206 ${NRC206_SRCS})
to override the default choice of compile language for capital .C
Can't you just rename the file to have a C++ extension? If not, you can
get foo.c compiled as C++ by creating an extra file called foo.cxx and
adding it instead. The file would contain just the code
// foo.cxx
#include foo.c
Good point.
Actually, it appears that I'm still seeing capital C
At 05:57 PM 5/17/2006, Steve Johns wrote:
Can't you just rename the file to have a C++ extension? If not, you can get
foo.c compiled as C++ by creating an extra file called foo.cxx and adding
it instead. The file would contain just the code
// foo.cxx
#include foo.c
Good point.
Actually, it
Actually, it appears that I'm still seeing capital C (e.g. FOO.C)
treated as C++, which is working out OK (so long as I know why it's
happening g).
BTW, can you confirm that behavior is still expected, as implemented in
CMake 2.4.2 ?
Capital C is a common extension for C++ on unix systems.
Hi.
I used CMake to create an MS VC7 solution configuration in order to import a
multi-directory project into the Visual Studio IDE, where I want to build it
to take advantage of the debugger, and DLL capabilities.
I was very pleased to generate all the solution and project files using
At 03:39 PM 5/16/2006, David Cole wrote:
You also get this behavior if you are used to using VC's Rebuild Solution...
With CMake, you never want to use Rebuild Solution - always Build
Solution...
Which is why CMake adds the ALL_BUILD target. You want to build the ALL_BUILD
target to build
Steve Johns wrote:
Is this right-click procedure available in MS VS .NET 2003, do you
know? If so, I'm not clear on where to find it.
Yes, it is. If you look at the Solution tab and select any target,
such as ALL_BUILD, use the + to open the target. There is a
CMakeLists.txt file listed.
Steve Johns wrote:
CMake considers upper-case C to be a C++ extension by default
because is a common convention on UNIX, and Windows is
case-insensitive. Try adding the files like this:
ADD_LIBRARY(NRC206 addint.c ...)
Thanks for the suggestion.
I tried this, but the result was still:
On 5/16/06, William A. Hoffman [EMAIL PROTECTED] wrote:
At 03:39 PM 5/16/2006, David Cole wrote:You also get this behavior if you are used to using VC's Rebuild Solution... With CMake, you never want to use Rebuild Solution - always Build Solution...
Which is why CMake adds the ALL_BUILD
CMake converts file names it is given to be the case they are actually
found on disk (for case-preserving filesystems like Windows). Rename the
files on disk to be lower case also. If that is not an option there may
be something else to do but I'll have to investigate.
Ah, more interesting
15 matches
Mail list logo