[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Axiom-developer] successfully built axiomUI on Fedora 3 x86-64
From: |
Bill Page |
Subject: |
[Axiom-developer] successfully built axiomUI on Fedora 3 x86-64 |
Date: |
Sun, 04 Sep 2005 01:44:12 -0400 |
Kai,
Thanks for your lastest tla axiom-GUI--1--patch-2. Below I have
included an additional patch to use the $AXIOM variable instead
of hardcoding paths or depending on implicit paths. This is
consistent with the approach used in the current Axiom build.
I am obviously writing this email in a little more detail than you
require :) but I am also cc'ing to axiom-developer list in case
these notes help anyone elso try this.
With your tla patch-2 and this patch I successfully built axiomUI
web-gui on my Fedora Core 3 x86-64 system.
I also upgraded my Firefox browser to DeerPark Alpha 2 from here:
http://www.mozilla.org/projects/firefox
using the link 'Deer Park Alpha 2 for Linux (English)' which
downloads 'deerpark-alpha2.installer.tar.gz'. I untarred and
ran the installer and now I start it with the command:
/usr/local/firefox/firefox&
This is what I noticed so far:
1) All intermediate and binary files are created in the
'src/web-gui' directory. As a minimum, to be (more or less)
compatible with the Axiom build intermediate files should
go into directory 'int/web-gui' and the binaries/executables
should go into 'mnt/bin'
2) run-axiom-ui.sh does not have executable flag. It needs
chmod a+x run-axiom-ui.sh
3) Running
./run-axiom-ui.sh
produces no initial startup message. Something re-assuring
and informative like:
"Waiting for browser http:/127.0.0.1:5050"
would be nice :)
4) 'make doc' does not run because the current Axiom build does
not put noweb.sty into the /usr/share/texmf tree. Instead the
path is hard coded. You could use this convention, in which
case the file should be named '${AXIOM}/bin/tex/noweb.sty'
but perhaps better, the Axiom build should put a copy of
noweb.sty someplace standard like this:
mkdir /usr/share/texmf/tex/latex/noweb
cp $AXIOM/bin/tex/noweb.sty /usr/share/texmf/tex/latex/noweb
/usr/bin/texhash
5) How can I exit cleanly from the run-axiom-ui.sh process?
Perhaps it should catch the ^C and kill signals and do
something nice.
6) On linux at least maybe we should setup an inetd service to
start run-axiom-ui.sh automatically on port 5050 so that this
is transparent to the user? Can you think of any other way
that we can make it unnecessary for the user to start two
processes? Should run-axiom-ui start the browser session for
the user?
7) Of course since this is 'alpha' version there are many easy
to find problems with output. The graphics output seems
especially fragile. The examples you give work fine but if
one deviates slightly it is possible to produce a mess.
E.g.
draw(1/sin(x),x=0..2*%pi)
Perhaps I should set up some AxiomUI categories on IssueTracker to
help keep track of these problems?
Now that SOC is over, what is the best way for us to ensure that
the project development continues? Will you be able to continue to
be involved? If so, would to be willing to continue to take the
lead?
Regards,
Bill Page.
--------
Patch to use $AXIOM variable to locate notangle and noweave.
address@hidden axiom--GUI--1]$ tla changes --diffs
* looking for address@hidden/axiom--GUI--1--patch-2 to
compare with
* comparing to address@hidden/axiom--GUI--1--patch-2
M src/web-gui/Makefile
M src/web-gui/Makefile.pamphlet
* modified files
--- orig/src/web-gui/Makefile
+++ mod/src/web-gui/Makefile
@@ -1,5 +1,5 @@
-TANGLE=/usr/bin/notangle -t8
-WEAVE=/usr/bin/noweave -delay
+TANGLE=${AXIOM}/bin/lib/notangle -t8
+WEAVE=${AXIOM}/bin/lib/noweave -delay
LISP=clisp
--- orig/src/web-gui/Makefile.pamphlet
+++ mod/src/web-gui/Makefile.pamphlet
@@ -10,8 +10,8 @@
\section{Makefile}
<<*>>=
-TANGLE=notangle -t8
-WEAVE=noweave -delay
+TANGLE=${AXIOM}/bin/lib/notangle -t8
+WEAVE=${AXIOM}/bin/lib/noweave -delay
LISP=clisp
@@ -209,4 +209,4 @@
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
@
-\end{document}
\ No newline at end of file
+\end{document}
---------------