Hi,
I just installed the current windows version of SciDavis on my Win7/ x64 system and it works pretty well.
I have Python 2.7 installed on my system, but it is not available withoin SciDavis.
Is the current windows version capable of using Python?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Unfortunately, the latest SciDAVis version for Windows that was capable of use Python was the 1.D5. Since 1.D8 the developers are building Windows versions using MXE (a tool used to build Windows binaries on Linux), and they are not able to include Python support in the Windows package.
Until to 1.D5 version, the Windows binaries for SciDAVis were provided by Mauricio Troviano, but he stopped to contribute with the project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By the way, IMHO, Python scripting is (was, in the "Windows case") one of the best features of SciDAVis, since it provides a powerful tool to automate and improve data analysis. Python support is so important that it was implemented in Microcal Origin since 2015 version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did spend some time on the Python question on Windows builds a
couple of years ago. Basically, the Python build scripts assume that
you are building on the target machine, whereas MXE is a cross
compiler. I ran out of time to work out how to patch it and PyQt to
support cross compilation. Wiser heads than me in the MXE project also
indicated that Python was going to be a tall order.
I also major, major problems trying native MingW builds on Windows. It
wasn't just Python that had issues, but more importantly Qt. I never
got Mauricio's recipe to work. Of course, MingW comes in about 3
different flavours, each with varying levels of being kept up to date,
so this stuff takes an inordinate amount of time. One of the reasons I
switched to MXE - so much just works out of the box, including Qt. And
when time is in short supply, that's important.
You might have more luck doing a Cygwin build of SciDaVis. It will
mean running SciDaVis under an X windows server, but otherwise it will
probably be fairly pain free, as it is closest to a Linux build
environment you'll get on Windows. But as you might be aware, the X11
requirement means it is a non-starter for building standalone
installable packages.
Cheers
--
Dr Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Senior Research Fellow hpcoder@hpcoders.com.au
Economics, Kingston University http://www.hpcoders.com.au
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just installed the current windows version of SciDavis on my Win7/ x64 system and it works pretty well.
I have Python 2.7 installed on my system, but it is not available withoin SciDavis.
Is the current windows version capable of using Python?
Hi,
Unfortunately, the latest SciDAVis version for Windows that was capable of use Python was the 1.D5. Since 1.D8 the developers are building Windows versions using MXE (a tool used to build Windows binaries on Linux), and they are not able to include Python support in the Windows package.
Until to 1.D5 version, the Windows binaries for SciDAVis were provided by Mauricio Troviano, but he stopped to contribute with the project.
By the way, IMHO, Python scripting is (was, in the "Windows case") one of the best features of SciDAVis, since it provides a powerful tool to automate and improve data analysis. Python support is so important that it was implemented in Microcal Origin since 2015 version.
I did spend some time on the Python question on Windows builds a
couple of years ago. Basically, the Python build scripts assume that
you are building on the target machine, whereas MXE is a cross
compiler. I ran out of time to work out how to patch it and PyQt to
support cross compilation. Wiser heads than me in the MXE project also
indicated that Python was going to be a tall order.
I also major, major problems trying native MingW builds on Windows. It
wasn't just Python that had issues, but more importantly Qt. I never
got Mauricio's recipe to work. Of course, MingW comes in about 3
different flavours, each with varying levels of being kept up to date,
so this stuff takes an inordinate amount of time. One of the reasons I
switched to MXE - so much just works out of the box, including Qt. And
when time is in short supply, that's important.
You might have more luck doing a Cygwin build of SciDaVis. It will
mean running SciDaVis under an X windows server, but otherwise it will
probably be fairly pain free, as it is closest to a Linux build
environment you'll get on Windows. But as you might be aware, the X11
requirement means it is a non-starter for building standalone
installable packages.
Cheers
--
Dr Russell Standish Phone 0425 253119 (mobile)
Principal, High Performance Coders
Visiting Senior Research Fellow hpcoder@hpcoders.com.au
Economics, Kingston University http://www.hpcoders.com.au
Thx for all the answers.
I think then it will be better to run it on a virtual Linux- machine...