Jon Fox wrote:
> The installation is on WindowsXP (yuck!) and unfortunately I don't have a
> copy of MS VC, so for now I'll try LabPython with python 2.2. If that works
> and I get ambitious I'll try and get my hands on VC6 and try to recompile.
Well as said there should be actually a VI, called "PYTHON Set Server Path.vi"
to actually change the python DLL the intermediate DLL is trying to link to.
I'm not really sure anymore how well that worked once the DLL was already used
for executing a Python script and in such might have a problem if you try to
change the path while a VI is loaded which uses the scrupt node configured to
use the Python plugin or try to change the path while there has been an
interactive session (the VI library interface of LabPython) opened but it did
work at some place for sure when called as first function in a LabVIEW program
before any other LabPython VIs on my Windows 2000 system with a prelease 2.3
python DLL.
> Right now I'm a gcc 3.4 man.
You should be able to create Windows DLLs with the MinGW toolchain which is
based on gcc as compiler. But I never tried this as I'm lazy and have Visual C
already installed for my other work on this machine.
> Thanks for the input. Perhaps I'll come to like G.
Well for scripting Python is a lot better. But for application development I
definitely prefer LabVIEW (and also can understand it much better ;-).
Rolf Kalbermatter
CIT Engineering Nederland BV tel: +31 (070) 415 9190
Treubstraat 7H fax: +31 (070) 415 9191
2288 EG Rijswijk http://www.citengineering.com
Netherlands mailto:rol...@ci...
|
