| 1 |
BUILDING AND INSTALLING ASCEND |
| 2 |
|
| 3 |
Thanks for downloading ASCEND! We hope you'll find it straight- |
| 4 |
forward to set up and run ASCEND. If you have any comments on |
| 5 |
your experience with this, we're very keen to hear about that. |
| 6 |
Please check out the up-to-date contact details at: |
| 7 |
https://pse.cheme.cmu.edu/wiki/view/Ascend/WebHome |
| 8 |
|
| 9 |
There are older versions of this document, which include instructions |
| 10 |
on how to build ASCEND with GNU Autotools. This may or may not work |
| 11 |
with the version are currently looking at. |
| 12 |
https://pse.cheme.cmu.edu/svn-view/ascend/code/trunk/INSTALL?view=log |
| 13 |
|
| 14 |
----- |
| 15 |
BUILDING ON LINUX AND WINDOWS |
| 16 |
|
| 17 |
To build ASCEND we now recommend using SCons. This is supported |
| 18 |
both on Windows (using the MinGW toolset) and Linux. |
| 19 |
|
| 20 |
ASCEND provides two possible interfaces. The older, more mature |
| 21 |
GUI is based on Tcl/Tk. A newer interface that is more in keeping |
| 22 |
with modern GUI design is implemented using PyGTK, but it is still |
| 23 |
missing some functionality. |
| 24 |
|
| 25 |
Using SCons 0.96.91 or newer, see your build options by typing |
| 26 |
|
| 27 |
scons -Qh |
| 28 |
|
| 29 |
You can add your build options to a file in this directory |
| 30 |
which you can create, called 'config.py'. |
| 31 |
|
| 32 |
Then to build ASCEND, type |
| 33 |
|
| 34 |
scons |
| 35 |
|
| 36 |
SCons will tell you what version(s) of ASCEND it is able to build. |
| 37 |
The PyGTK interface requires Python (which is present if you have |
| 38 |
SCons). The Tcl/Tk interface requires that you have Tcl/Tk and |
| 39 |
TkTable installed on your system. |
| 40 |
|
| 41 |
For updates on this information, please check |
| 42 |
https://pse.cheme.cmu.edu/wiki/view/Ascend/BuildingAscend |
| 43 |
|
| 44 |
For specific information on building the Python interface and |
| 45 |
setting up the PyGTK GUI, please see |
| 46 |
https://pse.cheme.cmu.edu/wiki/view/Ascend/PythonWrapper |
| 47 |
|
| 48 |
------ |
| 49 |
INSTALLING ON LINUX |
| 50 |
|
| 51 |
To then install ASCEND, you will need to have write access to the |
| 52 |
directories INSTALL_DATA, INSTALL_BIN as specified in your |
| 53 |
SCons configuration. You can then type |
| 54 |
|
| 55 |
scons install |
| 56 |
|
| 57 |
------ |
| 58 |
INSTALLING ON WINDOWS |
| 59 |
|
| 60 |
More details to come here. For the PyGTK GUI, you can install |
| 61 |
ASCEND by running the 'create.nsi' script (using the NSIS |
| 62 |
installer-creator from http://nsis.sf.net/ which is free) |
| 63 |
then running the created installation package. |
| 64 |
|
| 65 |
------ |
| 66 |
CREATING AN RPM/DEB PACKAGE |
| 67 |
|
| 68 |
Many users prefer to keep their systems clear of unpackaged |
| 69 |
software. For this reason, we aim to provide the ability to build |
| 70 |
SCons as an RPM package. If you are in your home directory, type |
| 71 |
|
| 72 |
rpmbuild -ta ascend-NNNNN.tar.bz2 |
| 73 |
|
| 74 |
This will pull out the 'spec' from from the source package, |
| 75 |
which hopefully will be up to date in correspondance with the |
| 76 |
package version number NNNNN. |
| 77 |
|
| 78 |
You will then be able to install ASCEND using something like |
| 79 |
|
| 80 |
rpm -i ~/rpm/ascend-NNNNN-0.jdpipe.i386.rpm |
| 81 |
|
| 82 |
Debian/Unbuntu users should find that they can create a usable |
| 83 |
.deb package using the tool 'alien'. We haven't got native |
| 84 |
support for the generation of .deb packages at this stage. |
| 85 |
|
| 86 |
------ |
| 87 |
GETTING SUPPORT AND FURTHER INFORMATION |
| 88 |
|
| 89 |
For support with ASCEND, details of mailing lists and other |
| 90 |
useful information, please visit |
| 91 |
|
| 92 |
ASCEND user's website: |
| 93 |
http://ascend.cheme.cmu.edu/ |
| 94 |
|
| 95 |
ASCEND developer's wiki: |
| 96 |
https://pse.cheme.cmu.edu/wiki/view/Ascend/WebHome |
Parent Directory
| 
Revision Log