Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#11 Shared library (for python module), python setup.py

open
nobody
None
5
2011-04-17
2005-11-11
Sebastien Maret
No

Currently if one installs GDL standalone version and GDL as a Python
module, GDL needs to be built twice. It would be great to build a shared
library that both the standalone and the python module would use. Also
I would prefer to have the python module as a separated package that
one could install in a more conventional way (i.e. python setup.py
install).

Discussion

  • Here's a relevant message from Orion suggesting simply installing the GDL.so instead of writing a setup.py:

    On 04/14/2011 05:27 PM, Sylwester Arabas wrote:
    > > Which I move to /usr/lib64/python2.7/site-packages/GDL.so
    > > Perhaps this could get fixed?
    > Anyone having experience with writing setup.py?
    > Or maybe something like here:
    > http://plplot.svn.sourceforge.net/viewvc/plplot/trunk/bindings/python/CMakeLists.txt

    Yeah, I would just use cmake to install. Something like

    install(
    TARGETS plplot_widgetmodule _plplotcmodule
    EXPORT export_plplot
    LIBRARY
    DESTINATION ${PYTHON_INSTDIR}
    )

    from the above file.

    --
    Orion Poplawski

     
    • summary: Shared library --> Shared library (for python module), python setup.py