* What version of CMake are you using?
2.8.11
* What generator are you using?
MinGW Makefiles
* What is in the CMakeFiles/*/CMake*Compiler.cmake files
for values like CMAKE_C_IMPLICIT_LINK_LIBRARIES?
CmakeCCompiler.cmake:
set(CMAKE_C_IMPLICIT_LINK_LIBRARIES
"mingw32;moldname;mingwex;msvcr
I ended up writing a macro to find libsqlite3 with this:
macro (FindSQLite3)
# Look for the library.
# find_path(SQLITE3_INCLUDE_DIR NAMES libsqlite3)
find_path(SQLITE3_INCLUDE_DIR NAMES sqlite3.h)
find_library(SQLITE3_LIBRARY NAMES libsqlite3)
After using VTK for sometime I want to add the opengl functionality. I
went back to CMake and set the flag VTK_USE_QVTK_QTOPENGL – TRUE.
The configuration went fine but at the end of the compilation I received
the following error and was wondering if anyone had this problem:
Building CXX obj
On 05/31/2013 01:35 PM, Alain Leblanc wrote:
> What happens when enable_language(Fortran) is invoked and CMake
> can not find the gfortran shared libraries?
CMake does not actually search for the libraries. It runs the Fortran
compiler front-end to build a test executable and passes options to
as
What happens when enable_language(Fortran) is invoked and CMake can not
find the gfortran shared libraries? Would an error message be issued?(Of
course I could just write a test case.)
I'm asking because I'm using a couple of Fortran programs in a big C++
project, and I don't use enable_language()
Adam Wolf wrote:
> If this gets looked at, maybe we can add my Linux FindPythonLibs
> improvements at the same time? ;)
Once you find a maintainer for the Python modules he or she may approve this.
Eike
--
signature.asc
Description: This is a digitally signed message part.
--
Powered by www.ki
If this gets looked at, maybe we can add my Linux FindPythonLibs
improvements at the same time? ;)
http://cmake.3232098.n2.nabble.com/FindPythonLibs-Bug-0013794-fix-td7584055.html
Adam Wolf
On Fri, May 31, 2013 at 11:54 AM, Jeremy Carter wrote:
> Hi,
>
> It has been established that the FindPyt
On 05/31/2013 05:47 AM, Leek, Jim wrote:
> Oh, if there any cmake way to get the fortran link flags
> I need to pass to g++? I know -lgfortran is all I need in
> this case, but if there was a generic way to get cmake to
> figure it out for me, that would be nice.
CMake is supposed to figure this o
Hi,
It has been established that the FindPythonLibs module fails to find
64-bit Python on Win7 64-bit, due to the fact that CMake can't read
the 64-bit portion of the Windows Registry (and that's where the
module looks to find Python). See:
http://www.cmake.org/Bug/view.php?id=11303 .
I made a te
Rolf Eike Beer wrote
> Even too complicated ;) I have no idea about this specific problems, but
> some
> general remarks.
Thank you for the tips, I appreciate it :)
Finally I solved the problem. There was no compatibility between x64 mingw
and my x32 SDL libs, the solution (obviously) is to get
thanks a lot David!
this works very nicely.
best regards,
radovan
On Fri, May 31, 2013 at 4:34 PM, David Cole wrote:
> > this does not seem to be the case for Experimental/Nightly.
> > inspecting the targets in the Makefiles i can see ARGS in test
> > but not in Experimental/Nightly.
>
> > do
Hi,
I am trying to build an xcode project using cmake, but I am having some
problems including dylib (libsqlite3.dylib).
Was using:
target_link_libraries(${Target} libsqlite3.dylib)
but i think i am going about it the wrong way.
Any help would be appreciated
--
Powered by www.kitware.com
Vis
> this does not seem to be the case for Experimental/Nightly.
> inspecting the targets in the Makefiles i can see ARGS in test
> but not in Experimental/Nightly.
> do you know of a way/workaround to
> run (sequential) Experimental/Nightly tests
> on N procs in parallel?
Just run it directly inst
dear all,
it is possible to run "make test" in parallel
using several processors using:
$ ARGS=-j4 make test
this does not seem to be the case for Experimental/Nightly.
inspecting the targets in the Makefiles i can see ARGS in test
but not in Experimental/Nightly.
do you know of a way/workaround
On Fri, 31 May 2013 09:47:47 +
"Leek, Jim" wrote:
Oh, if there any cmake way to get the fortran link flags
I need to pass to g++? I know -lgfortran is all I need in
this case, but if there was a generic way to get cmake to
figure it out for me, that would be nice.
I am not aware of an
Oh, if there any cmake way to get the fortran link flags I need to pass to g++?
I know -lgfortran is all I need in this case, but if there was a generic way to
get cmake to figure it out for me, that would be nice.
- Original Message -
From: Arjen Markus [mailto:arjen.mar...@deltares.nl]
Actually, I'm not sure why it works on Linux either. That really threw me.
That's for the tip on building shared. That actually did work. I would really
like a static build, but I guess I'm just going to have to add an if(Windows)
if(gfortran) clause or something, huh?
-Original Message-
Hi Jim,
I do not quite know why this works fine on Linux, but the
issue is caused by the C++ part of the link step. As you
are using g++ to link all the C++ runtime libraries, you
need to tell it what Fortran runtime libraries to add.
Linking with gfortran automatically ensures all these
librarie
Hi, I recently rebuilt an old build system with cmake. It works well on Linux,
but part of the idea of using cmake was to make it more portable. Now I'm
working on the Windows port, but I'm having issues with the Fortran libraries.
The program itself is C++, but it has a number of optional th
19 matches
Mail list logo
