-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
That's a problem of make, actually.
The topic is covered in the official Windows installation instructions.
https://urldefense.us/v3/__https://docs.epics-controls.org/en/latest/getting-started/installation-windows.html*windows-path-names__;Iw!!G_uCfscf7eWS!ZdlafAS4_3yKWJ4Ws-SaiP45v3NoDLtAdV1SXZiiPvQ9JRRHUliUpnBOdBmXK7MLUilZ4viwjpIbgIMaZX7W7W-W3IQ$
Cheers,
~Ralph
On 2024-06-26 at 15:25, tech-talk at aps.anl.gov wrote:
>
> Hi Hussein,
>
> Unfortunately the EPICS build rules and our Makefiles don't work when the
path to Base or other modules contain spaces, and it would be quite a lot
of work to fix that (patches welcome if it's important to you!). You can't
just change a configuration setting to get around that.
>
> Thank-you for posting the complete error messages. It looks like you have
Base installed inside a MS Visual Studio BuildTools subdirectory. That is
not a good location, I recommend that you build it somewhere like
C:\epics\base. In addition to Base you will be installing and building
other support modules such as Asyn, so that layout lets you
useC:\epics\asyn for that, and so on.
>
> Hope this helps,
>
> - Andrew
>
> On 6/26/24, 9:26 AM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:
>
> Hello,
>
> I am setting up EPICS Base on my Windows 10 machine, but I get a compile
> error when I run the Makefile in the EPICS Base directory:
>
> perl -CSD C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/bin/windows-x64/makeMakefile.pl
> O.windows-x64 ../../../..
> Can't open perl script "C:/Program": No such file or directory
>
> It seems that my compiler does not interpret the path to the Perl script
> correctly, as it only captures the path up to the first space. As a
> result, the Perl script cannot be found.
>
> Can you tell me why this is happening and how I can fix the problem?
> Which configuration file do I need to edit to correct this?
>
> The complete output of the makefile:
>
> make
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C
> ./configure install
> make[1]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/configure'
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C
> O.windows-x64 -f ../Makefile TOP=../.. \
> T_A=windows-x64 install
> make[2]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/configure/O.windows-x64'
> make[2]: Nothing to be done for 'install'.
> make[2]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/configure/O.windows-x64'
> make[1]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/configure'
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C ./src
> install
> make[1]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src'
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C ./tools
> install
> make[2]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/tools'
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C
> O.windows-x64 -f ../Makefile TOP=../../.. \
> T_A=windows-x64 install
> make[3]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/tools/O.windows-x64'
> make[3]: Nothing to be done for 'install'.
> make[3]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/tools/O.windows-x64'
> make[2]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/tools'
> C:/ProgramData/chocolatey/lib/make/tools/install/bin/make.exe -C
> template/base install
> make[2]: Entering directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/template/base'
> perl -CSD C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/bin/windows-x64/makeMakefile.pl
> O.windows-x64 ../../../..
> Can't open perl script "C:/Program": No such file or directory
> make[2]: *** [../../../configure/RULES_ARCHS:67: O.windows-x64] Error 2
> make[2]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src/template/base'
> make[1]: *** [../configure/RULES_DIRS:85: template/base.install] Error 2
> make[1]: Leaving directory 'C:/Program Files (x86)/Microsoft Visual
> Studio/2022/BuildTools/epics-base/src'
> make: *** [configure/RULES_DIRS:85: src.install] Error 2
>
> Thanks
> Hussein
>
-----BEGIN PGP SIGNATURE-----
Version: FlowCrypt Email Encryption 8.5.7
Comment: Seamlessly send and receive encrypted email
wnUEARYKACcFgmZ8NF8JkBf1I3sS/czbFiEEZXnpIZOwkN8evX8MF/UjexL9
zNsAAELNAP0f7VU04an++F/wbW1nLwudTafc2Ahl+0WDPGXagt/qNAEA/rJs
jNSnORSrZD1brwNHuJWTpUHp9a0O4LIJCZvD1g8=
=b1no
-----END PGP SIGNATURE-----
- Replies:
- Re: install epics-base: Perl Script Path Interpretation Issue on Windows J. Lewis Muir 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
- Navigate by Date:
- Prev:
Re: CSS-Phoebus: Dynamically changing the contents of embedded databrowser Kasemir, Kay via Tech-talk
- Next:
RE: mbbo fields don't match db definitions ??? Mark Rivers 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>
- Navigate by Thread:
- Prev:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows Johnson, Andrew N. via Tech-talk
- Next:
Re: install epics-base: Perl Script Path Interpretation Issue on Windows J. Lewis Muir 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>
|