On 06/26, Ralph Lange via Tech-talk wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
Hi, Ralph!
BTW, it seems that the above hack to avoid the URL rewriting didn't work
because the URL still got rewritten:
epics.anl.gov/tech-talk/2024/msg00801.php
> That's a problem of make, actually.
>
> The topic is covered in the official Windows installation instructions.
[Undid the below URL rewrite, and removed the scheme to prevent another
rewrite.]
> docs.epics-controls.org/en/latest/getting-started/installation-windows.html#windows-path-names
Is the no-space-or-parentheses-in-paths restriction specific to Windows?
If not, I think it should be added to the other platform-specific
installation sections as well (i.e., each "Installation on [platform]"
section).
Thanks,
Lewis
- Replies:
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- References:
- install epics-base: Perl Script Path Interpretation Issue on Windows Hussein Matar via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Johnson, Andrew N. via Tech-talk
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Navigate by Date:
- Prev:
RE: Errors during building of asyn package Yury Malevich - STFC UKRI via Tech-talk
- Next:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
<2024>
2025
- Navigate by Thread:
- Prev:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Next:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Ralph Lange via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
<2024>
2025
|