That's 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
Python files into /usr/local/lib/python2.5/site-
Yes. This was an unforeseen side affect when Mac changed the default compiler
mixed with a fix in CMake that changed the default C compiler from gcc to cc
(previously you would get clang's CPP compile and gcc's C compiler).
In general you want CUDA to use the same compiler as the rest of the ho
Hi,
FindCUDA.cmake sets CUDA_HOST_COMPILER to CMAKE_C_COMPILER. I think that
the CUDA_HOST_COMPILER variable was introduced in cmake 2.8.10. The issue
is that on macosx, CMAKE_C_COMPILER defaults to /usr/bin/cc which is clang,
and clang is not a supported cuda compiler. One workaround is to set
Hi,
Am Dienstag, 26. März 2013 schrieb sandrews :
> Hi,
>
> My project is primarily C and C++, but also includes some Python code. I
> can get everything to build fine, and my CMakeLists.txt files uses the
> INSTALL(TARGETS ...) to so that the user can install the compiled code to
> the proper p
Hi,
My project is primarily C and C++, but also includes some Python code. I
can get everything to build fine, and my CMakeLists.txt files uses the
INSTALL(TARGETS ...) to so that the user can install the compiled code to
the proper place. However, part of the installation is to copy the Python
2013/3/26 Pietro Moras :
> My fault, certainly, dear Mr. Eric Noulard, but evidently my question has
> not been understood.
No "fault" at all.
>The question here is NOT how to distribute a Python (3) source project,
> but the setup for an ordinary “.exe” program, capable of autonomous
> execu
My fault, certainly,
dear Mr. Eric Noulard, but evidently my question has not been understood. The
question here is
NOT how to distribute a Python (3) source project, but the setup for
an ordinary “.exe” program, capable of autonomous execution as
any normal program as commonly intended. That is
Hi,
I'm currently working on porting a project Mac OS X and need some help with
some things.
1) Is it possible to preserve the source code hierarchy in the generate
project? Having every source listed in a single level doesn't really help.
I've tried setting the property "set_property(GLOBAL PROP
Hi,
I'm currently working on porting a project Mac OS X and need some help with
some things.
1) Is it possible to preserve the source code hierarchy in the generate
project? Having every source listed in a single level doesn't really help.
I've tried setting the property "set_property(GLOBAL PROP
