Recent

Author Topic: Installation Directory  (Read 5520 times)

Pasqualish

  • Jr. Member
  • **
  • Posts: 68
Installation Directory
« 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 ?

molly

  • Hero Member
  • *****
  • Posts: 2330
Re: Installation Directory
« Reply #1 on: August 11, 2016, 07:06:58 am »
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.

Bart

  • Hero Member
  • *****
  • Posts: 5275
    • Bart en Mariska's Webstek
Re: Installation Directory
« Reply #2 on: August 11, 2016, 09:39:29 am »
It's not the compiler but some of the tools that are used (like make) that cannot handle this very well.

Bart

Thaddy

  • Hero Member
  • *****
  • Posts: 14201
  • Probably until I exterminate Putin.
Re: Installation Directory
« Reply #3 on: August 11, 2016, 10:44:08 am »
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

« Last Edit: August 11, 2016, 10:49:45 am by Thaddy »
Specialize a type, not a var.

Leledumbo

  • Hero Member
  • *****
  • Posts: 8746
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Installation Directory
« Reply #4 on: August 11, 2016, 11:41:50 am »
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.

Thaddy

  • Hero Member
  • *****
  • Posts: 14201
  • Probably until I exterminate Putin.
Re: Installation Directory
« Reply #5 on: August 11, 2016, 12:57:03 pm »
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?
Specialize a type, not a var.

Leledumbo

  • Hero Member
  • *****
  • Posts: 8746
  • Programming + Glam Metal + Tae Kwon Do = Me
Re: Installation Directory
« Reply #6 on: August 11, 2016, 01:16:32 pm »
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 ;)

Thaddy

  • Hero Member
  • *****
  • Posts: 14201
  • Probably until I exterminate Putin.
Re: Installation Directory
« Reply #7 on: August 11, 2016, 10:59:38 pm »
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...
« Last Edit: August 11, 2016, 11:11:58 pm by Thaddy »
Specialize a type, not a var.

 

TinyPortal © 2005-2018