Sponsored Content
Top Forums Programming Integration of PyQt/PySide issue Post 302761367 by itkalenko on Friday 25th of January 2013 01:47:07 PM
Old 01-25-2013
Thanks for your reply.

The problem was due to mismatch of Qt libs versions.
After that we solved issues with incompatibility of libs that are coming along with Salome (sip) and those that were installed
in the system.

But we still have some issues: We cannot pack commercial PyQt with VendorID in the hidden library.
If i get it right, there is a mention of this possibility in the oficial document "VendorID - Signing Python Interpreters and Modules"
(p.3.1 Creating Restricted Extension Modules).

To figure out how Vedor ID works i created foo.py script that contained couple of functions,
1 class and also foomodule.c file (identical to the one in example Reference Guide 3.1 Creating Restricted Extension Modules)

After that we tried to create a library with the help of commands:

>> python ~/VendorID-1.0.0/sib/sib.py -u foo.py

the folder build_foo is created with files makefile, __main__.c, frozen.c in it

>> make

And we got the next message in the terminal:

gcc -pthread -Xlinker -export-dynamic __main__.o foo.o frozen.o -o foo -lpthread -ldl -lutil -lm -L/usr/local/lib -lpython2.6
/usr/local/lib/libpython2.6.a(dynload_shlib.o): In function
`_PyImport_GetDynLoadFunc':
/home/modeller/Python-2.6.6/Python/dynload_shlib.c:94: undefined reference to `dlsym'
/home/modeller/Python-2.6.6/Python/dynload_shlib.c:130: undefined reference to `dlopen'
/home/modeller/Python-2.6.6/Python/dynload_shlib.c:141: undefined reference to `dlsym'
/home/modeller/Python-2.6.6/Python/dynload_shlib.c:133: undefined reference to `dlerror'
...
/home/modeller/Python-2.6.6/Objects/floatobject.c:972: undefined reference to `pow'
/usr/local/lib/libpython2.6.a(longobject.o): In function
`PyLong_FromString':
/home/modeller/Python-2.6.6/Objects/longobject.c:1610: undefined reference to `log'
/home/modeller/Python-2.6.6/Objects/longobject.c:1610: undefined reference to `log'
collect2: executing lt finished with return code 1
make: *** [foo] Error 1


The issue with PySide still remains: PySide is referring to a lib that has to be located in the system folder /usr/lib/i386-linux-gnu/libpyside-python2.7.so, while in our case all paths should be relative.
 

4 More Discussions You Might Find Interesting

1. AIX

ML integration on Media

Hello to all, Someone knows how to create a AIX Bootable Media with a Maintenance Level integrated on it? Regards. (0 Replies)
Discussion started by: spacewalker
0 Replies

2. Programming

NS3 with MQTT integration. HELP !!!!

Hi, I'm doing my thesis on the NS3 environment. I need to integrate it with mqtt. Mqtt provides a (mosquitto) broker / server, and it expects to have clients connect to it. A client could be a publisher (publishes data on the broker) or a subscriber (receives data from the broker it has subscribed... (4 Replies)
Discussion started by: KishIsrael
4 Replies

3. Solaris

Solaris Integration

I want to integrate two diffrent servers of SUN at different location. How to integrate them.Please help me or give me a link or doc which is useful Regards Kaushal (2 Replies)
Discussion started by: xal_kaushi
2 Replies

4. Linux

Selenium Integration

Hi People, I am trying to run Selenium Scripts on my server. System is a Linux Box and I am accessing it via Putty. I have some basic admin privileges for it. The Steps: 1. A build.xml has been created which has this o RELEASE_ROOT this has been set to the Java Project folder. o... (1 Reply)
Discussion started by: ankur328
1 Replies
DH_PYCENTRAL(1) 						     Debhelper							   DH_PYCENTRAL(1)

NAME
dh_pycentral - use the python-central framework to handle Python modules and extensions SYNOPSIS
dh_pycentral [debhelper options] [-n] [-Xitem] [-V version] [module dirs ...] DESCRIPTION
dh_pycentral is a debhelper program that will scan your package, detect public Python modules and move them in /usr/share/pycentral so that python-central can byte-compile those for all supported Python versions. Extensions are kept into the original installation location. Moving the files to the pycentral location and adding symbolic links to /usr/lib/pythonX.Y/*-packages can be done by setting the environment varibale DH_PYCENTRAL to a string containing the string include-links. Moving the files to the pycentral location can be disabled by setting the environment varibale DH_PYCENTRAL to a string containing the string nomove. The functionality to shorten the time of unavailabilty of files during unpack and configure has been removed (symlinking files in the preinst and not removing the symlinked files on upgrade) in version 0.6.9. You must have filled the XS-Python-Version header to indicate the set of python versions that are going to be supported. dh_pycentral expects the XB-Python-Version for each binary package it is supposed to work on. dh_pycentral will also generate substitution variables: the ${python:Provides} variable will contain versioned provides of the package (if the package's name starts with "python-"). A python-foo package could provide "python2.3-foo" and "python2.4-foo" at the same time. Python extensions have to provide those whereas it's only option for pure python modules. The ${python:Versions} variable should be used to provide the required XB-Python-Version field listing the python versions supported by the package. OPTIONS
module dirs If your package installs python modules in non-standard directories, you can make dh_pycentral check those directories by passing their names on the command line. By default, it will check /usr/lib/$PACKAGE, /usr/share/$PACKAGE, /usr/lib/games/$PACKAGE, /usr/share/games/$PACKAGE, /usr/lib/python?.?/site-packages and /usr/lib/python?.?/dist-packages. Note: only /usr/lib/python?.?/site-packages and the extra names on the command line are searched for binary (.so) modules. -V version If the .py files your package ships are meant to be used by a specific pythonX.Y version, you can use this option to specify the desired version, such as 2.3. Do not use if you ship modules in /usr/lib/site-python. With the new policy, this option is mostly deprecated. Use the XS-Python-Field to indicate that you're using a specific python version. -n, --noscripts Do not modify postinst/postrm scripts. -Xitem, --exclude=item Exclude files that contain "item" anywhere in their filename from being taken into account to generate the python dependency. You may use this option multiple times to build up a list of things to exclude. CONFORMS TO
Python policy, version 0.4.1 (2006-06-20) SEE ALSO
debhelper(7) This program is a part of python-central but is made to work with debhelper. AUTHORS
Raphael Hertzog <hertzog@debian.org> Also includes bits of the old dh_python written by Josselin Mouette <joss@debian.org> who used many ideas from Brendan O'Dea <bod@debian.org>. 2011-04-14 DH_PYCENTRAL(1)
All times are GMT -4. The time now is 09:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy