Lazarus
Installation => Windows (32/64) => Topic started by: Pasqualish on August 11, 2016, 07:01:27 am
-
Lazarus gives a default installation directory of c:\Lazarus. Is there an advantage to installing here versus the normal c:\Program Files\Lazarus ?
-
Some compilers do not like spaces in their filename/path, binutils are not fond of them either and some editors/IDE's might trip over them.
-
It's not the compiler but some of the tools that are used (like make) that cannot handle this very well.
Bart
-
It's not the compiler but some of the tools that are used (like make) that cannot handle this very well.
Bart
That's silly. The windows installer can use the ShortPathName API to obtain spaceless paths and pass these to the tools like make.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364989%28v=vs.85%29.aspx
-
That's silly. The windows installer can use the ShortPathName API to obtain spaceless paths and pass these to the tools like make.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364989%28v=vs.85%29.aspx
That's silly. make isn't coded using Windows API.
-
That's silly. The windows installer can use the ShortPathName API to obtain spaceless paths and pass these to the tools like make.
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364989%28v=vs.85%29.aspx
That's silly. make isn't coded using Windows API.
Nope, but you can pass it a for "make.exe" valid path by using GetShortpathname first, silly ;)
If it is too much trouble to pipe the paths through a little extra utility?
-
Nope, but you can pass it a for "make.exe" valid path by using GetShortpathname first, silly ;)
If it is too much trouble to pipe the paths through a little extra utility?
Help the whole toolchain to implement that then ;)
-
Nope, but you can pass it a for "make.exe" valid path by using GetShortpathname first, silly ;)
If it is too much trouble to pipe the paths through a little extra utility?
Help the whole toolchain to implement that then ;)
Oh, well, I will. It's a 10 liner or something. (w/o too much housekeeping)
This is a Windows issue and I never understood why either symlink, hardlink, junction, SUBST to an alternative path without spaces /or GetShortPathName was ever used for the windows install. There is not really an excuse, but time. I might add that FPC has already the option to specify where to look for the binutils (-FD) so -FD<ShortPathName> solves the issue as well. Or setting the environment variable BINUTILSDIR probably...
These are all feasable options. Just tell me what is your favorite...