Re: [CMake] cmake 3.12 - python libs / 32 / 64 bits

FYI, I just deliver a MR ( https://gitlab.kitware.com/cmake/cmake/merge_requests/2624) which fix the problem of the selection of the library with the wrong architecture. Le jeu. 15 nov. 2018 à 10:00, Eric Noulard a écrit : > Le jeu. 15 nov. 2018 à 09:47, Stéphane Ancelot > a écrit : > >> I

Re: [CMake] cmake 3.12 - python libs / 32 / 64 bits

Le jeu. 15 nov. 2018 à 09:47, Stéphane Ancelot a écrit : > I agree. That was a debug snippet...but is wrong ... I setted up again the > toolchain, but does not help. > If you are using a proper toolchain for 32bit compilation. It looks like a bug in the find_package for Python in the

Re: [CMake] cmake 3.12 - python libs / 32 / 64 bits

I agree. That was a debug snippet...but is wrong ... I setted up again the toolchain, but does not help.  So, I know where are include_dirs and libs  for 32 bits cross compiling, I have to hardcode it like this ?  add_library(python SHARED IMPORTED)  set_target_properties( python PROPERTIES

Re: [CMake] cmake 3.12 - python libs / 32 / 64 bits

The way you proceed is wrong. The system configuration is determined during the 'project' function call. Setting information after this call is useless. So, in your example, on a 64bit system, the compilation configuration will be 64bit (variable CMAKE_SIZEOF_VOID_P has value 8). This explain why

[CMake] cmake 3.12 - python libs / 32 / 64 bits

Hi, My system is 64 bits but I can cross compile python c modules for 32 bits . Unfortunately I don't manage to retrieve python 32 libs , always the 64 bits version is found. here is what I tried : cmake_minimum_required(VERSION 3.10) project(py_autom) set(CMAKE_SYSTEM_PROCESSOR "i686")

Re: [CMake] cmake vs. Python 3.4

Yes. That did the trick. Sorry for the noise. On 23 Dec 2016 23:52, "Dan Liew" wrote: > > > On 23 Dec 2016 7:58 pm, "Lev" wrote: > > Hi list, > > > I have this: > > FIND_PACKAGE(PythonInterp) > > and cmake finds this: > > -- Found PythonInterp:

Re: [CMake] cmake vs. Python 3.4

Am Samstag, 24. Dezember 2016, 12:06:10 schrieb Rolf Eike Beer: > Am Freitag, 23. Dezember 2016, 20:57:49 schrieb Lev: > > Hi list, > > > > > > I have this: > > > > FIND_PACKAGE(PythonInterp) > > > > and cmake finds this: > > > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9")

Re: [CMake] cmake vs. Python 3.4

Am Freitag, 23. Dezember 2016, 20:57:49 schrieb Lev: > Hi list, > > > I have this: > > FIND_PACKAGE(PythonInterp) > > and cmake finds this: > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9") > > However, 3.4 is also installed. How can I specify to find 3.4? > > If I say: >

Re: [CMake] cmake vs. Python 3.4

On 23 Dec 2016 7:58 pm, "Lev" wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say:

Re: [CMake] cmake vs. Python 3.4

> > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. > The standard Python distribution for versions 3 or greater installs a binary called `python3`, not `python`. That is the standard.

Re: [CMake] cmake vs. Python 3.4

On Fri, 23 Dec 2016 12:53:30 -0800 (PST) "Alan W. Irwin" wrote: > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. Ok. Thanks both of you. Merry XMAS,

Re: [CMake] cmake vs. Python 3.4

On Friday, December 23, 2016 12:53:30 PM Alan W. Irwin wrote: > On 2016-12-23 20:57+0100 Lev wrote: > > Hi list, > > > > > > I have this: > > > > FIND_PACKAGE(PythonInterp) > > > > and cmake finds this: > > > > -- Found PythonInterp: /usr/bin/python (found version "2.7.9") > > > > However,

Re: [CMake] cmake vs. Python 3.4

On 23/12/16 20:53, Alan W. Irwin wrote: On 2016-12-23 20:57+0100 Lev wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say:

Re: [CMake] cmake vs. Python 3.4

On 2016-12-23 20:57+0100 Lev wrote: Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say: set(Python_ADDITIONAL_VERSIONS 3.4)

[CMake] cmake vs. Python 3.4

Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say: set(Python_ADDITIONAL_VERSIONS 3.4) FIND_PACKAGE(PythonInterp 3 REQUIRED) still no

Re: [CMake] CMake for Python 3

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

Re: [CMake] CMake for Python 3

of autonomous execution as any normal program as commonly intended. That is, without requiring the presence of the programming language, be it Python 3 or any other, used for developing it. I think I get it. But it is not in the feature of CMake to transform a python application into an autonomous

[CMake] CMake for Python 3

I'd love to be reassured that CMake (+CPack) is a “right” tool for: Building the distribution package for a complex Python 3 (+PyQt) application, mainly aimed at the Windows platform. My goal is a single install file that, out of an original Python 3 application, will generate an ordinary “.exe”

Re: [CMake] CMake for Python 3

2013/3/25 Pietro Moras studio...@hotmail.com I'd love to be reassured that CMake (+CPack) is a “right” tool for: Building the distribution package for a complex Python 3 (+PyQt) application, mainly aimed at the Windows platform. If your application is pure python why would you use CMake

[CMake] CMake and Python

Hi all, I don't know if anybody would find this useful or not, but I thought I'd let everybody know about it and if somebody would like to use it, I can figure out the best way to get it out there. We have a fairly extensive python library that we use to setup our code and manipulate our

[CMake] cmake for python projects

Hello, when we were considering to use D for our multi-platform project we did some research about appropriate build system and ended with the two: waf cmake with more preference for the latter due to its ability to create binary packages for Mac and Windows (afaik, using NSIS installer) with