ake List"
Sent: Monday, July 2, 2012 6:09:59 PM
Subject: RE: [CMake] cmake 2.6 and 2.8 find different fortran compilers with
MPI?
Thanks Tim. We do have the module system set up including the compiler, so I’ll
make sure it defines FC.
From: Tim Gallagher [mailto:tim.gallag...
Thanks Tim. We do have the module system set up including the compiler, so
I’ll make sure it defines FC.
From: Tim Gallagher [mailto:tim.gallag...@gatech.edu]
Sent: Monday, July 02, 2012 2:59 PM
To: Ateljevich, Eli
Cc: CMake List
Subject: Re: [CMake] cmake 2.6 and 2.8 find different fortran
;t need to worry about manually setting
things or putting things in your path in a particular order.
Tim
- Original Message -
From: "Eli Ateljevich"
To: "CMake List"
Sent: Monday, July 2, 2012 5:20:34 PM
Subject: [CMake] cmake 2.6 and 2.8 find different fortran
Hi,
I wonder if anyone can help me get a consistent Fortran build out of 2.6 and
2.8.8. I am using CMake 2.6 and 2.8, trying to come up with a compatible build.
I had to rob some items from 2.8 to find things like MPI correctly and I have
set the policies such that I believe they both use the sa
On 8. Jan, 2010, at 9:54 , Mahendra Ladhe wrote:
> Hi,
>I've a Ubuntu 8.04.1 Linux machine and cmake version 2.4-patch 7 in
> /usr/bin/
> Due to project requirement, I installed cmake version 2.6-patch 4 under
> /usr/local/
>
> I want to make sure that when I or other users execute cmake,
Hi,
I've a Ubuntu 8.04.1 Linux machine and cmake version 2.4-patch 7 in /usr/bin/
Due to project requirement, I installed cmake version 2.6-patch 4 under
/usr/local/
I want to make sure that when I or other users execute cmake, by default it's
always the 2.4 version in /usr/bin/cmake irrespec
Thanks a lot Alan,
this solved the issue and also my original problem concerning the pot
target.
> Yes. replace bla.txt everywhere by ${CMAKE_CURRENT_BINARY_DIR}/bla.txt,
It is sufficient to specify the path for add_custom_target, i.e.
--8<---CMakeLists.txt
cmake_minimum_req
On 2010-01-01 01:57+0100 Spicy wrote:
Hi cmakers,
I decided to start a new project using cmake. While I got a lot of
things going quickly, some things are taking me to despair. The current
issue has a couple of web hits, but either I misunderstand something
critical or cmake 2.6 (as of current
Hi cmakers,
I decided to start a new project using cmake. While I got a lot of
things going quickly, some things are taking me to despair. The current
issue has a couple of web hits, but either I misunderstand something
critical or cmake 2.6 (as of current Debian Lenny) is broken:
--8<---CMa
Hi,
I know you guys have discussed cmake-2.6 on OpenBSD before on this list.
I spent a little while trying to figure out how to get the latest
release of cmake-2.6 building shared libraries with the correct names
and versions. I was hoping I could find a developer to work with us on
this, as the
Hi!
I have managed to solve my problems just the way Robert proposed. I changed
the cMakeOptions.cmake file fixing the lines:
find_package(VTK REQUIRED)
include(${VTK_USE_FILE})
and using the VTK_WRAP_TCL3 with the required parameters.
Thank you very much for the useful info.
Jorge,
2009/4/6
Hi,
I have Recently upgraded to cmake 2.6 and i noticed that the command
VTK_WRAP_TCL used to wrap classes in TCL has been deprecated. I've
looking around for some info on how to wrap classes in TCL in cmake
2.6 but still got any. I'd appreciate any information or experience
you may have
Jorge Ballesteros wrote:
Hi you all!
I have Recently upgraded to cmake 2.6 and i noticed that the command
VTK_WRAP_TCL used to wrap classes in TCL has been deprecated. I've
looking around for some info on how to wrap classes in TCL in cmake 2.6
but still got any. I'd appreciate any informatio
Hi you all!
I have Recently upgraded to cmake 2.6 and i noticed that the command
VTK_WRAP_TCL used to wrap classes in TCL has been deprecated. I've looking
around for some info on how to wrap classes in TCL in cmake 2.6 but still
got any. I'd appreciate any information or experience you may have o
Sean McBride wrote:
Hi all,
Back in early April 2008 we debated whether CMake's .app should be named
simply "CMake.app" or something with the version number, like "CMake
2.6-3.app".
I just updated from 2.6.2 to 2.6.3, and went to rebuild my VTK. It now says:
/bin/sh: /Applications/CMake 2.6-2
Hi all,
Back in early April 2008 we debated whether CMake's .app should be named
simply "CMake.app" or something with the version number, like "CMake
2.6-3.app".
I just updated from 2.6.2 to 2.6.3, and went to rebuild my VTK. It now says:
/bin/sh: /Applications/CMake 2.6-2.app/Contents/bin/cmak
se others in the future encounter a
similar problem.
Cheers,
Anders.
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Wed, 3 Sep 2008 08:10:32
+0000Subject: [CMake] cmake 2.6 insists on using MSVC x64 even when in 32 bit
shell
Hi all I'm trying to compile a 32 bit version of VTK
Anders Moe wrote:
Thank for answering.
I'm using the CmakeSetup.exe utility and interactively pick the Visual
Studio 8 2005 compiler when it asks meI hope that answered the
question ?
The error dialog doesn't allow copy/paste, or I'd include more info.
The information should be i
ards,
Anders
Anders Moe
Software Integration ManagerGeocapw: +47 22 95 56 66
[EMAIL PROTECTED]
Date: Wed, 3 Sep 2008 06:38:00 -0400From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
[EMAIL PROTECTED]: Re: [CMake] cmake 2.6 insists on using MSVC x64 even when in
32 bit s
What CMake generator are you using?
On Wed, Sep 3, 2008 at 4:10 AM, Anders Moe <[EMAIL PROTECTED]> wrote:
>
>
> Hi all
>
> I'm trying to compile a 32 bit version of VTK using the 32 bit MSVC 2005
> command shell. Note that I'm running XP64.
>
> This works fine for Qt, but cmake gives an error du
Hi all
I'm trying to compile a 32 bit version of VTK using the 32 bit MSVC 2005
command shell. Note that I'm running XP64.
This works fine for Qt, but cmake gives an error during the "simpel test
program compile" where it appears that the test solution *.sln is setup for
x64, since the er
> That module was never part of CMake:
Hi Bill, thanks for your reply.
> $ cvs log FindGLEW.cmake
> cvs log: nothing known about FindGLEW.cmake
That leaves no doubt about it !
> It might have been part of your project, and you used
> CMAKE_MODULE_PATH to find it?
Googling it (code.google is my
Antoine PREVOT wrote:
Hi,
I am actually testing cmake 2.6-1, and I can't find FindGLEW.cmake
anymore in the Modules folder of both darwin sources and binary archives
(cmake-2.6.1.tar & cmake-2.6.1-Darwin-universal.tar).
Nothing about this in the ChangeLog.
Bug or Feature ? :)
That module w
Hi,
I am actually testing cmake 2.6-1, and I can't find FindGLEW.cmake anymore in
the Modules folder of both darwin sources and binary archives (cmake-2.6.1.tar
& cmake-2.6.1-Darwin-universal.tar).
Nothing about this in the ChangeLog.
Bug or Feature ? :)
Tonio
_
On 2008-05-30 18:00+0200 Maik Beckmann wrote:
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a
On 2008-05-30 18:00+0200 Maik Beckmann wrote:
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a
Am Freitag 30 Mai 2008 17:41:21 schrieb Kelly (KT) Thompson:
> Hi,
>
> I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
> Fortran 10) project that needs to use the link flags "/libs:dll
> /threads" (alternate "/MD"). I am generating a "Visual Studio 8 2005"
> project. I have
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a "Visual Studio 8 2005"
project. I have reduced the problem to a "hello world" F90 code:
program main
print
Christian Ehrlicher wrote:
Thx for the explanation.
No problem, how do you think we could reword the warning to avoid future
confusion? You are certainly not alone here. :)
-Bill
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mai
Bill Hoffman schrieb:
Christian Ehrlicher wrote:
I understood the warning - I know that it is not mandatory.
> But how useful is a warning when the only way to get rid of them is
>
to disable it? I either have to fix all places (including the system libs
>) or disable it and don't care
Christian Ehrlicher wrote:
I understood the warning - I know that it is not mandatory.
> But how useful is a warning when the only way to get rid of them is
>
to disable it? I either have to fix all places (including the system libs
>) or disable it and don't care at all. That's stupid.
Christian Ehrlicher wrote:
> I understood the warning - I know that it is not mandatory. But how useful is
> a warning when the only way to get rid of them is to disable it? I either
> have to fix all places (including the system libs) or disable it and don't
> care at all. That's stupid.
Addin
> Von: Bill Hoffman
> Christian Ehrlicher wrote:
> > Hi,
> >
> > during your new warning when mixing libs in target_link_libraries
> > (CMP0003) I changed target_link_libraries(foo ws2_32) to
> >
> > find_library(WS2_32_LIBRARY ws2_32)
> > target_link_libraries(foo ${WS2_32_LIBRARY})
> >
> > bu
Christian Ehrlicher wrote:
Hi,
during your new warning when mixing libs in target_link_libraries
(CMP0003) I changed target_link_libraries(foo ws2_32) to
find_library(WS2_32_LIBRARY ws2_32)
target_link_libraries(foo ${WS2_32_LIBRARY})
but now cmake finds ws2_32.dll in system32 instead the co
> Von: Hendrik Sattler
> Christian Ehrlicher schrieb:
> >> Von: Hendrik Sattler
> >> Christian Ehrlicher schrieb:
> >>
> >>> during your new warning when mixing libs in target_link_libraries
> >>> (CMP0003) I changed target_link_libraries(foo ws2_32) to
> >>>
> >>> find_library(WS2_32_LIBRARY
Christian Ehrlicher schrieb:
Von: Hendrik Sattler
Christian Ehrlicher schrieb:
during your new warning when mixing libs in target_link_libraries
(CMP0003) I changed target_link_libraries(foo ws2_32) to
find_library(WS2_32_LIBRARY ws2_32)
target_link_libraries(foo ${WS2_32_LIBRARY})
but n
> Von: Hendrik Sattler
> Christian Ehrlicher schrieb:
> > during your new warning when mixing libs in target_link_libraries
> > (CMP0003) I changed target_link_libraries(foo ws2_32) to
> >
> > find_library(WS2_32_LIBRARY ws2_32)
> > target_link_libraries(foo ${WS2_32_LIBRARY})
> >
> > but now cmak
Christian Ehrlicher schrieb:
during your new warning when mixing libs in target_link_libraries
(CMP0003) I changed target_link_libraries(foo ws2_32) to
find_library(WS2_32_LIBRARY ws2_32)
target_link_libraries(foo ${WS2_32_LIBRARY})
but now cmake finds ws2_32.dll in system32 instead the correc
Hi,
during your new warning when mixing libs in target_link_libraries
(CMP0003) I changed target_link_libraries(foo ws2_32) to
find_library(WS2_32_LIBRARY ws2_32)
target_link_libraries(foo ${WS2_32_LIBRARY})
but now cmake finds ws2_32.dll in system32 instead the correct one
(ws2_32.dll.a / w
Hi Andreas,
On Wednesday 14 May 2008, you wrote:
> Hi,
> Thank you for all these hints. Are details like that described in the
> Mastering CMake book?
Yes and no.
The process how the system and the compiler are determined is described, but
not every implementation detail of the files.
> I trac
Hi,
Thank you for all these hints. Are details like that described in the
Mastering CMake book?
I tracked it down to:
CMakeDetermineCCompiler.cmake: line 97:
IF (NOT _CMAKE_TOOLCHAIN_PREFIX)
GET_FILENAME_COMPONENT(COMPILER_BASENAME "${CMAKE_C_COMPILER}" NAME_WE)
MESSAGE(STATUS "CMAKE_C_COMPILE
On Tuesday 13 May 2008, Andreas Pokorny wrote:
> Hi,
> Can you give me some hints on filtering the strace output. I expected
> to find syscalls
> that try to open "ar" or "ar.exe". There was none.
It's done in Modules/CMakeFindBinUtils.cmake, which is included e.g. in
Modules/CMakeDetermineCCompi
Hi,
Can you give me some hints on filtering the strace output. I expected
to find syscalls
that try to open "ar" or "ar.exe". There was none.
I looked at calls of "symlink_info::check". When grepping for these
calls, there was a
block of:
38 4093345 [main] cmake 528 symlink_info::check: 0 = symlin
On Friday 09 May 2008, Andreas Pokorny wrote:
> Hello,
> I currently try to replace my cmake-2.4 cross compile workarounds with
> proper cmake-2.6 toolchain files.
> The first one I tried was my ARM QNX Neutrino 6.3 file:
>
>
> SET(CMAKE_SYSTEM_NAME QNX)
> SET(CMAKE_SYSTEM_
Hello,
I currently try to replace my cmake-2.4 cross compile workarounds with
proper cmake-2.6 toolchain files.
The first one I tried was my ARM QNX Neutrino 6.3 file:
SET(CMAKE_SYSTEM_NAME QNX)
SET(CMAKE_SYSTEM_VERSION 6.3)
SET(QNX_TARGET $ENV{QNX_TARGET} CACHE PATH "Pat
On Thursday 17 April 2008, Andreas Pokorny wrote:
> Hi,
> We currently use cmake-2.4-8 and embedded visual c (evc) 4.0 to build for
> armv4 WinCE5. I plan to upgrade the project to cmake-2.6 soon. Then I will
> probably make use of the cross compile feature.
>
> Right now we simply include a cmake
Hi,
We currently use cmake-2.4-8 and embedded visual c (evc) 4.0 to build for
armv4 WinCE5. I plan to upgrade the project to cmake-2.6 soon. Then I will
probably make use of the cross compile feature.
Right now we simply include a cmake file containing the settings required for
WinCE. With that fi
On Wednesday 16 April 2008, David Blado wrote:
> Hi All,
>
> I understand that CMake 2.6 will fully support cross compilation. I
> assume that this means (with the right toolchain file) that I should be
> able to build for any Windows CE SDK (Pocket PC, Windows Mobile,
> Standard CE).
Yes.
> I
Hi All,
I understand that CMake 2.6 will fully support cross compilation. I
assume that this means (with the right toolchain file) that I should be
able to build for any Windows CE SDK (Pocket PC, Windows Mobile,
Standard CE). If that assumption is correct, my question is whether the
generate
I have committed a fix to CVS CMake that should avoid this problem in the
future. It should be included in the next CMake 2.6 RC.
$ cvs commit -m "BUG: There are compiler problems with wxWidgets and
INCLUDE_DIRECTORIES(SYSTEM ...) use on the Mac. Set variable
wxWidgets_INCLUDE_DIRS_NO_SYSTEM on th
Speaking of wxWidgets being broken, could at least one cmake-dashboard
runs with:
BUILD_WXDialog:BOOL=ON
As far as I remember this is still using the old UsewxWidgets style
(~cmake 2.4.5). Just knowing that the build is working would make a
great test.
Thanks !
On Tue, Apr 15, 2008 at 11:10 PM,
On Tue, Apr 15, 2008 at 6:47 PM, David Cole <[EMAIL PROTECTED]> wrote:
> Is there a sample CMake project that I could try to reproduce this with? Or
> could you send me access to your source tree? Is it an open source project?
Copy minimal.cpp (and sample.xpm) from wxWidgets samples directory with
Perhaps I should have added that I am not using XCODE since the
isystem business gets removed for XCODE in Darwin.cmake.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
OSX 10.3.9 (gcc 3.3)
cmake 2.6-RC-8
wxwidgets 2.8.3
In moving from cmake 2.4 to 2.6-RC-8 the WxWidgets support is failing.
When compiling wxwidget code I am seeing commands from cmake like:
/usr/bin/c++ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXMAC__
-fmessage-length=0 -D__WXMAC__ -I/Users/an
Hi,
I am trying to get a grip on how to get resources installed in an
application bundle on OS X. What do i have to do except the following:
set_target_properties(foo
PROPERTIES
RESOURCE ${res_list})
I
On Friday 28 March 2008 9:57:32 am David Cole wrote:
> You can launch it from a shell that has the env set :
> open /Applications//cmake-gui.app
>
> Or follow the directions here to set env vars for all your GUI apps in Mac
> OSX:
> http://developer.apple.com/documentation/MacOSX/Conceptual/OSX
You can launch it from a shell that has the env set :
open /Applications//cmake-gui.app
Or follow the directions here to set env vars for all your GUI apps in Mac
OSX:
http://developer.apple.com/documentation/MacOSX/Conceptual/OSX_Technology_Overview/CommandLine/chapter_950_section_4.html
On
On Fri, Mar 28, 2008 at 4:45 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote:
> I am guessing you would have to set those variables somewhere else for
> them to be in the system. I am not sure how a mac works, what
> environment does the windowing system run in? Can you set variables for
> that e
Mike Jackson wrote:
In testing CMakeGui.app the first problem I ran across was its inability
to pick up environment variables I have set in my .bash_profile file. Is
there a way to tell the gui app to look at that file for environment
variables?
While not directly a cmake issue, I was wonderi
In testing CMakeGui.app the first problem I ran across was its
inability to pick up environment variables I have set in
my .bash_profile file. Is there a way to tell the gui app to look at
that file for environment variables?
While not directly a cmake issue, I was wondering if anyone else
Bug 0006286 submitted.. finally..
On Jan 14, 2008 12:33 PM, Mike Jackson <[EMAIL PROTECTED]> wrote:
>
> On Jan 14, 2008, at 12:20 PM, Bill Hoffman wrote:
>
> > Mike Jackson wrote:
> >> I just built the latest CVS head of CMake and tried running on OS
> >> X (10.4.11 Intel) and noticed a few thing
On Jan 14, 2008, at 12:20 PM, Bill Hoffman wrote:
Mike Jackson wrote:
I just built the latest CVS head of CMake and tried running on OS
X (10.4.11 Intel) and noticed a few things.
1: CMake Error: CMake executable cannot be found at /Users/Shared/
Toolkits/CMake-ICC/bin/QtDialog.app/Contents/
On Monday 14 January 2008 10:20:18 am Bill Hoffman wrote:
> Mike Jackson wrote:
> > I just built the latest CVS head of CMake and tried running on OS X
> > (10.4.11 Intel) and noticed a few things.
> >
> > 1: CMake Error: CMake executable cannot be found at
> > /Users/Shared/Toolkits/CMake-ICC/bin/
Mike Jackson wrote:
I just built the latest CVS head of CMake and tried running on OS X
(10.4.11 Intel) and noticed a few things.
1: CMake Error: CMake executable cannot be found at
/Users/Shared/Toolkits/CMake-ICC/bin/QtDialog.app/Contents/MacOS/cmake
Probably just a path issue between the
I just built the latest CVS head of CMake and tried running on OS X
(10.4.11 Intel) and noticed a few things.
1: CMake Error: CMake executable cannot be found at /Users/Shared/
Toolkits/CMake-ICC/bin/QtDialog.app/Contents/MacOS/cmake
Probably just a path issue between the .app bundle and the
On Wednesday 25 July 2007 23:07:44 Andy Dingfelder wrote:
> Great.
> I will try and see about getting the latest version.
>
> Is anyone here running Gentoo?
>
> The way I got cmake 2.4 was by running emerge, and clearly that is not
> going to work with the cvs builds.
> So, I assume I need to set u
Great.
I will try and see about getting the latest version.
Is anyone here running Gentoo?
The way I got cmake 2.4 was by running emerge, and clearly that is not
going to work with the cvs builds.
So, I assume I need to set up a portage overlay for emerging a
development version but I would rat
From the CMake CVS repository. CVS HEAD has the cross-compiling
functionality in it right now...
HTH,
David
On 7/24/07, Andy Dingfelder <[EMAIL PROTECTED]> wrote:
The example on http://www.cmake.org/Wiki/CMake_Cross_Compiling says that
this is supported by CMake starting with version 2.6.0 (
The example on http://www.cmake.org/Wiki/CMake_Cross_Compiling says that
this is supported by CMake starting with version 2.6.0 (not yet released
as of July 2007).
Where can one download v2.6 to try this ?
WARNING: T
69 matches
Mail list logo