I have been developing Fortran 2003 code on a Mac system. Because Xcode comes
with a very old version of gcc its Fortran compiler has poor support for newer
versions of Fortran, so I have been using newer versions of gcc installed using
Mac Fink, and run from either the terminal application, or
Thank you.
At the end, I realized that I could just call the standard Python installer
from CMake. This led to a more reliable install process and also a vastly
cleaner CMakeLists.txt file. My line for installing the Python code is
simply:
install(CODE "execute_process(COMMAND python setup.py i
Hi,
This problem is now resolved, my tool chain already had a definition
for RINT which was causing the problem, but cmake was unable to detect it.
I commented out this part from my_global.h file which solved the problem.
With Regards,
Niranjan
On Wed, Mar 20, 2013 at 6:03 PM, Niranjan M wro
Hi,
I'm using CMake 2.10.2 the VS2012(VC11) generator.
I summed-up my problem in the last paragraph.
I'm trying to do this:
add_test(
NAME ${TEST_PROJECT_NAME}
WORKING_DIRECTORY ${TEST_WORKING_DIR}
COMMAND ${TEST_PROJECT_NAME}
)
In my current setup, I need ${TEST_WORKING_DIR} to be de
Am 2013-03-27 05:46, schrieb Steve Andrews:
Thats very helpful. Thank you.
My other question was about how to get CMake to create directories at
installation time. Do you, or someone else, have suggestions about
that? Despite your advice, I think that I want the "make install"
step to put Pyt
Hello, for my project I'd like to be able to configure a 32 bit build
with GCC in a 64 bit Linux environment by setting variables from command
line interface. As far as I understand of CMake, this can be
accomplished by setting CMAKE_CXX_FLAGS and CMAKE_SHARED_LINKER_FLAGS to
"-m32" (my project
