axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] Re: Axiom on Windows


From: Alfredo Portes
Subject: Re: [Axiom-developer] Re: Axiom on Windows
Date: Tue, 1 Feb 2011 18:53:54 -0500

Hi,

For Axiom:

http://axiom-wiki.newsynthesis.org/AxiomBinaries axiom-windows-0.1.4.exe

There is no native support for Axiom in Windows. Many of the issues
you are reporting are because of this and not because of the other
projects. So this file should probably be removed as it does not
reflect the Axiom project at http://axiom-developer.org. I will remove
it. For Axiom support in Windows you should follow:

http://axiom-developer.org/axiom-website/download.html

For Fricas:

http://axiom-wiki.newsynthesis.org/FriCASBinaries Fricas-Rev.263.exe

was an attempt to make an installer for Fricas, and it required to have an
AXIOM variable. Note that this file was never distributed by the
Fricas project and it
was just something uploaded to the wiki in case people wanted to try it. There
was no intention to harm other projects. The wiki page has now been updated.
Proper support in Windows for Fricas is done by using Cygwin.

http://fricas.sourceforge.net/download.html

For OpenAxiom:

OpenAxiom has the only current installer on Windows that I know of. OpenAxiom
"does not use the AXIOM variable" since the project was started
almost. I will make sure today that this is the case in the installer
and it was not something left  from the old plugin to texmacs. If that
is the case I will fix this ASAP.

Again these installers were not created by any of the projects and in
no way it means you cannot have all 3 projects in your computer.

On Tue, Feb 1, 2011 at 5:11 PM, daly <address@hidden> wrote:
> On Tue, 2011-02-01 at 17:08 -0500, daly wrote:
>> Jeffrey,
>>
>> One of the problems is that Axiom has been forked into FriCAS
>> and Open-Axiom but those versions have not properly specialized
>> the files. This will result in damage to an Axiom installation.
>>
>> I see from your shell variables that Open-Axiom seems to be
>> the last installed version.
>>
>> Tim Daly
>>
>> On Tue, 2011-02-01 at 16:05 -0500, address@hidden
>> wrote:
>> > As list administrator, your authorization is requested for the
>> > following mailing list posting:
>> >
>> >     List:   address@hidden
>> >     From:   address@hidden
>> >     Subject: Axiom on Windows
>> >     Reason:  Post by non-member to a members-only list
>> >
>> > At your convenience, visit:
>> >
>> >     http://lists.nongnu.org/mailman/admindb/axiom-developer
>> >
>> > to approve or deny the request.
>> > email message attachment
>> > > -------- Forwarded Message --------
>> > > From: Kenneth Evans <address@hidden>
>> > > To: address@hidden
>> > > Subject: Axiom on Windows
>> > > Date: Tue, 01 Feb 2011 14:44:51 -0600
>> > >
>> > > Hi
>> > >
>> > > I am new to Axiom and am trying to use it on Windows 7, 64-bit.  (I am
>> > > experienced with Mathematica but have never previously used Axiom.)
>> > > Most of the bits and pieces to make this work appear to be out there,
>> > > but are not very well documented or easy to find.  Clearly, several
>> > > people have taken the time to make installers, etc.  Surely someone is
>> > > actually using it successfully on Windows.
>> > >
>> > > I myself have it working to some extent.  This is what I did:
>> > >
>> > > Downloaded:
>> > >
>> > > http://axiom-wiki.newsynthesis.org/AxiomBinaries
>> > > axiom-windows-0.1.4.exe
>> > >
>> > > http://sourceforge.net/projects/open-axiom/files/
>> > > open-axiom-1.3.0-windows-i386.exe
>> > >
>> > > http://axiom-wiki.newsynthesis.org/FriCASBinaries
>> > > Fricas-Rev.263.exe
>> > >
>> > > I installed them in the order OpenAxiom, FriCAS, Axiom (not having much
>> > > information on which of the three to use).  They all installed and made
>> > > desktop shortcuts.  The ones for OpenAxiom and Axiom, more or less
>> > > worked from the shortcuts with the command-line interface.  The one for
>> > > FriCas failed with a socket error ("can't open socket listing file").
>> > > They all put their paths in PATH, which could possibly be a problem.  I
>> > > uninstalled FriCAS.  The others I installed and reinstalled as I found
>> > > one did some things right and the other other things right.  Currently
>> > > they are both installed with Axiom first in the PATH.
>> > >
>> > > I got the QT windows version of TeXmacs.
>> > >
>> > > http://axiom-wiki.newsynthesis.org/TeXmacs
>> > > texmacs-installer.exe
>> > >
>> > > I got it running.  It is apparently set up for Axiom.  I cloned the
>> > > axiom plug-in and made it work for OpenAxiom using snippets of
>> > > information gleaned via the web.  So I can now run both as sessions in
>> > > TeXmacs.  Axiom works better for me.  I can, in fact, do a lot of what
>> > > Axiom as a CAS is supposed to do.
>> > >
>> > > The main problem with TeXmacs is that when it is covered by another
>> > > window, clicking on the title bar causes it to maximize, rather than
>> > > just coming on top -- very annoying.
>> > >
>> > > The main problem I have right now with the CAS is that I cannot get it
>> > > to read .axiom.input.  I would like to do this to, at a minimum, set my
>> > > working directory to "My Documents/Axiom" where I expect to keep my
>> > > .input files.  This is what happens (with Axiom in the command-line
>> > > interface to keep it simple):
>> > >
>> > > 1. )cd doesn't work
>> > >
>> > > (1) -> )cd
>> > >
>> > >     >> System error:
>> > >     Cannot get the truename of #p"~/".
>> > >
>> > > protected-symbol-warn called with (NIL)
>> > > (1) ->
>> > >
>> > > Using ")system ls", I can see that I am in "My Documents, actually
>> > > c:\Users\evans\Documents.  I would guess Axiom didn't do this as it
>> > > doesn't seem to know it (Axiom) is there.  It is probably some kind of
>> > > windows default.
>> > >
>> > > )cd Axiom doesn't work.  In fact, nothing I have tried works except:
>> > >
>> > > )cd c:/Users/evans/Documents/Axiom
>> > >
>> > > Even after that )cd still doesn't work, but )read
>> > > <filename-without-path> works.
>> > >
>> > > Before doing that )cd Axiom or ./Axiom didn't work.
>> > >
>> > > Is there some way to get around this?  Note that $HOME is defined as
>> > > c:\Users\evans\Documents.  You would think it might try $HOME if ~ fails.
>> > >
>> > > 2. It does not read .axiom.input.  I have tried putting it where it
>> > > should be (c:\Users\evans) in "My Documents" and in other places.  Does
>> > > anyone know how to make it read .axiom.input.
>> > >
>> > > These are some things from the environment that might be applicable:
>> > >
>> > > HOME=c:\Users\evans
>> > > HOMEDRIVE=C:
>> > > HOMEPATH=\Users\evans
>> > > LOCALAPPDATA=C:\Users\evans\AppData\Local
>> > > OPENAXIOM=C:/Program Files
>> > > (x86)/OpenAxiom/lib/open-axiom/i686-pc-mingw32/1.3.0
>> > > USERNAME=evans
>> > > USERPROFILE=C:\Users\evans
>> > >
>> > > Thanks in advance for any help.
>> > >
>> > >   -Ken
>> > >
>> > >
>
>
> _______________________________________________
> Axiom-developer mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/axiom-developer
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]