Hi,
I'm new to cmake and want to port a C++ project which is now built using
autotools to cmake build system.
The project has some libraries (we call them modules) which are used in two
applications. The applications uses lt_dladdsearchdir to add the path where to
search the modules and then
Hi list,
I try to write a cmake script for a python module. Its finally working
now, but the solution I came up with is not very nice.
1. Finding the correct python environment:
I have two python frameworks on my mac: Python2.5 which comes with OS
X, and python2.6 from macports. If I just
Hi Alok:
I have changed the subject line to something more appropriate.
On 2010-06-16 22:25-0700 Alok Govil wrote:
Alan wrote:
Isn't that the complete issue? My experience (under Wine, but the
principle
is the same) is you must have mingw32-make.exe on your PATH in order for
-G
MinGW
Hi Alan,
Just like CMake is able to distinguish different versions of Visual Studio,
would it distinguish MinGW-32 with MinGW-64 also (which means either both
would be in path simultaneously, or neither would be, and cmake picks the
right one based on the generator specifed)? Let me
On 2010-06-17 16:23:09 +0200, Janosch Peters said:
3. Copy python files during installation
The python module needs some python files along with the compiled C
module. Currently, I just copy all the stuff using cmakes file()
command. That means, all files are created when the user types in
On Thu, Jun 17, 2010 at 3:16 PM, Scott Johnson
scott.john...@neuwave.com wrote:
On a whim I totally changed the path to a different drive and naming
structure and tried again. I was able to fully configure and generate the
solution. Even after I set the options I was originally trying.
On 6/17/2010 11:07 AM, Alok Govil wrote:
Hi Alan,
Just like CMake is able to distinguish different versions of Visual
Studio,
would it distinguish MinGW-32 with MinGW-64 also (which means
either both
would be in path simultaneously, or neither would be, and cmake
picks the
right one
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via d2c75bd0014099019e85bc13e956f4c7f4cc8441 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via abe355ef1ca075c78dfea75f808a256b052699ec (commit)
from
