Hi,
I noticed gcc is used to link a c++ library on SunOS due to Sun shipping GCC
without a shared libstdc++ in the past (see discussion
http://www.cmake.org/pipermail/cmake/2006-August/010535.html here). Since
this does not seem to be the case anymore, changing the
CMAKE_CXX_CREATE_SHARED_LIBRARY
Many people care. Few have time to respond to everything on the CMake
mailing list...
This is how to become a CMake module maintainer if it is necessary:
http://www.cmake.org/Wiki/CMake:Module_Maintainers
Looks like Eric Wing is the maintainer for the other SDL related find
modules. I'll forward
On 29/06/2011 21:49, David Demelier wrote:
Hello cmake users,
I don't know how users usually send new modules so I try by mail. I made
a cmake module for SDL_gfx library
(http://www.ferzkopp.net/Software/SDL_gfx-2.0/)
It's not a SDL official library but it is popular and a lot of games are
usin
Hi Tim,
> How do we tell the project to use the compilers found by FindMPI?
Compiler detection in CMake currently happens before FindMPI and I'm not sure
whether it makes sense to force that to happen after FindMPI runs. The
expectation is that the user will supply the matching compiler in a t
On 2011-07-06 17:25+0200 pellegrini wrote:
thanks Alan for your help,
indeed 'ifort_release_win' stands for a build with ifort using a graphical
user interface. I just realize it was certainly not the best name for my
build directory (ifort_release_gui would have led to less confusion I gues
Use something like
SET (GUI ${GUI} CACHE BOOL "description")
To put proper initial value from command line into cache. It won't be
overwritten on the second run.
On Jul 1, 2011 2:02 PM, "pellegrini" wrote:
> Hello everybody,
>
> there is a behaviour I do not understand when using cmake with -D op
On Wednesday 06 July 2011, Jerry Gagelman wrote:
> 2011/7/6 Alexander Neundorf
>
> > On Wednesday 06 July 2011, Jerry Gagelman wrote:
> >
> > If these variables exist already in the cache, then a simple
> > set(... CACHE ...)
> > does not override the value which is already in the cache.
> > You
2011/7/6 :
> Folks
>
>
>
> As part of some other open source S/W OpenFOAM-2.0.0
>
> I need to build cmake-2.8.3 (preferred)
Why would need to build CMake?
Can't you take it from
http://www.cmake.org/files/v2.8/cmake-2.8.4-Linux-i386.tar.gz ?
> However on all the versions 2.8.2 , 2.8.3 , 2.8.4 I
I've attached a slightly modified patch, this one uses [0-9A-Za-z\\.]+ as
the version regex instead of [0-9\\.]+ just in case the version is a
pre-release with "a", "b" etc. as part of the version string.
- David
On Wed, Jul 6, 2011 at 11:10 AM, David Gobbi wrote:
> Hi All,
>
> The attached pa
On 07/06/2011 03:41 PM, Jerry Gagelman wrote:
> I'm redistributing a library for which the original authors have hand coded
> their own Makefile, but I would like to streamline everything with CMake.
> Their Makefile provides for Debug and Release flavored configurations, each
> has its own set of
Hi All,
The attached patch changes FindPythonLibs.cmake so that it returns the
following variables:
PYTHON_VERSION
PYTHON_MAJOR_VERSION
PYTHON_MINOR_VERSION
PYTHON_MICRO_VERSION
The purpose of this patch is to allow CMake scripts to perform conditional
configuration based on what python version w
2011/7/6 Alexander Neundorf
> On Wednesday 06 July 2011, Jerry Gagelman wrote:
>
> If these variables exist already in the cache, then a simple
> set(... CACHE ...)
> does not override the value which is already in the cache.
> You can only override a value in the cache from a CMakeLists.txt by u
Along similar lines, we have it currently working with:
find_package(MPI REQUIRED)
include(CMakeForceCompiler)
CMAKE_FORCE_C_COMPILER(mpicc ${CMAKE_C_COMPILER_ID})
CMAKE_FORCE_CXX_COMPILER(mpicxx ${CMAKE_CXX_COMPILER_ID})
CMAKE_FORCE_Fortran_COMPILER(mpif90 ${CMAKE_Fortran_COMPIL
Hi,
How do we tell the project to use the compilers found by FindMPI? On the master
branch, FindMPI has been modified to create MPI__COMPILER, etc.., but how
does one then specify that it should be used rather than the
CMAKE__COMPILER?
Tim
___
Powere
On Wednesday 06 July 2011, Jerry Gagelman wrote:
> I'm redistributing a library for which the original authors have hand coded
> their own Makefile, but I would like to streamline everything with CMake.
> Their Makefile provides for Debug and Release flavored configurations, each
> has its own set
On Tuesday 05 July 2011, Laszlo Papp wrote:
> Hi,
>
> I am trying to build a package in scratchbox on Harmattan, but I am
> having a small issue in the installation step (The compilation and
> build went just fine). Everything worked just fine previously on MeeGo
> and desktop system. This is the
On Wednesday 06 July 2011, Bello, Musodiq O (GE Healthcare) wrote:
> Thanks, Michael. But is there a way to make the references to CMake a
> relative path rather than an absolute path? This will allow us to bundle
> CMake with the source tree.
You can bundle CMake with the source tree, but you can
No, I don't think so. But then: *WHY*??? Would you also bundle GNU Make?
It just doesn't make sense. Declare CMake to be a build dependency, and
that's it. If people want to build your stuff, they have to install
CMake. It's really just
wget http://www.cmake.org/files/v2.8/cmake-2.8.4-Linux-i386.t
Thanks, Michael. But is there a way to make the references to CMake a relative
path rather than an absolute path? This will allow us to bundle CMake with the
source tree.
Thanks.
Musodiq
From: Michael Wild [mailto:them...@gmail.com]
Sent: Saturday, July 02, 2011 1:19 AM
To: Bello, Musod
thanks Alan for your help,
indeed 'ifort_release_win' stands for a build with ifort using a
graphical user interface. I just realize it was certainly not the best
name for my build directory (ifort_release_gui would have led to less
confusion I guess).
In the meantime, I found that cmake 2.
On 2011-07-06 11:36+0200 pellegrini wrote:
Hello everybody,
I have troubles running cmake 2.8.4 on my ubuntu 10.04 machine.
I must use that version because of a bug fix concerning rc files.
When running cmake, I get the following error message:
I'm redistributing a library for which the original authors have hand coded
their own Makefile, but I would like to streamline everything with CMake.
Their Makefile provides for Debug and Release flavored configurations, each
has its own set of CFLAGS, and for consistency I would like to incorporat
Folks
As part of some other open source S/W OpenFOAM-2.0.0
I need to build cmake-2.8.3 (preferred)
However on all the versions 2.8.2 , 2.8.3 , 2.8.4 I get a build error
libCMakeLib.a(cmMakefile.o): In function `std::list
>::_M_insert(std::_List_iterator, cmDefinitions const&)':
cmMake
Hello everybody,
I have troubles running cmake 2.8.4 on my ubuntu 10.04 machine.
I must use that version because of a bug fix concerning rc files.
When running cmake, I get the following error message:
##
-- The Fortran compiler i
Tirsdag 05 juli 2011 16.25.49 skrev Yngve Inntjore Levinsen :
> Dear developers,
>
> I am having what looks like a problem with library suffixes which I am not
> able to figure out.
>
> Essentially, our project has an option which when turned on adds a "-static"
> to the compiler flags. This t
25 matches
Mail list logo
