Repository navigation
LazAssPicker now works out each build's IDE configuration folder the way Lazarus itself does, and tells you when two builds would share one.
- Each build shows the configuration folder it starts with:
--pcp=in its launch arguments, otherwise thelazarus.cfgbeside the Lazarus executable, otherwise the default (~/.lazarus, or%LOCALAPPDATA%\lazaruson Windows).~/and relative folders are read as Lazarus reads them. - A Windows secondary install, whose Start menu shortcut relies on
lazarus.cfg, is listed once instead of twice. - A shortcut with a relative
--primary-config-path=no longer stops Apply associations with "configuration directory is missing". - When two checked builds would start with the same configuration folder, LazAssPicker says so beside the build and when you apply. Lazarus versions cannot share one.
--pcp <folder>written with a space is refused: Lazarus only reads--pcp=<folder>and would open the folder as a file.- Quotes around the folder in
lazarus.cfgare pointed out: Lazarus 5 removes them, but 4 and older read them as part of the folder's name.
Downloads:
- Windows x86-64 -
lazasspicker-0.3.0-windows-x86_64.zip. Unzip it, putlazasspicker.exebeside fpcupdeluxe (or anywhere you like) and run it. Tested on Windows 10. - Linux x86-64 (GTK3) -
lazasspicker-0.3.0-linux-x86_64.tar.gz. Unpack it, putlazasspickerbeside fpcupdeluxe and run it.
Each download has its SHA-256 checksum beside it. There is no macOS build.