/[ascend]/trunk/INSTALL.txt
ViewVC logotype

Annotation of /trunk/INSTALL.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 476 - (hide annotations) (download)
Mon Apr 17 07:06:45 2006 UTC (13 years, 2 months ago) by johnpye
Original Path: trunk/INSTALL
File size: 3711 byte(s)
Added some INSTALL notes relating to building windows installer.
Added some optimisations to the SWIG build to reduce target file size.
Fixed bug with WITH_INSTALLER=1 flag.
1 johnpye 438 BUILDING AND INSTALLING ASCEND
2 aw0a 1
3 johnpye 438 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 johnpye 146
9 johnpye 438 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 johnpye 476 with the version you are currently looking at.
12 johnpye 438 https://pse.cheme.cmu.edu/svn-view/ascend/code/trunk/INSTALL?view=log
13 johnpye 146
14 johnpye 438 -----
15     BUILDING ON LINUX AND WINDOWS
16 johnpye 146
17 johnpye 438 To build ASCEND we now recommend using SCons. This is supported
18 ben.allan 474 both on Windows (using the MinGW toolset) and Linux. Their fans
19     will also find build tools for jam and autotools. The autotools
20     build is still maintained for at least the tcl/tk interface version.
21 aw0a 1
22 johnpye 438 ASCEND provides two possible interfaces. The older, more mature
23     GUI is based on Tcl/Tk. A newer interface that is more in keeping
24     with modern GUI design is implemented using PyGTK, but it is still
25     missing some functionality.
26 aw0a 1
27 johnpye 438 Using SCons 0.96.91 or newer, see your build options by typing
28 aw0a 1
29 johnpye 438 scons -Qh
30 aw0a 1
31 johnpye 438 You can add your build options to a file in this directory
32     which you can create, called 'config.py'.
33 aw0a 1
34 johnpye 438 Then to build ASCEND, type
35 aw0a 1
36 johnpye 438 scons
37 aw0a 1
38 johnpye 438 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
40     SCons). The Tcl/Tk interface requires that you have Tcl/Tk and
41     TkTable installed on your system.
42 aw0a 1
43 johnpye 438 For updates on this information, please check
44     https://pse.cheme.cmu.edu/wiki/view/Ascend/BuildingAscend
45 aw0a 1
46 johnpye 438 For specific information on building the Python interface and
47     setting up the PyGTK GUI, please see
48     https://pse.cheme.cmu.edu/wiki/view/Ascend/PythonWrapper
49 aw0a 1
50 johnpye 438 ------
51     INSTALLING ON LINUX
52 aw0a 1
53 johnpye 438 To then install ASCEND, you will need to have write access to the
54     directories INSTALL_DATA, INSTALL_BIN as specified in your
55     SCons configuration. You can then type
56 aw0a 1
57 johnpye 438 scons install
58 aw0a 1
59 johnpye 438 ------
60     INSTALLING ON WINDOWS
61 aw0a 1
62 johnpye 476 To build a Windows installer (a 'setup.exe') for the PyGTK GUI,
63     you will need to have the NSIS installer-creator installed on
64     your system (which is free, at http://nsis.sf.net/). Then you
65     should simply need to type
66 aw0a 1
67 johnpye 476 scons WITH_INSTALLER=1
68    
69     This will leave an installer package named 'ascend-setup.exe'
70     in the pygtk/interface directory.
71    
72 johnpye 438 ------
73     CREATING AN RPM/DEB PACKAGE
74 aw0a 1
75 johnpye 438 Many users prefer to keep their systems clear of unpackaged
76     software. For this reason, we aim to provide the ability to build
77 johnpye 476 ASCEND as an RPM package. There is a "SPEC" file includes in the
78     source tree. If you have a source package, such as for example
79     ascend-NNNNN.tar.bz2, place it in your home directory, then
80     type the following
81 aw0a 1
82 johnpye 438 rpmbuild -ta ascend-NNNNN.tar.bz2
83 aw0a 1
84 johnpye 438 This will pull out the 'spec' from from the source package,
85     which hopefully will be up to date in correspondance with the
86     package version number NNNNN.
87 aw0a 1
88 johnpye 438 You will then be able to install ASCEND using something like
89 aw0a 1
90 johnpye 438 rpm -i ~/rpm/ascend-NNNNN-0.jdpipe.i386.rpm
91 aw0a 1
92 johnpye 438 Debian/Unbuntu users should find that they can create a usable
93     .deb package using the tool 'alien'. We haven't got native
94     support for the generation of .deb packages at this stage.
95 aw0a 1
96 johnpye 476 NOTE: occasionally the 'ascend.spec' file may need to be updated
97     if changes have been made to the 'ascend.spec.in' file. Check
98     the implementation details in the SConstruct file.
99    
100 johnpye 438 ------
101     GETTING SUPPORT AND FURTHER INFORMATION
102 aw0a 1
103 johnpye 438 For support with ASCEND, details of mailing lists and other
104     useful information, please visit
105 aw0a 1
106 johnpye 438 ASCEND user's website:
107     http://ascend.cheme.cmu.edu/
108 aw0a 1
109 johnpye 438 ASCEND developer's wiki:
110     https://pse.cheme.cmu.edu/wiki/view/Ascend/WebHome

john.pye@anu.edu.au
ViewVC Help
Powered by ViewVC 1.1.22