build python source

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

build python source

Mark Brethen-2
According to the readme for “qreduce” the procedure to build the Qt-based GUI for Reduce is:

1. Get a matching PySide binary package following the instructions
   here: http://developer.qt.nokia.com/wiki/PySideDownloads/

2. Go to ../libreduce, and say "make". This will create there a new
   directory <dir> based on your exact machine and OS type.

3. Return here, and say "ln -s ../libreduce/<dir>/RedPy.so".

4. Say "./qreduce.py".


I have installed pyside2 for step 1 made necessary patches to the python source. Steps 2 and 3 are not required, since I have created a libreduce port that installs the RedPy library in ../../lib. A file “qrmodel.py” imports RedPy using the following lines

here = os.path.dirname(os.path.realpath(__file__))
p = Popen("%s/../../config.guess" % here, stdout=PIPE, stderr=PIPE)
config_guess, err = p.communicate()
p = Popen(["%s/../../scripts/findhost.sh" % here, config_guess], stdout=PIPE, stderr=PIPE)
arch, err = p.communicate()
sys.path.append("%s/../libreduce/%s" % (here, arch.rstrip()))

from RedPy import procNew, procDelete, ansNew, ansDelete

I need to comment out those lines that locate RedPy using sys.path.append and supply the correct path to RedPy.so. I can patch this directly and supply the actual path. If I add Python group and set ‘python.add_archflags’ how should the source import this during build.


Mark Brethen
[hidden email]



Reply | Threaded
Open this post in threaded view
|

Re: build python source

Mark Brethen-2
I’ll try to be more specific. This python source does not seem to set the build env. and I don’t see how the python port group will do that. I think the build command needs to set be to "./qreduce.py” and the library path set in “qrmodel.py”. Do I understand this correctly?

Mark Brethen
[hidden email]



> On Oct 27, 2018, at 2:57 PM, Mark Brethen <[hidden email]> wrote:
>
> According to the readme for “qreduce” the procedure to build the Qt-based GUI for Reduce is:
>
> 1. Get a matching PySide binary package following the instructions
>   here: http://developer.qt.nokia.com/wiki/PySideDownloads/
>
> 2. Go to ../libreduce, and say "make". This will create there a new
>   directory <dir> based on your exact machine and OS type.
>
> 3. Return here, and say "ln -s ../libreduce/<dir>/RedPy.so".
>
> 4. Say "./qreduce.py".
>
>
> I have installed pyside2 for step 1 made necessary patches to the python source. Steps 2 and 3 are not required, since I have created a libreduce port that installs the RedPy library in ../../lib. A file “qrmodel.py” imports RedPy using the following lines
>
> here = os.path.dirname(os.path.realpath(__file__))
> p = Popen("%s/../../config.guess" % here, stdout=PIPE, stderr=PIPE)
> config_guess, err = p.communicate()
> p = Popen(["%s/../../scripts/findhost.sh" % here, config_guess], stdout=PIPE, stderr=PIPE)
> arch, err = p.communicate()
> sys.path.append("%s/../libreduce/%s" % (here, arch.rstrip()))
>
> from RedPy import procNew, procDelete, ansNew, ansDelete
>
> I need to comment out those lines that locate RedPy using sys.path.append and supply the correct path to RedPy.so. I can patch this directly and supply the actual path. If I add Python group and set ‘python.add_archflags’ how should the source import this during build.
>
>
> Mark Brethen
> [hidden email]
>
>
>