Experimental Physics and
Industrial Control System

Ralph Lange via Core-talk <core-talk at aps.anl.gov> · Fri, 24 Apr 2020 07:58:21 -0000

I would say, in cases where the user runs the compiler setup (vsvarsall or equivalent script) first, EpicsHostArch could look at a few environment variables and figure out the intended setting in most cases.
It would not detect all possible cases on all possible platforms, certainly, but should the inability to reach perfection keep us from improving it?

Since you do run your compiler setup batch beforehand, I am sure
EpicsHostArch could perfectly tell which of those targets you want to
build in your Strawberry field.

Older free VisualStudio versions (2008, 2010, 2012) that don't offer the
64bit compiler are the main 32bit reasons I can think of. Not sure about
legacy/embedded systems - are those running Windows?

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1873406

Title:
  EpicsHostArch script does not detect recent MSYS2/MinGW setups on
  Windows

Status in EPICS Base:
  New
Status in EPICS Base 3.15 series:
  New
Status in EPICS Base 7.0 series:
  New

Bug description:
  On MSYS2/MinGW installations, the EpicsHostArch script does not
  recognize the host platform correctly.

  64bit:
  $ ./startup/EpicsHostArch
  lib/perl/EpicsHostArch.pl: Architecture 'x86_64-msys-thread-multi' not recognized

  32bit:
  $ ./startup/EpicsHostArch
  lib/perl/EpicsHostArch.pl: Architecture 'x86_64-msys-thread-multi' not recognized

  Which is not surprising, as the underlying MSYS2 subsystem is the
  same, and the difference is in the environment settings that point to
  the appropriate toolchain.

  64bit:
  $ echo $PATH
  /mingw64/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
  $ printenv | grep MSYSTEM
  MSYSTEM_CARCH=x86_64
  MSYSTEM_CHOST=x86_64-w64-mingw32
  MSYSTEM_PREFIX=/mingw64
  MSYSTEM=MINGW64

  32bit:
  $ echo $PATH
  /mingw32/bin:/usr/local/bin:/usr/bin:/bin:/c/Windows/System32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
  $ printenv | grep MSYSTEM
  MSYSTEM_CARCH=i686
  MSYSTEM_CHOST=i686-w64-mingw32
  MSYSTEM_PREFIX=/mingw32
  MSYSTEM=MINGW32

  NB: I am impressed by the clarity and simplicity of MSYS2 / MinGW

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1873406/+subscriptions

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System