maxima makefile etc



>>>>> "Richard" == Richard Fateman <fateman@cs.berkeley.edu> writes:

    Richard> 5.9.0

    Richard> First, spend an afternoon loading cygwin on my machine.
    Richard> spend an afternoon looking at many files which may or
    Richard> may not be correctly set up, with mysterious names and flags
    Richard> in a scripting language which I intensely dislike. Then
    Richard> run configure, make, (which fails)... at least one problem
    Richard> is that the location for windows programs tends to be
    Richard> in a directory with a space in the name, e.g.
    Richard> c:\Program Files\acl62\alisp.exe   for ANSI Allegro CL.

    Richard> so lisp-utils/run  fails.

    Richard> Try to do, by hand, the effect of the run script.

    Richard> Beyond that, names like /usr/local/   seem to be all
    Richard> over the place.  I had to disable $file_search which got
    Richard> into an infinite error loop with windows-filenames.

    Richard> So my impression is that the portability is mostly
    Richard> n lisps, but one style of operating system (and it is not the
    Richard> operating system running on 95% of machines).

    Richard> Am I misunderstanding something here???

I don't think you're missing anything.  I agree that everything is
somewhat Unix-centric now.

However, this is what I often do.

o Ignore all the makefiles, and autoconf, and stuff.
o cd to the src directory
o Load defsystem.lisp if it isn't already
o Load "maxima.system"
o (mk:oos "maxima" :compile)

You should get a working maxima.  Plotting probably won't work though
because it doesn't know how to find the external plotting programs.
But everything else should.

I also haven't tried this in a clean maxima tree, since I always play
with maxima in a Unix system.

Ray