This comes from another message thread, but I though this deserves a separate title...

I have two icons on my desktop, and both use the --pcp= parameter with different profile directories.

Lazarus (stable) -> $HOME/.lazarus-stable/
Lazarus (unstable). -> $HOME/.lazarus/

Can I tell Lazarus (Tools > Configure Build Lazarus) what my desired output filename must be, instead of always defaulting to 'lazarus'

Currently I build the stable executable, rename it. Then build the unstable version and rename it. :-(

Can I override the default executable name ('lazarus') to something else?

Regards,
- Graeme -

Why do you rename it?
I guess with 'stable' lazarus a 0.9.28 plus stable packages and the unstable is the 0.9.29 plus unstable packages, right?

Can I override the default executable name ('lazarus') to something else?

No.
It would make startlazarus job hard to find the right executable and give advice when something went wrong.

Mattias

Mattias Gaertner wrote

Why do you rename it? I guess with 'stable' lazarus a 0.9.28 plus stable packages and the unstable is the 0.9.29 plus unstable packages, right?

I use both from inside the same /opt/lazarus/ directory. I do not binary install Lazarus in any other directory. So when I switch branches (I'm using Git repository), the directory doesn't change either. So no separate lazarus directories for different versions of source code (branches) either.

My use-case is probably different to most, because I don't use the LCL, other than to compile the IDE. So between rebuilds I do a 'clean all' before I build stable and unstable executables. The executables can run on there own (very usable) without the need of correctly versioned *.ppu files.

OK. What is the actual point of 'startlazarus'? I never use it. I always launch Lazarus directly from the 'lazarus' executable.

Regards,
- Graeme -

Why not use a symlink?
/opt/lazarus-stable -> /opt/lazarus

Finding the right lazarus executable, starting and restarting lazarus. On windows, the system with the exe lock, it additionally juggle the executables.

Mattias

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 -

True.

This way you save some disk space, but you have to rebuilt everything on every switch. I don't see much gain in changing the output file of lazarus.

[...]

Mattias