26 |
|
|
27 |
Using SCons 0.96.91 or newer, see your build options by typing |
Using SCons 0.96.91 or newer, see your build options by typing |
28 |
|
|
29 |
scons -Qh |
scons -Qh |
30 |
|
|
31 |
You can add your build options to a file in this directory |
You can add your build options to a file in this directory |
32 |
which you can create, called 'config.py'. |
which you can create, called 'config.py'. |
33 |
|
|
34 |
Then to build ASCEND, type |
Then to build ASCEND, type |
35 |
|
|
36 |
scons |
scons |
37 |
|
|
38 |
SCons will tell you what version(s) of ASCEND it is able to build. |
SCons will tell you what version(s) of ASCEND it is able to build. |
39 |
The PyGTK interface requires Python (which is present if you have |
The PyGTK interface requires Python (which is present if you have |
48 |
https://pse.cheme.cmu.edu/wiki/view/Ascend/PythonWrapper |
https://pse.cheme.cmu.edu/wiki/view/Ascend/PythonWrapper |
49 |
|
|
50 |
------ |
------ |
51 |
|
RUNNING FOR THE FIRST TIME |
52 |
|
|
53 |
|
If you've build ASCEND from source, you don't need to 'install' |
54 |
|
it before you can run it. The main issue with running from the |
55 |
|
source directories is that you need to set various environment |
56 |
|
variables: |
57 |
|
|
58 |
|
ASCENDLIBRARY |
59 |
|
Location of the 'models' directory, eg ~/src/ascend-NNN/models |
60 |
|
|
61 |
|
LD_LIBRARY_PATH |
62 |
|
Must contain the paths to the ascend shared libraries, in |
63 |
|
particular libascend.so, or for the Tcl/Tk interface, also |
64 |
|
libascendtcl.so. |
65 |
|
|
66 |
|
It can often be easier to simply install in your home directory |
67 |
|
as shown below. |
68 |
|
|
69 |
|
------ |
70 |
|
ISSUES WITH THE TCL/TK INTERFACE |
71 |
|
|
72 |
|
It can sometimes be a bit challenging to build the Tcl/Tk |
73 |
|
interface. ASCEND requires Tcl/Tk version 8.3.5, which is not the |
74 |
|
standard version on modern Linux distributions. A suggested |
75 |
|
approach in this case is to download and install the 'ActiveTcl' |
76 |
|
distribution, version 8.3.5, and to install it in ~/activetcl. |
77 |
|
http://downloads.activestate.com/ActiveTcl/Windows/8.3.5/ |
78 |
|
|
79 |
|
Then, you should be able to build the Tcl/Tk interface as shown: |
80 |
|
|
81 |
|
export LD_LIBRARY_PATH=~/activetcl/lib:~/activetcl/lib/Tktable2.8 |
82 |
|
scons TCL=~/activetcl |
83 |
|
|
84 |
|
------ |
85 |
INSTALLING ON LINUX |
INSTALLING ON LINUX |
86 |
|
|
87 |
To then install ASCEND, you will need to have write access to the |
To then install ASCEND, you will need to have write access to the |
88 |
directories INSTALL_DATA, INSTALL_BIN as specified in your |
directories INSTALL_DATA, INSTALL_BIN as specified in your |
89 |
SCons configuration. You can then type |
SCons configuration. You can then type |
90 |
|
|
91 |
scons install |
scons install |
92 |
|
|
93 |
|
The simplest way to install ASCEND 'off-root' is something like: |
94 |
|
|
95 |
|
scons INSTALL_PREFIX=~/ascroot |
96 |
|
|
97 |
|
Note that if you install (or run) ASCEND off-root, you need to |
98 |
|
ensure that Linux can access the shared libraries. For example, |
99 |
|
in the above case, you would need to add |
100 |
|
|
101 |
|
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/ascroot/lib |
102 |
|
|
103 |
------ |
------ |
104 |
INSTALLING ON WINDOWS |
INSTALLING ON WINDOWS |
108 |
your system (which is free, at http://nsis.sf.net/). Then you |
your system (which is free, at http://nsis.sf.net/). Then you |
109 |
should simply need to type |
should simply need to type |
110 |
|
|
111 |
scons WITH_INSTALLER=1 |
scons WITH_INSTALLER=1 |
112 |
|
|
113 |
This will leave an installer package named 'ascend-setup.exe' |
This will leave an installer package named 'ascend-setup.exe' |
114 |
in the pygtk/interface directory. |
in the pygtk/interface directory. |
118 |
|
|
119 |
Many users prefer to keep their systems clear of unpackaged |
Many users prefer to keep their systems clear of unpackaged |
120 |
software. For this reason, we aim to provide the ability to build |
software. For this reason, we aim to provide the ability to build |
121 |
ASCEND as an RPM package. There is a "SPEC" file includes in the |
ASCEND as an RPM package. There is a "SPEC" file included in the |
122 |
source tree. If you have a source package, such as for example |
source tree. If you have a source package, such as for example |
123 |
ascend-NNNNN.tar.bz2, place it in your home directory, then |
ascend-NNNNN.tar.bz2, place it in your home directory, then |
124 |
type the following |
type the following |
125 |
|
|
126 |
rpmbuild -ta ascend-NNNNN.tar.bz2 |
rpmbuild -ta ascend-NNNNN.tar.bz2 |
127 |
|
|
128 |
This will pull out the 'spec' from from the source package, |
This will pull out the 'spec' from from the source package, |
129 |
which hopefully will be up to date in correspondance with the |
which hopefully will be up to date in correspondance with the |
131 |
|
|
132 |
You will then be able to install ASCEND using something like |
You will then be able to install ASCEND using something like |
133 |
|
|
134 |
rpm -i ~/rpm/ascend-NNNNN-0.jdpipe.i386.rpm |
rpm -i ~/rpm/ascend-NNNNN-0.jdpipe.i386.rpm |
135 |
|
|
136 |
Debian/Unbuntu users should find that they can create a usable |
Debian/Unbuntu users should find that they can create a usable |
137 |
.deb package using the tool 'alien'. We haven't got native |
.deb package using the tool 'alien'. We haven't got native |