Mattias Gaertner wrote: > > Why not use a symlink? > /opt/lazarus-stable -> /opt/lazarus
I don't understand... or you don't understand my use-case. :) This is what I do about once a week.... in order $ cd /opt/lazarus $ git checkout upstream // now inside clean "trunk" branch $ git pull // get latest Trunk and Fixes branch $ make clean; make all; // I actually do this from in Lazarus IDE $ mv lazarus lazarus-unstable Now I have Trunk (unstable) executable $ git checkout fixes_0.9.28 $ make clean; make all; $ mv lazarus lazarus-0.9.28 I have two icons on my desktop for each of the 'lazarus-xxx' versions (I don't use startlazarus) and have the correct '--pcp=xxx' parameter setup. See why I want to pass in a option to generate an alternative executable, instead of the default 'lazarus'. If I don't do a rename between compiles, the second compile will override the first ones executable. I can't see how symlinks will help in this case? > Finding the right lazarus executable, starting and restarting lazarus. > On windows, the system with the exe lock, it additionally juggle the > executables. OK, so in the case of Linux, only first task (find right executable) is really used. When starting 'lazarus' directly, I have no problems restarting or rebuilding Lazarus executable from within Linux. So I don't miss much. :) Regards, - Graeme - -- fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal http://opensoft.homeip.net/fpgui/ -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
