Forum > Windows (32/64)
Does the windows installer provided on SF set a PATH to fpc.exe?
Gustavo 'Gus' Carreno:
Hey PascalDragon
--- Quote from: PascalDragon on May 31, 2022, 08:58:44 am ---
--- Quote from: Gustavo 'Gus' Carreno on May 31, 2022, 08:18:36 am ---Being a Linux only person for quite some time, and not having easy access to a Windows machine, I can't quickly test if it does or not.
--- End quote ---
No savourer of some good wine then? :P
--- End quote ---
DAMN YOU meddling kids!!! I hate it when someone points out that I'm asking something cuz I'm a bit lazy to do it :fist_in_the_air: :P
YES, of course I have wine, and to add more shame to it, I even have the preferred version supplied from the Wine HQ winery.
--- Quote from: PascalDragon on May 31, 2022, 08:58:44 am ---I have not checked, but all in all it would make sense that Lazarus only adds the path to lazbuild to the PATH (if at all), but not the one to its provided fpc cause the point of Lazarus is after all to build Lazarus projects for which you should use lazbuild which uses the Lazarus configuration which in turn has knowledge about the location of the compiler.
--- End quote ---
Well, I've made, somewhat, the same point on the first response I gave: If you're going through the motion of installing the full Monty(Lazarus+FPC), why would you then just use fpc.exe?
To me it makes sense that then you use lazbuild progname.lpi for all your CLI and GUI needs.
I think that if they don't present a really compelling argument, I'll have to redirect them to the setup-lazarus version from Olly which, I THINK, allows one to install only the FPC installer, if one is provided somewhere. Is there?
I know that we have 3 packages for Debian: Lazarus, FPC and FPC source. But I can only find/remember a single installer for the twins.
--- Quote from: PascalDragon on May 31, 2022, 08:58:44 am ---If you install FPC itself on the other hand I think (again, not tested) that it allows you to add the directory of fpc.exe to PATH cause after all you want to be able to use fpc directly in that case...
--- End quote ---
Yeah, I'm also unable to opine on this cuz I don't even know if there's an installer that only installs the FPC side of the twins.
Cheers,
Gus
Gustavo 'Gus' Carreno:
Hey Zvoni,
--- Quote from: Zvoni on May 31, 2022, 09:19:56 am ---OK, i might have phrased it wrong:
I've looked through my System-Variables, looking for "c:\Lazarus\blablablabla"
and nothing like that pops up there
--- End quote ---
Ok, now I'm doubting my own sanity, LOL!!! :o
I now have to check my own code to see if I'm the one amending the system PATH variable to find lazbuild.exe.
Cheers,
Gus
Gustavo 'Gus' Carreno:
Hey Y'all,
Yeap, I can now confirm that I'm borderline senile: It is my TypeScript code that actually adds the path to the GitHub runner.
ARGHHHHH, I hate getting old :P
@PascalDragon: Would it make sense to add an issue to the Lazarus source GitLab repo in order to ask if they can add, AT LEAST, the path to Lazarus from within the installer?
I ask this cuz I've had a look at the Inno Setup script and they do heavily insert new keys on the Windows registry, but no adding of the path, which is rather puzzling, no?
If so, would it then be asking too much if the path to the fpc.exe file could also be added?
Cheers,
Gus
PascalDragon:
--- Quote from: Gustavo 'Gus' Carreno on May 31, 2022, 09:21:28 am ---
--- Quote from: PascalDragon on May 31, 2022, 08:58:44 am ---If you install FPC itself on the other hand I think (again, not tested) that it allows you to add the directory of fpc.exe to PATH cause after all you want to be able to use fpc directly in that case...
--- End quote ---
Yeah, I'm also unable to opine on this cuz I don't even know if there's an installer that only installs the FPC side of the twins.
--- End quote ---
So then you've never stumbled upon FPC's Download page, which - for Windows - will lead you here? ;D
--- Quote from: Gustavo 'Gus' Carreno on May 31, 2022, 09:33:36 am ---@PascalDragon: Would it make sense to add an issue to the Lazarus source GitLab repo in order to ask if they can add, AT LEAST, the path to Lazarus from within the installer?
I ask this cuz I've had a look at the Inno Setup script and they do heavily insert new keys on the Windows registry, but no adding of the path, which is rather puzzling, no?
If so, would it then be asking too much if the path to the fpc.exe file could also be added?
--- End quote ---
You'd have to ask the Lazarus devs about that or simply open an issue and see what response you'll get. Please note however that the Lazarus installer provides the option to create a secondary installation (where the primary config path is configured by parameter setup in the shortcut) to allow the usage of multiple Lazarus versions in parallel. There it might not be useful to add anything to PATH.
Martin_fr:
Currently the lazarus installer (as on sourceforge) does not add any PATH at all.
I don't see much of a reason to add any.
On the other hand,
- if one would add the PATH, it adds to the maintenance of the installer. And probably quite a bit. (and it currently already needs more maintenance than it gets, as there isn't the time needed -> so adding time....? no).
- And it will cause issues for people who want to use more than one install....
But to entertain the idea at least in theory.
- It would have to be a simple build in functionality of inno 5.6 (yes that is old)
- It would have to be optional / not enabled by default
(looking at the most recent installer commit (which will for various reasons get reverted) "not default" is tricky)
- it will need to warn if you do a 2ndary install => but that needs scripting => and therefore adds to maintenance....
But if you want to
- provide a pull-request
- deal with any bugs resulting of it
(if bugs result from it, and no fixing pull request is provided, the answer is to revert the addition)
Then we can talk about it
- based on the most recent commit reverted
- PATH setting off by default / not part of "full install"
(afaik inno takes command line, so it can be enabled by whatever script you have)
- setting for current or all users
- warning when enabled for 2ndary install
- warning if detected a 2ndary install
- warning if making a 2ndary install, and path already has lazbuild / option to remove from path
The warnings depend on testing how it will affect a 2ndary install.
Including
- rebuilding ide
- rebuilding ide via makefile
- building projects
- building projects via "project groups" (one or several at once)
It might be, that if the PATH can be set from the installer, the IDE will then need to have an option to detect that.
- warn the user
- provide an option to override the PATH for any operation run from within the IDE.
Just a collection of "what could possible go wrong".
Hopefully nothing will go wrong in any case at all, and almost no warnings would be needed.
Navigation
[0] Message Index
[#] Next page
[*] Previous page