From: Jaime V. <vi...@fe...> - 2025-08-13 10:22:04
|
Hello Wolfgang, Thanks for the explanation. On 13/08/25 07:41, Wolfgang Dautermann wrote: > I just call ./configure with an installation path (c:\maxima-5.48.1 > for example) and if Maxima is installed elsewhere, there is nothing I > can do. (Some time ago I had that path unchangeable, but there were > complaints). > The same effect would (most likely) occur on Linux/Unix if - let's say > - one configures Maxima for the prefix /opt/maxima-5.48.1 and later > moves that installation somewhere else. Oh, now I see the problem. > > But maybe it can fixed with TCL? I don't know much about TCL, but with > > set script_path [ file dirname [ file normalize [ info script ] ] ] > puts $script_path > > (found on the internet) one seems to get the script path (and output > it). Can Xmaxima changed, so that it uses that, instead of the > "./configure" prefix? Sure, we can fix it so that we make it independent of autoconf. I guess it is safe to assume that if xmaxima is in D:/whatever/bin then maxima will also be in the same directory? Another thing that I can do is to include the variables that are currently created by autoconf into the xmaxima_default file. That way if someone else faces the same problem as Laurent, there will be no need to edit Xmaxima itself but just add a few lines (probably just one line) in xmaxima_default. Regards, Jaime |