>On Tue, 2002-09-10 at 04:49, Mike Clarkson wrote:
>>
>> I checked a set of changes into CVS that should address most of the issues
>> that have been raised over the last few days about xmaxima, including
>
>Great. I think your changes are a huge improvement. I can actually use
>xmaxima on both my machines now.
Glad you like it! Please think of some suggestions for the menus for me.
>> James, could I ask you to change the interfaces/xmaxima/Makefile.am to
>> copy the Tkmaxima/ subdirectory over to xmaxima/Tkmaxima on install -
>> then I can do autoloading.
>
>I just checked in changes to interfaces/xmaxima/Makefile.am such that
>the contents of Tkmaxima are now in
> verpkglibdir/Tkmaxima
>(verpkglibdir = lib directory + package name + version). I think that's
>the right place for them to go. Let me know if you need more help with
>Makefile.am
I think I could use a few more additions in the configure/make:
1) In autoconf-variables.tcl, could you record the lisp.
2) Is there a primordial release date somewhere that could go in
with the version too?
3) Could you change xmaxima-local to invoke wish directly and not shell.
4) Could you make the installed xmaxima (/usr/local/bin/xmaxima)
be a simple Bourne shell script that execs wish on the
{datadir}/xmaxima. Even something like
#!/bin/sh
exec wish {datadir}/xmaxima $*
is fine. This will allow me to do autoloading.
I made an interfaces/bin directory to start gathering the bits and
pieces of code and knowledge that it takes to build a xmaxima
distribution (or any other interface to maxima), that is above and
beyond the configure and make of Maxima itself:
I checked in CY's Inno install script,
I plan to make a Makefile for things like the freewrap setup. By
definition, there will probably never be a Makefile.am in here.
We're making great progress in getting the Windows version packageable,
but some bad news is that xmaxima won't take spaces in filenames
(e.g. C:/Program Files/) anytime soon - it's deep in the browser.