[pyrwi] r11 committed - Clean up and add 64bit notes.

1 view
Skip to first unread message

py...@googlecode.com

unread,
Apr 10, 2010, 10:17:34 AM4/10/10
to pyrwi...@googlegroups.com
Revision: 11
Author: daniel...@gmail.com
Date: Sat Apr 10 07:17:16 2010
Log: Clean up and add 64bit notes.
http://code.google.com/p/pyrwi/source/detail?r=11

Modified:
/wiki/Install.wiki

=======================================
--- /wiki/Install.wiki Sat Apr 10 06:33:35 2010
+++ /wiki/Install.wiki Sat Apr 10 07:17:16 2010
@@ -1,4 +1,4 @@
-#Installation Summary. Taken from install.txt in the trunk.
+#summary Installation Summary. Taken from install.txt in the trunk.

Installing the pyrwi package
# Install all the support libraries and tools listed on
http://drlock.com/projects/pyrwi/docs/install.php
@@ -6,17 +6,17 @@
# The DAQmx DLL is built with MSVC which makes linking to a GCC
project difficult. The current solution requires building a GCC compatible
library.
* Install pexports
http://www.emmestech.com/software/pexports-.43/download_pexports.html by
copying the EXE into C:\msys\1.0\bin
* In MSYS change to nidaqmx/gccLib
- * Run the ./build.sh script. This script will make many intermediate
files, but the end result is libnidaqmx.a this is the new version of the
library.
+ * Run the ./build.sh script. This script will make many intermediate
files, but the end result is `libnidaqmx.a` this is the new version of the
library.
* This only has to be done once, unless you install a new version of
DAQmx.
# Now the nidaqmx python module can be built and installed.
* Change to the nidaqmx directory.
- * Edit the build.sh scipt so that paths are correct for your
installation.
- * Run ./build.sh This will use SWIG to generate C & Python code and
then use GCC to compile the final package.
- * Edit the install.sh scipt so that paths are correct for your
installation.
- * Run ./install.sh which will copy of nidaqmx.py _nidaqmx.pyd into
the Python site-packages directory.
+ * Edit the `build.sh` scipt so that paths are correct for your
installation.
+ * Run `./build.sh` This will use SWIG to generate C & Python code
and then use GCC to compile the final package.
+ * Edit the `install.sh` scipt so that paths are correct for your
installation.
+ * Run `./install.sh` which will copy of `nidaqmx.py` `_nidaqmx.pyd`
into the Python site-packages directory.
# The PyRWI project is in its early stages, so there isn't an installer.
- * You will have to copy the files to the Python library. This is
usually at c:\python26\lib\site-packages or something similar
- * Copy the pyrwi directory (the one containing __init__.py)
+ * You will have to copy the files to the Python library. This is
usually at `c:\python26\lib\site-packages` or something similar
+ * Copy the pyrwi directory (the one containing `__init__.py`)
* If you are willing to help setup a distutils installer, please
contact us through the mailing list.
# You can test the installation by starting IPython or IDLE and typing:
{{{
@@ -24,3 +24,9 @@
import pyrwi
}}}
* If they import without error, you are all set.
+
+=64 bit Notes=
+Most of the libraries needed to run on 64bit seem to be available, but I
am seeing many comments hat SciPy 64bit may be hard to come by
pre-compiled. Here are a couple articles on how to compile yourself:
+ *
http://www.scipy.org/Download#head-f64942d62faddeb27278a2c735e81ef2a7349db0
+ * http://cournape.wordpress.com/2009/03/26/scipy-on-windows-amd64/
+ * http://sites.google.com/site/applegatearchive/software/scipy-on-amd64

Reply all
Reply to author
Forward
0 new messages