> CMake suppose you have CMake.
OK.
> Send us your CMakeLists.txt, there is something odd here.
I tried on another machine (Red Hat Linux) with a newer version of
CMake (2.8.4), but I get the same results.
This is what I did:
I downloaded Step6.tar.gz from
http://public.kitware.com/cgi-bin/vie
Am Mittwoch, 22. Juni 2011, 17:33:01 schrieb Karl Merkley:
> 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()
I'm not sure if
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
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 Jun 22, 2011, at 3:46 PM, Michael Hertling wrote:
> Wouldn't a simple
>
> CC="gcc -std=c99" cmake
>
> 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 have to kno
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 Wed, Jun 22, 2011 at 11:33 PM, Karl Merkley 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
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 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
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 cac
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 Xc
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 examp
On 06/22/2011 10:32 PM, David Cole wrote:
> On Wed, Jun 22, 2011 at 4:24 PM, Hauke Heibel
> wrote:
>
>> On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling
>> wrote:
>>> You might use -DMY_VARIABLE="${ARGUMENTS}" without VERBATIM, and
>>> SEPARATE_ARGUMENTS(MY_VARIABLE) in Foo.cmake. This doesn't
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 liba
2011/6/22 Dave Ohlsson :
> [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 in
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_
On Wed, Jun 22, 2011 at 4:24 PM, Hauke Heibel
wrote:
> On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling
> 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
On Wed, Jun 22, 2011 at 10:09 PM, Michael Hertling 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 but since MY_VA
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
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 woul
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 ${ARGU
[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
Alexander Neundorf wrote:
>> Is there some way I can modify that example to re-create the linker error
>> described in the comment?
>
> Well, if simply the path is used, FindQt4.cmake does not have to be
> executed before.
> If imported targets are used, FindQt4.cmake has to be executed before (or
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
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
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
>
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
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).
Unfortunately,
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 varie
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
>
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_defaultt
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)
project(ITK_M
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
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 list
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_packa
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 Neundor
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 equi
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
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 wrote:
> Since I got no feedback, I assume it's a bug. I've filed it here:
>
> 0012295: LINK_FLAGS_RELEASE has no effect
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
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 s
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 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 thi
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 t
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 file
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
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 t
The old syntax works, and I renamed file as f (good point).
Thank you.
2011/6/22 Michael Wild
> 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 act
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 LIS
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
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 directo
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 REQUIR
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::QtCor
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, i
>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
using namespace std;
#include "mpi.h"
int main( int argc, char * argv[] )
{
int node;
int num_nod
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 lin
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 C:/Wi
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
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 f
59 matches
Mail list logo
