Hi,
I have the following question about generated by cmake solution and project
files on Win32 platform.
1. as result of processing my CMakeLists.txt, I got a 'solution' for VS .NET
2005, and several projects within it.
2. Every time I open the .vcproj file in VS .NET, 'single start up
Christoph Cullmann wrote:
Am Mittwoch 14 Mai 2008 16:30:24 schrieben Sie:
Are you sure the generated source file names are completely unpredictable?
Unless some random generator is being used, those names are probably
predictable, and it might be worth your while to look further into
Am Donnerstag, 15. Mai 2008 09:16:56 schrieb Martin Apel:
That's what I did for a similar problem: I modified the generator to
output a list of generated files, when called with a special command
line switch.
In this case the generator only generates the file list, not the files
themselves. I
Good morning,
thanks for all your comments. Here are the results:
- it seems to me that cmake is building console applications by default
(/SUBSYSTEM:CONSOLE).
That is correct for my .com applications. For the .exe, I will need
WINDOWS subsystem. Any possiblities in cmake?
- for the suffix,
Hi John,
- it seems to me that cmake is building console applications by
default (/SUBSYSTEM:CONSOLE).
That is correct for my .com applications. For the .exe, I will need
WINDOWS subsystem. Any possiblities in cmake?
Use the WIN32 option of the add_executable command:
Phil Pellouchoud wrote:
I have a *static library* that is giving the following warning:
LNK4221
Is there a way to tell cmake to add
/IGNORE:4221
Sorry, but there is no /IGNORE option to LIB. Afaik, LIB does not have
an option for disabling warnings. If you find one, please let
Use the WIN32 option of the add_executable command:
http://www.cmake.org/HTML/cmake-2.6.html#command:add_executable
Thanks. For any other interested people:
- this switches using of main to WinMain
- to switch it back, you can use
set_target_properties (autoconsole
On Wed, May 14, 2008 at 4:22 AM, Matthias Riechmann [EMAIL PROTECTED]
wrote:
Hi folks,
is there any well defined way to include external DLL files (Qt, VTK, ITK,
...) into the installer? I guess it will work somehow using the
INSTALL(FILES ...) command but currently I have no idea how to
Hi all,
I just download the gcc-4.3 binary distribution of mingw. It fails to
compile CMake due to
{{{
class cmSourceGroup
{
...
std::vectorcmSourceGroup GroupChildren; // cmSourceGroup is incomplete!
};
}}}
since libstdc++ is compilied with --enable-concept-checks.
Is gcc right? By
Michael Andronov wrote:
Hi,
I have the following question about generated by cmake solution and
project files on Win32 platform.
1. as result of processing my CMakeLists.txt, I got a 'solution' for VS
.NET 2005, and several projects within it.
2. Every time I open the .vcproj file in VS
So far so good it seems to work but then there is the next problem:
CMake is running on windows and so it happens that some paths contain
backslashes. This never was a problem before but the install-command
doesn't seem to like it. Is there a command for converting backslashes
to regular
Is there a command for converting backslashes to regular slashes?
Yes. Look at FILE(TO_CMAKE_PATH...) in the documentation.
Alan
__
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria
On Thursday 15 May 2008 15:55:46 Maik Beckmann wrote:
Hi all,
I just download the gcc-4.3 binary distribution of mingw. It fails to
compile CMake due to
{{{
class cmSourceGroup
{
...
std::vectorcmSourceGroup GroupChildren; // cmSourceGroup is incomplete!
};
}}}
since libstdc++ is
I won't name the package because I find this construction really
stupid, but I'm writing CMakeLists.txt files for a package we want to
use and came across this:
%_floof: %.c
$(CC) $(CFLAGS) -DFLOOF -o $@ -lfloof
So I don't really see how CMake could do something like this. And
that doesn't
On Thursday 15 May 2008, kent williams wrote:
I won't name the package because I find this construction really
stupid, but I'm writing CMakeLists.txt files for a package we want to
use and came across this:
%_floof: %.c
$(CC) $(CFLAGS) -DFLOOF -o $@ -lfloof
So I don't really see how
On Thursday 15 May 2008 20:01:02 kent williams wrote:
I won't name the package because I find this construction really
stupid, but I'm writing CMakeLists.txt files for a package we want to
use and came across this:
%_floof: %.c
$(CC) $(CFLAGS) -DFLOOF -o $@ -lfloof
So I don't
So I seem to have gotten it to work by doing this:
SET_TARGET_PROPERTIES( target PROPERTIES LINK_FLAGS
/LIBPATH:path_to_libraries )
Which seems kinda gross to me...
-phil
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Phil Pellouchoud
Sent: Thursday, May 15, 2008 10:03
Am Donnerstag 15 Mai 2008 17:16:32 schrieb dizzy:
Seems CMake is violating ISO C++ then. You may not instantiate standard
library templates of incomplete types (for example, even struct A {
std::auto_ptrA a; }; is invalid, C++0x will have an exception to that
for shared_ptr, but for the
Am Donnerstag 15 Mai 2008 20:45:09 schrieb Maik Beckmann:
I'll configure my gcc installation to use concepts-checks and I'll do some
testing on the code at my workspace (i.e. boost) just to see how common
this kind of STL abuse is.
Well, boost.python fails to compile due to a missing
dizzy escreveu:
Seems CMake is violating ISO C++ then. You may not instantiate standard
library templates of incomplete types (for example, even struct A {
std::auto_ptrA a; }; is invalid, C++0x will have an exception to that for
shared_ptr, but for the standard containers that surely is the
Hi,
(Beware the cmake noob here ;)
I have a simple fortran project and am having a problem during compiler
identification stage. Attached is my CMakeLists.txt and the CMakeError.log.
Just to give some more details, the problem takes place on login nodes
(regular linux system) of a supercomputer
21 matches
Mail list logo