On 21. Jan, 2010, at 24:55 , Mateusz Loskot wrote:
> Hi,
>
> I'm trying to perform the following checks:
>
> check_function_exists(std::pow HAVE_POW)
>
> or
>
> check_symbol_exists(std::pow cmath HAVE_POW)
>
> but it looks that both macros have troubles
> with resolving std:: namespace.
>
>
On 2010-01-21 11:03+0900 Ryo IGARASHI wrote:
Dear developers,
Currently, FindLAPACK.cmake and FindBLAS.cmake *requires* Fortran compiler.
However, I can easily think of a situation when no Fortran compiler
but LAPACK/BLAS
available. Let's say:
* Use ATLAS on VC9 (Windows)
* Buy Intel C++ compil
Dear developers,
Currently, FindLAPACK.cmake and FindBLAS.cmake *requires* Fortran compiler.
However, I can easily think of a situation when no Fortran compiler
but LAPACK/BLAS
available. Let's say:
* Use ATLAS on VC9 (Windows)
* Buy Intel C++ compiler but not Fortran compiler (each of them have
M
Hi,
I have a very interesting problem. It is described below.
I have two projects Proj1 & Proj2 under a top level root directory.
Now, the build steps are as follows:
1. Build Proj1 into Proj1.exe
2. Execute Proj1.exe and it generates source1.cpp as an output (it
is a source file gener
Hi,
I'm trying to perform the following checks:
check_function_exists(std::pow HAVE_POW)
or
check_symbol_exists(std::pow cmath HAVE_POW)
but it looks that both macros have troubles
with resolving std:: namespace.
The documentation is not very clear about that.
Or I should stick to try_compil
Philip Lowman wrote:
> On Mon, Jan 18, 2010 at 7:17 PM, Mateusz Loskot wrote:
>>
>> In CMakeLists.txt I have something like this:
>>
>> if(MSVC)
>> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /W4")
>> endif()
>>
>> I configure my build using command prompt of Visual Studio 2005 (8.0):
>>
>> D:\dev\ge
Tyler Roscoe wrote:
> On Tue, Jan 19, 2010 at 12:17:04AM +, Mateusz Loskot wrote:
>> I believe it would make sense to have UNIQUE command too:
>>
>> list(UNIQUE )
>>
>> unless it's already available and I've not read the doc
>> carefully, have I?
>
> It's called REMOVE_DUPLICATES.
It looks ex
>> To add an additional option I have successfully used QtCreator (which
>> builds using MinGW) on windows with cmake. It supports CMakeLists.txt
>> files directly. I would call it work in progress as far as the CMake
>> support.
>
> What's not working ?
> (it works off the same CodeBlocks files)
>
On Wednesday 20 January 2010, John Drescher wrote:
> > 2010/1/20 Mike Jackson :
> >> You need to have a valid/correct installation of MinGW or MSYS+MinGW or
> >> Cygwin.
> >
> > As a complement to Mike advice you may have a look at
> > Code::Blocks (aka C::B) too, it's a cross-platform IDE working
Mike, Eric & John - thanks very much for the help.
I will work on these ideas.
Regards,
Vikas
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf
> Of John Drescher
> Sent: 20 January 2010 18:53
> To: Eric Noulard
> Cc: cmake@cmake.org
> Subjec
> 2010/1/20 Mike Jackson :
>> You need to have a valid/correct installation of MinGW or MSYS+MinGW or
>> Cygwin.
>
> As a complement to Mike advice you may have a look at
> Code::Blocks (aka C::B) too, it's a cross-platform IDE working on Windows
> and there is downloadable installer which comes b
2010/1/20 Mike Jackson :
> You need to have a valid/correct installation of MinGW or MSYS+MinGW or
> Cygwin.
As a complement to Mike advice you may have a look at
Code::Blocks (aka C::B) too, it's a cross-platform IDE working on Windows
and there is downloadable installer which comes bundled with
2010/1/20 John Drescher :
>> Navigate to a CLEAN build directory and invoke either cmake or cmake-gui
>>
>
> Out of source builds work great here. You keep your source in one tree
> and your builds in other trees.
Hi Vikas,
May be you could read the FAQ for knowing more about out-of-source:
http:
> Navigate to a CLEAN build directory and invoke either cmake or cmake-gui
>
Out of source builds work great here. You keep your source in one tree
and your builds in other trees. For me its a choice between 32 and 64
bit builds for different microsoft compilers.
I have my source trees inside of
You need to have a valid/correct installation of MinGW or MSYS+MinGW or Cygwin.
After you get one of those installed and working correctly then it is
a matter of telling CMake you want to generate makefiles for one of
those systems.
So, if you want to use MinGW with the new GCC 4.4 compiler, the
Thanks for the quick reply Mike.
Regards,
Vikas
> -Original Message-
> From: Mike Jackson [mailto:mike.jack...@bluequartz.net]
> Sent: 20 January 2010 17:21
> To: Chauhan, Vikas
> Cc: cmake@cmake.org
> Subject: Re: [CMake] How to customise filters in cmake generated
projects for
> VS2008
Hi,
At present I have written my source code for VS2008. I use cmake to
generate VS2008 project files.
If I wanted to switch the compiler to gcc then is it possible to use the
same cmakelists.txt that I have in my source tree & generate the nmake
files or makefiles or vcproj files to use gcc compi
On Wednesday 20 January 2010, Christian Ehrlicher wrote:
> > Von: Hendrik Sattler
> > Zitat von Christian Ehrlicher
> >
> > > I'm using QT4_CREATE_TRANSLATION() to automatically update my
> > > ts-files for translations. Now my problem is that cmake is to smart
> > > and deletes my generated ts-fil
On Wednesday 20 January 2010, David Genest wrote:
> > Ok, so it is definitely cross compiling.
> > In the sense that CMAKE_CROSSCOMPILING needs to be set (which indicates
> > e.g.
> > to TRY_RUN() that it cannot run the executables).
>
> Ok, so can I hard-code this in the generator? Because the onl
SOURCE_GROUP("ProjectInclude" FILES ${SOME_HEADERS} )
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Wed
Thanks for the suggestions.
I've decided to do inside our subversion repository, since I need to
maintain a branch for this project anyway. There is no point scripting
the cutting down since I only have to do it once, carefully, on the
repository branch.
Thanks again.
Ian.
Michael Jackson w
Hi,
Would you have any ideas on how I could organise the filters that are
present in the Cmake generated vcproj files. At present it just
generates filters "Source Files" & "Header Files" .
If I want to include header files from different functional areas then I
how can I create new filters, for
hi,
i started to work on your scripts. very nice work!
unfortunately, i couldnt find the problem, and i cant reproduce it with my
scripts. there must be a difference somewhere.
cheers,
keyan
On 19 Jan 2010, at 00:30, Judicaël Bedouet wrote:
> Hi,
>
> Effectively, I have reproduced your two
Hi all,
I noticed a behaviour of CMAKE_CONFIGURATION_TYPES and CMAKE_BUILD_TYPE
that is close to wizardry in my opinion when it comes to 'make install'
It seems that 'make install' prefers to use "install configurations"
that are predefined in CMake (i.e. debug, minsizerel, release, etc.)
over us
On 01/20/2010 07:59 AM, Christian Ehrlicher wrote:
Von: Hendrik Sattler
Zitat von Christian Ehrlicher
I'm using QT4_CREATE_TRANSLATION() to automatically update my
ts-files for translations. Now my problem is that cmake is to smart
and deletes my generated ts-files during 'make clean'. Is
> Von: Hendrik Sattler
> Zitat von Christian Ehrlicher
> > I'm using QT4_CREATE_TRANSLATION() to automatically update my
> > ts-files for translations. Now my problem is that cmake is to smart
> > and deletes my generated ts-files during 'make clean'. Is there a
> > way to work around this
> Ok, so it is definitely cross compiling.
> In the sense that CMAKE_CROSSCOMPILING needs to be set (which indicates
> e.g.
> to TRY_RUN() that it cannot run the executables).
Ok, so can I hard-code this in the generator? Because the only place which I
see that the CMAKE_CROSSCOMPILING variable
Zitat von Christian Ehrlicher :
I'm using QT4_CREATE_TRANSLATION() to automatically update my
ts-files for translations. Now my problem is that cmake is to smart
and deletes my generated ts-files during 'make clean'. Is there a
way to work around this? In general it's fine that cmake dele
Look at the CMake FAQ: there's an example that adds a mode called
"Maintainer":
http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_extend_the_build_modes_with_a_custom_made_one_.3F
Ryan
On 1/20/10 5:52 AM, Surya Kiran Gullapalli wrote:
Hello all,
I'm using cmake 2.8 to generage VS2005 project files
Hello all,
I'm using cmake 2.8 to generage VS2005 project files. By default, we've 4
build configurations Debug, Release, MinSizeRel, RelWithDebInfo.
I want to have a different Build configuration, The cxxflags, definitions
(which we add with Add_Definitions) are different from what I've with the
Hi,
I'm using QT4_CREATE_TRANSLATION() to automatically update my ts-files for
translations. Now my problem is that cmake is to smart and deletes my generated
ts-files during 'make clean'. Is there a way to work around this? In general
it's fine that cmake deletes the output of an add_custom_co
Zitat von Marc Kammer :
ADD_LIBRARY(ObjectManager STATIC /homes/myNameprogram2/src/theOtherProg.cpp)
to CMakeLists.txt in the "first dir".
If I now try to compile theProg.cpp I get the following error message:
-- Build files have been written to: /homes/myName/program1/src/make
[ 50%] Built tar
On Fri, Jan 15, 2010 at 6:59 PM, Alexander Neundorf wrote:
> On Friday 08 January 2010, Ryan Pavlik wrote:
> > On Thu, Jan 7, 2010 at 4:00 PM, Jed Brown wrote:
> > > On Thu, 07 Jan 2010 15:54:33 -0600, Ryan Pavlik
> > >
> > > wrote:
> > > > If you use the _LIBRARIES variable, you don't need to
Dear All,
I've recently being trying to package ParaView into a tarball using cpack.
However, I've found that a lot of the shared libraries (such as mpi, ffmpeg,
ssl) are not included in the tarball. Is there a way to force the inclusion
of all the libraries the paraview executable is dependent on
Hello,
I have a seemingly easy problem.
I develop a program and try to include some source code file (also developed
by me) that lies in an external directory:
first dir:
/homes/myName/program1/src/
->theProg.cpp
second dir:
/homes/myName/program2/src/
->theOtherProg.hpp
->theOtherProg.cpp
The
35 matches
Mail list logo
