Hi Alejandro, Bill, I think Gaby uploaded a corrected version of OpenAxiom-1.1.0.exe. I didn't include some of the Linux binaries still necessary in Windows (rm, cp, cat ..). Gaby is now aware of this and in the future a more platform independent solution should be implemented.
Like Bill already pointed out: OpenAxiom does not use any external env. variable. You can run OpenAxiom in Windows by just invoking open-axiom in a command prompt. (It is included in the path). The use of --system is just needed if OpenAxiom is not installed in the default "Program Files" directory. Regards, Alfredo On Tue, Mar 4, 2008 at 12:56 PM, Bill Page <[EMAIL PROTECTED]> wrote: > On 3/3/08, Alejandro Jakubi wrote: > > > > I intend to continue the long process of getting acquainted > > with Axiom and for this purpose I find very convenient the use > > of the Texmacs GUI. > > > > Good. I am very interested in your experience with this. > > > Currently, on Windows, I have installed Axiom 0.1.4 (January 17, > > 2005) and WinTexmacs 1.0.4.4. So, I have thought about updating > > Axiom, but binaries are only available for linux. Hence, I have installed > > the Windows port of OpenAxiom 1.1.0 (at this point, for me, I guess > > that the differences are irrelevant). > > > > I think this OpenAxiom binary for Windows was originally prepared by > Alfredo Portes. He might have some more information about how it can > be used. I believe that internally there are some differences in how > the linux-type commands are handled but I am not sure it that will > affect you. So far it seems to work ok for me but I have not tested it > extensively. > > > As you have written a version of tm_axiom.c for Windows, I wonder > > whether you have written also a version of "tm_openaxiom.c" to be > > able to have also an OpenAxiom session within WinTexmacs. Or, at > > least you could tell me what kind of changes have to be made on > > tm_axiom.c for this purpose. > > > > I have not written a new version to tm_axiom.c especially for > OpenAxiom. In principle, although I have not tested this, the same > tm_axiom.c interface should work for both. > > > By analogy, I guess, I should set an "OPENAXIOM" environment variable > similarly > > to AXIOM=C:/axiom/mnt/windows, and replace /bin/AXIOMsys.exe with > > /bin/open-axiom.exe. Is it correct? Is that all? > > > > Unlike the original AXIOM program, I do not think it is necessary to > set any environment variables for OpenAxiom. After installing > OpenAxiom look for the OpenAxiom shortcut on your desktop. Right-click > it and then click 'properties'. The correct way to start OpenAxiom is > shown in the Target: field. In my case that is: > > "C:\My Program Files\OpenAxiom\bin\open-axiom.exe" --system="C:\My > Program Files\OpenAxiom\lib\open-axiom\i686-pc-mingw32\1.1.0" > > The exact path names depends on where you decide to install OpenAxiom. > You see that instead of the AXIOM variable, the locaction of OpenAxiom > is specified in the --system option of the command line. Somehow you > will have to arrange to include this option in the tm_axiom program. > > If you have any trouble with this, please let me know. > > Regards, > Bill Page. > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ open-axiom-devel mailing list open-axiom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
