The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12297
==
Reported By:Tim Cera
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12299
==
Reported By:Steven Velez
Assigned To:
On 06/21/2011 03:25 PM, Alexander Neundorf wrote:
Ok, I pushed the branch again.
The new name looks better. Perhaps I missed this last time, but the
documentation of the variable within the command is back up in the
simple section. Please put it at the very bottom of the entire
documentation,
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12301
==
Reported By:Stephen Kelly
Assigned To:
On 2011-06-22 17:36-0400 Mantis Bug Tracker wrote:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12301
==
Reported By:
On Wed, Jun 22, 2011 at 9:06 PM, Clinton Stimpson clin...@elemtech.com wrote:
On Jun 22, 2011, at 9:11 PM, Alan W. Irwin wrote:
On 2011-06-22 17:36-0400 Mantis Bug Tracker wrote:
The following issue has been SUBMITTED.
==
Writing to the list since some of you may find a script useful that I
have been developing for a while now.
I'm using this script to help maintain source files for inkscape
~2000 files, and blender3d ~4000 files.
With large, portable projects is its hard to keep track of all files
on an active
Hi
I'm trying to compile a main program (it contains MPI functions) using cmake. I
get an executable file (there aren't problems in compilation ), but it doesn't
run correctly.
If I compile my code using a simple Makefile, it works; but I need to compile
it using cmake (that's a prerequisite
What do you mean with "it doesn't run correctly"? Does it not even
start? How do you start your program?
Andreas
Am 22.06.2011 12:00, schrieb M Dolores Villalobos Ortiz:
Hi
I'm trying to compile a main program (it contains MPI functions) using
cmake. I get an
Hi all
On 64-bit Windows 7
I am trying to use the find_library command to locate a 64-bit mpich2
dll in the C:/Windows/System32 directory. I use
find_library (MPI_LIB fmpich2g PATHS C:/Windows/System32)
This command fails to find the dll. However, if I also install 32-bit
mpich2 so that
Clinton Stimpson wrote:
#
http://mail.kde.org/pipermail/kde-windows/2007-December/001692.html
#
http://lists.trolltech.com/pipermail/qt-interest/2009-July/009829.html
# qt is always compiled with QT_NO_DEBUG under mingw,
# so we need to compile stuff linked against it
# the same or
What do you mean with it doesn't run correctly? Does it not even
start? How do you start your program?
--
My program's code is:
#include iostream
using namespace std;
#include mpi.h
int main( int argc, char * argv[] )
{
int node;
int
On 06/22/2011 12:00 PM, Mª Dolores Villalobos Ortiz wrote:
Hi
I'm trying to compile a main program (it contains MPI functions) using
cmake. I get an executable file (there aren't problems in compilation ),
but it doesn't run correctly.
If I compile my code using a simple Makefile, it
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
SET(QT_USE_IMPORTED_TARGETS 1)
find_package(Qt4 REQUIRED)
then the imported targets would satisfy the Qt4::QtCore
Wups, sent a moment to early...
Stephen Kelly wrote:
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
SET(QT_USE_IMPORTED_TARGETS 1)
find_package(Qt4 REQUIRED)
then
This may be an issue with CMake being 32bit. 32bit programs on 64bit
windows get run in a sort of sandbox (you probably already know this, so
don't be offended if you do!). To a 32bit program on 64bit windows, I
believe the c:/windows/system32 directory is secretly the
c:/windows/syswow64
Hello,
I'm using CMake to do some OCaml building.
I launch the build command, using add_custom_command, so for the build to
actually trigger, I added the add_custom_target command.
Which I thought I did fine :
MACRO(OCAML_OPT LIST_OF_FILES)
message(STATUS ${LIST_OF_FILES})
FOREACH(FILE
On 06/22/2011 04:11 PM, Maxime Lecourt wrote:
Hello,
I'm using CMake to do some OCaml building.
I launch the build command, using add_custom_command, so for the build
to actually trigger, I added the add_custom_target command.
Which I thought I did fine :
MACRO(OCAML_OPT
The old syntax works, and I renamed file as f (good point).
Thank you.
2011/6/22 Michael Wild them...@gmail.com
On 06/22/2011 04:11 PM, Maxime Lecourt wrote:
Hello,
I'm using CMake to do some OCaml building.
I launch the build command, using add_custom_command, so for the build
On Jun 22, 2011, at 7:01 AM, Stephen Kelly wrote:
Wups, sent a moment to early...
Stephen Kelly wrote:
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
Hm... this is the CMake user list, not the MPI-user list. You're
posing your question on the wrong list.
(but how did you compile? Did you use mpicc?)
Sincerely,
Jakob
On 06/22/2011 02:25 PM, Mª Dolores Villalobos Ortiz wrote:
What do you mean with it doesn't run correctly? Does it
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION} which
I presume is filled from the find_package command (I just copied the file
from elsewhere).
Is there an equivalent for COMPONENTS so that if someone does a
find_package(Grantlee COMPONENTS Foo Bar)
my config
On 6/21/2011 4:43 PM, Alan W. Irwin wrote:
So it is not a regression, but in my opinion it is still a bug.
More comments at http://public.kitware.com/Bug/view.php?id=12284.
Please fix.
Patches are welcome, please send one... It would have to be an option
somehow at this point so as not
On Wednesday 22 June 2011, Stephen Kelly wrote:
Wups, sent a moment to early...
Stephen Kelly wrote:
Clinton Stimpson wrote:
It means the target must be created again with something like
add_library(Qt4::QtCore UNKNOWN IMPORTED)
If GrantleeConfig.cmake were to do this:
On Wednesday 22 June 2011, Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied the
file from elsewhere).
Is there an equivalent for COMPONENTS so that if someone does a
On Wednesday, June 22, 2011 10:01:37 am Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied the
file from elsewhere).
Is there an equivalent for COMPONENTS so that if someone
On Wednesday, June 22, 2011 05:06:41 am Stephen Kelly wrote:
Clinton Stimpson wrote:
#
http://mail.kde.org/pipermail/kde-windows/2007-December/001692.html
#
http://lists.trolltech.com/pipermail/qt-interest/2009-July/009829.htm
l # qt is always compiled with QT_NO_DEBUG under mingw,
So that the answer stays on the list:
One must use the STATIC_LIBRARY_FLAGS property, rather than
LINK_FLAGS, for static libraries.
On Tue, Jun 21, 2011 at 3:12 PM, Ben Medina ben.med...@gmail.com wrote:
Since I got no feedback, I assume it's a bug. I've filed it here:
0012295:
Alexander Neundorf wrote:
On Wednesday 22 June 2011, Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied
the file from elsewhere).
Is there an equivalent for COMPONENTS so
Clinton Stimpson wrote:
On Wednesday, June 22, 2011 10:01:37 am Stephen Kelly wrote:
Hi,
In my GrantleeConfigVersion.cmake.in I can use ${PACKAGE_FIND_VERSION}
which I presume is filled from the find_package command (I just copied
the file from elsewhere).
Is there an equivalent for
Hi Alex, thanks for the more detailed explanation. It is indeed more clear.
However, I still don't think there is a linker error if I omit
QT_USE_IMPORTED_TARGETS from the config file. I tried to re-create the error
condition with a trivial project and could not re-create it.
Alexander
Clinton Stimpson wrote:
Yeah, I just looked again to verify what you are seeing... you don't need
to do this SET(QT_USE_IMPORTED_TARGETS 1)
in GrantleeConfig.cmake, but you can still do
find_package(Qt4 REQUIRED)
to create the imported targets.
Clint
Cool, I'll just do a find_package(Qt4
I use (or try to use) mpicxx. There is an older post in
http://www.mail-archive.com/cmake@cmake.org/msg36851.html
--
Hm... this is the CMake user list, not the MPI-user list. You're
posing your question on the wrong
Hi!
In my tries to properly compile a library with Visual C++ 10 Express,
I've noticed that despite setting LIBRARY_OUTPUT_DIRECTORY
${PROJECT_SOURCE_DIR}/lib in SET_TARGET_PROPERTIES (which works
perfectly fine with gcc on Linux and Xcode on OSX), the Visual C++
Output directory property of
Thank you.
I have tried to compile my code using that version of CMakeLists, but it
doesn't work. My program's output is still wrong.
This is completely, utterly wrong!
# 2.7 was a development version, so you should either specify
# 2.6 or 2.8...
cmake_minim_required(VERSION 2.7)
Clinton Stimpson wrote:
And all unit tests then fail with MinGW. The errorString() reported is:
QDEBUG : TestBuiltinSyntax::testInsignificantWhitespace(insignificant-
whitespace43) Object QObject(0x0) The plugin
'C:/software/grantlee/qtcreator-
build/grantlee/0.1/grantlee_defaulttags.dll
'
On Wednesday, June 22, 2011 12:21:51 pm Stephen Kelly wrote:
Clinton Stimpson wrote:
And all unit tests then fail with MinGW. The errorString() reported is:
QDEBUG : TestBuiltinSyntax::testInsignificantWhitespace(insignificant-
whitespace43) Object QObject(0x0) The plugin
I am using cmake 2.8 for building MSVC solutions for a project.
The project builds fine as do the tests on Windows. The problem
comes when I try to run the tests. I usually get an error message
that the dependent DLLs cannot be found. I have searched on google
for an answer and came up with a
Hi,
My CMake version is 2.8.3 and I am trying to run a CMake script as a
custom target via
add_custom_target(RunFooTarget ALL
COMMAND ${CMAKE_COMMAND}
-DMY_VARIABLE=${ARGUMENTS}
-P Foo.cmake
VERBATIM
)
where ${ARGUMENTS} is a standard CMake list (semi-colon separated).
On Wednesday 22 June 2011, Stephen Kelly wrote:
Hi Alex, thanks for the more detailed explanation. It is indeed more clear.
However, I still don't think there is a linker error if I omit
QT_USE_IMPORTED_TARGETS from the config file. I tried to re-create the
error condition with a trivial
On Wednesday, June 22, 2011 12:21:51 pm Stephen Kelly wrote:
Clinton Stimpson wrote:
And all unit tests then fail with MinGW. The errorString() reported is:
QDEBUG : TestBuiltinSyntax::testInsignificantWhitespace(insignificant-
whitespace43) Object QObject(0x0) The plugin
Is there a good cross-platform way to enable C99 in a CMake project right now?
You can obviously do this:
set(CMAKE_C_FLAGS -std=c99)
However, that's the GNU way to enable C99, and other compilers do it
differently. It would be nice if there were some flags for this set for you in
Clinton Stimpson wrote:
The output is attached, but I'm not certain it's very helpful. Let me
know if anything else would be useful. I can maybe try to create a
smaller plugin using qt example for easy reproduction of the issue.
What is CMAKE_BUILD_TYPE set to?
I think it should be the
[Warning: I am a CMake beginner.]
Hi,
This must have been asked many times, but I can't find the answer...
(I did look at the CMake FAQ.)
If I use the autotools and I want to make a Linux source code
distribution to a user who doesn't have the autotools installed, I
ship him the source together
On 06/22/2011 09:14 PM, Hauke Heibel wrote:
Hi,
My CMake version is 2.8.3 and I am trying to run a CMake script as a
custom target via
add_custom_target(RunFooTarget ALL
COMMAND ${CMAKE_COMMAND}
-DMY_VARIABLE=${ARGUMENTS}
-P Foo.cmake
VERBATIM
)
where ${ARGUMENTS} is a
On Wed, 22 Jun 2011 12:32:55 -0700, Todd Gamblin said:
Is there a good cross-platform way to enable C99 in a CMake project
right now? You can obviously do this:
set(CMAKE_C_FLAGS -std=c99)
However, that's the GNU way to enable C99, and other compilers do it
differently. It would be
On Wednesday, June 22, 2011 01:47:33 pm Stephen Kelly wrote:
Clinton Stimpson wrote:
The output is attached, but I'm not certain it's very helpful. Let me
know if anything else would be useful. I can maybe try to create a
smaller plugin using qt example for easy reproduction of the issue.
On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling mhertl...@online.de wrote:
You might use -DMY_VARIABLE=${ARGUMENTS} without VERBATIM, and
SEPARATE_ARGUMENTS(MY_VARIABLE) in Foo.cmake. This doesn't prevent
the list's conversion, but seems a bit smarter than a FOREACH loop.
I considered this
On Wed, Jun 22, 2011 at 4:24 PM, Hauke Heibel
hauke.hei...@googlemail.comwrote:
On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling mhertl...@online.de
wrote:
You might use -DMY_VARIABLE=${ARGUMENTS} without VERBATIM, and
SEPARATE_ARGUMENTS(MY_VARIABLE) in Foo.cmake. This doesn't prevent
Done.
http://www.cmake.org/Bug/view.php?id=12300
On Jun 22, 2011, at 1:08 PM, Sean McBride wrote:
On Wed, 22 Jun 2011 12:32:55 -0700, Todd Gamblin said:
Is there a good cross-platform way to enable C99 in a CMake project
right now? You can obviously do this:
set(CMAKE_C_FLAGS
2011/6/22 Dave Ohlsson dave.ohls...@gmail.com:
[Warning: I am a CMake beginner.]
Hi,
This must have been asked many times, but I can't find the answer...
(I did look at the CMake FAQ.)
If I use the autotools and I want to make a Linux source code
distribution to a user who doesn't have
hi everyone,
I have been trying to use cmake to build ctsim(need to add my own code to it
later) and finally managed to do it however I have difficulty understanding why
my puny solution works!
I have 3 different directories (a,b,c) in ctsim , so I set up cmake files in
each one and built
On 06/22/2011 10:32 PM, David Cole wrote:
On Wed, Jun 22, 2011 at 4:24 PM, Hauke Heibel
hauke.hei...@googlemail.comwrote:
On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling mhertl...@online.de
wrote:
You might use -DMY_VARIABLE=${ARGUMENTS} without VERBATIM, and
Clinton Stimpson wrote:
On Wednesday, June 22, 2011 01:47:33 pm Stephen Kelly wrote:
Clinton Stimpson wrote:
The output is attached, but I'm not certain it's very helpful. Let me
know if anything else would be useful. I can maybe try to create a
smaller plugin using qt example for easy
On 06/22/2011 08:00 PM, Mathias Bavay wrote:
Hi!
In my tries to properly compile a library with Visual C++ 10 Express,
I've noticed that despite setting LIBRARY_OUTPUT_DIRECTORY
${PROJECT_SOURCE_DIR}/lib in SET_TARGET_PROPERTIES (which works
perfectly fine with gcc on Linux and Xcode on
Stephen Kelly wrote:
As a workaround, you can enforce a value for CMAKE_BUILD_TYPE if on
Windows
and CMAKE_CONFIGURATION_TYPES is empty. If you enforce that, then you
don't need to have the add_definition(-DQT_NO_DEBUG).
Thanks for the pointer. I'll try setting that in the cache before
On 06/22/2011 09:32 PM, Todd Gamblin wrote:
Is there a good cross-platform way to enable C99 in a CMake project right
now? You can obviously do this:
set(CMAKE_C_FLAGS -std=c99)
However, that's the GNU way to enable C99, and other compilers do it
differently. It would be nice if
I need to install a library into a directory whose name depends on the machine
type. For example
if (WIN32)
if (CMAKE_CL_64)
set(ARCH_DIR win32)
else()
set(ARCH_DIR win64)
endif()
elseif (UNIX)
if ()
set(ARCH_DIR linux32)
else()
set(ARCH_DIR linux64)
On Wed, Jun 22, 2011 at 11:33 PM, Karl Merkley k...@elemtech.com wrote:
I need to install a library into a directory whose name depends on the
machine type. For example
if (WIN32)
if (CMAKE_CL_64)
set(ARCH_DIR win32)
else()
set(ARCH_DIR win64)
endif()
elseif (UNIX)
if
Hi Karl,
You could do so something like that:
set(bitness 32)
if(CMAKE_SIZEOF_VOID_P EQUAL 8)
set(bitness 64)
endif()
The following macro provides a more complete example...
http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/CMake/SlicerMacroGetPlatformArchitectureBitness.cmake?view=markup
#
On Jun 22, 2011, at 3:46 PM, Michael Hertling wrote:
Wouldn't a simple
CC=gcc -std=c99 cmake path/to/source
for the initial configuration be an appropriate solution?
I would say no, because whether or not the project is written in C99 or not
isn't something the caller of cmake should
On Jun 22, 2011, at 11:11 AM, Mª Dolores Villalobos Ortiz wrote:
Thank you.
I have tried to compile my code using that version of CMakeLists, but it
doesn't work. My program's output is still wrong.
Whether or not mpiexec launches properly isn't something CMake can control. If
you are
On 2011-06-22 12:04-0400 Bill Hoffman wrote:
On 6/21/2011 4:43 PM, Alan W. Irwin wrote:
So it is not a regression, but in my opinion it is still a bug.
More comments at http://public.kitware.com/Bug/view.php?id=12284.
Please fix.
Patches are welcome, please send one... It would have to
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 672b6ca5e431f511f2638511b0128b6956f3e3ad (commit)
from
64 matches
Mail list logo
