Mailinglist Archive: zypp-devel (7 mails)

[Klaus Kaempf <kkaempf@xxxxxxx>]

* Michael Andres <ma@xxxxxxx> [Dec 01. 2009 14:29]:
>  
>  FIND_PACKAGE(PythonInterp REQUIRED)
> -EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE} -c "from sys import stdout; 
> from distutils import sysconfig; stdout.write(sysconfig.get_python_lib())" 
> OUTPUT_VARIABLE PYTHON_LIB_PATH)
> +EXECUTE_PROCESS(COMMAND ${PYTHON_EXECUTABLE} -c "from sys import stdout; 
> from distutils import sysconfig; stdout.write(sysconfig.get_python_lib(1))" 
> OUTPUT_VARIABLE PYTHON_LIB_PATH)

Thats not completely accurate. You need two pathes:

1. PYTHON_LIB_PATH  - for generic Python files (all .py files)
2. PYTHON_ARCH_PATH - for arch-specific files (all .so files)

Swig usually generates two binding files. One .so file with a 'raw'
api and one .py file to make the raw api usable.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx