[CMake] MSYS Generator with Visual Studio compilers

Hello, Due to the relative slowness of mingw32-make.exe (MinGW) compared to make.exe (MSYS) I set out to convert a working MinGW generator project over to MSYS. The project uses Visual Studio CXX and Intel Fortran. Is this even possible? My approach was to treat the toolchain like a cross compi

Re: [CMake] No rule to build mod file

On 12/10/2014 7:49 AM, Alain Miniussi wrote: > Is this something expected ? Parallel builds of Fortran 90 sources with modules are expected to work with the Makefile generator, and known to work on several non-trivial projects. Please post or link a complete example tarball with sources that repr

Re: [CMake] Including another CMakeLists project

If the projects are truly independent, you may also want to look at the external_project command. Regards, Micha On 12/10/2014 03:42 PM, Petr Bena wrote: > I have 3 projects, all using cmake. When I run cmake on each of them > and separately build them, it's all fine. > > When I use include() on

[CMake] 64 bit build of wxWidgets-2.8.12 is not found

Hello, I am using: - Windows 7 Professional 64 Bit - Visual Studio 2010 Professional - CMake 3.0.1 and I have installed wxMSW-2.8.12-Setup.exe to L:\wxWidgets-2.8.12-vc10\ and created 32 bit and 64 bit shared library builds there (see footnote [1]). Now I want to use the 64-bit wxWidgets librari

Re: [CMake] Including another CMakeLists project

I think you may want to try the add_subdirectory() command instead of include(), if you truly have multiple projects that are being built by CMake. The name suggests that it would only work with a hierarchical directory structure, but that is not the case - you can specify absolute paths if necessa

Re: [CMake] Including another CMakeLists project

Yup, that works. Thanks On Wed, Dec 10, 2014 at 3:48 PM, Parag Chandra wrote: > I think you may want to try the add_subdirectory() command instead of > include(), if you truly have multiple projects that are being built by > CMake. The name suggests that it would only work with a hierarchical >

Re: [CMake] Including another CMakeLists project

I would try using add_subdirectory() instead of include() On Wed, Dec 10, 2014 at 9:42 AM, Petr Bena wrote: > I have 3 projects, all using cmake. When I run cmake on each of them > and separately build them, it's all fine. > > When I use include() on these 2 cmake files in 1 of them, so that I >

[CMake] Including another CMakeLists project

I have 3 projects, all using cmake. When I run cmake on each of them and separately build them, it's all fine. When I use include() on these 2 cmake files in 1 of them, so that I could run only 1 cmake and then build them all using 1 make, it fails. I believe that these 3 cmakes are colliding wit

Re: [CMake] CMake Vs 2012 Express 64bit

Not sure, but I believe that is a limitation of the Express edition itself; not a problem with CMake per se. You may want to try the just-released VS 2013 Community Edition instead. If you insist on using 2012 Express, perhaps this link may be of help: http://www.kobashicomputing.com/64-bit-c-deve

[CMake] Target 'copy-construction'/'fork'

Hi, Given a target named Foo, is there a simple/builtin way to create a copy of that target named Bar so that it retains all the properties of Foo but can be independently changed from that point onward i.e. is there a way for CMake targets to follow the semantics of standard C++ objects with

[CMake] CMake Vs 2012 Express 64bit

Hi all, is there a way that CMake create solution files for 64-bit targets? (Visual Studio 2012 Express) Greetings Michael -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support

[CMake] No rule to build mod file

Hi, I am experiencing a problem related with dependencies on fortran mod files. Basically, the "make -j" it's failing with: make[2]: *** No rule to make target `dsfdm3d/inc/modacqui.mod', needed by `dsfdm3d/src/CMakeFiles/dsfdm_sp-exe.dir/main.f90.o'. Stop. mod file are generated as a side e

Re: [CMake] Copying shared libraries in a post-build step

> > > b: in msvc, you cannot debug by right-click on the target -> debug -> > start new instance. > > I can and do all the time. > -- > > Powered by www.kitware.com > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Kitware offers various servi

Re: [CMake] Copying shared libraries in a post-build step

2014-12-10 13:29 GMT+03:00 Sergei Nikulov : > > > 2014-12-10 2:38 GMT+03:00 Walter Gray : > >> Hey all, >> I'm working on a module that will allow me to automatically copy all the >> required .dll files as defined by well-formed import library targets to the >> appropriate location (same folder f

Re: [CMake] Copying shared libraries in a post-build step

> > This sounds more like an install phase... to bring the whole package > > together in one appropriate place. > > > > if( WIN32 ) > > INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION bin > > ARCHIVE DESTINATION lib ) > > else( WIN32 ) > > INSTALL( TARGE

Re: [CMake] Copying shared libraries in a post-build step

2014-12-10 2:38 GMT+03:00 Walter Gray : > Hey all, > I'm working on a module that will allow me to automatically copy all the > required .dll files as defined by well-formed import library targets to the > appropriate location (same folder for windows, Frameworks folder for OSX > bundle, ect). I

Re: [CMake] Copying shared libraries in a post-build step

On Wed, Dec 10, 2014 at 2:14 AM, Tim Blechmann wrote: > > This sounds more like an install phase... to bring the whole package > > together in one appropriate place. > > > > if( WIN32 ) > > INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION bin > > ARCHIVE DESTINATION lib ) > > else( WI

Re: [CMake] Copying shared libraries in a post-build step

> This sounds more like an install phase... to bring the whole package > together in one appropriate place. > > if( WIN32 ) > INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION bin > ARCHIVE DESTINATION lib ) > else( WIN32 ) > INSTALL( TARGET RUNTIME DESTINATION bin LIBRARY DESTINATION