Mercurial > vim
view src/msvc-latest.bat @ 33988:7c30841c60a0 v9.0.2180
patch 9.0.2180: POSIX function name in exarg causes issues
Commit: https://github.com/vim/vim/commit/6fdb6280821a822768df5689a5d727e37d38306c
Author: Zoltan Arpadffy <zoltan.arpadffy@gmail.com>
Date: Tue Dec 19 20:53:07 2023 +0100
patch 9.0.2180: POSIX function name in exarg causes issues
Problem: POSIX function name in exarg struct causes issues
on OpenVMS
Solution: Rename getline member in exarg struct to ea_getline,
remove isinf() workaround for VMS
There are compilers that do not treat well POSIX functions - like
getline - usage in the structs.
Older VMS compilers could digest this... but the newer OpenVMS compilers
( like VSI C x86-64 X7.4-843 (GEM 50XB9) ) cannot deal with these
structs. This could be limited to getline() that is defined via
getdelim() and might not affect all POSIX functions in general - but
avoiding POSIX function names usage in the structs is a "safe side"
practice without compromising the functionality or the code readability.
The previous OpenVMS X86 port used a workaround limiting the compiler
capabilities using __CRTL_VER_OVERRIDE=80400000
In order to make the OpenVMS port future proof, this pull request
proposes a possible solution.
closes: #13704
Signed-off-by: Zoltan Arpadffy <zoltan.arpadffy@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 19 Dec 2023 21:00:04 +0100 |
parents | 54dda39c5bb3 |
children |
line wrap: on
line source
@echo off rem To be used on MS-Windows for Visual C++ 2017 or later. rem See INSTALLpc.txt for information. rem rem Usage: rem For x86 builds run this with "x86" option: rem msvc-latest x86 rem For x64 builds run this with "x86_amd64" option or "x64" option: rem msvc-latest x86_amd64 rem msvc-latest x64 rem rem Optional environment variables: rem VSWHERE: rem Full path to vswhere.exe. rem VSVEROPT: rem Option to search specific version of Visual Studio. rem Default: -latest rem To search VS2017: rem set "VSVEROPT=-version [15.0^,16.0^)" rem To search VS2019: rem set "VSVEROPT=-version [16.0^,17.0^)" rem To search VS2022: rem set "VSVEROPT=-version [17.0^,18.0^)" if "%VSWHERE%"=="" ( set "VSWHERE=%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe" set VSWHERE_SET=yes ) if not exist "%VSWHERE%" ( echo Error: vswhere not found. set VSWHERE= set VSWHERE_SET= exit /b 1 ) if "%VSVEROPT%"=="" ( set VSVEROPT=-latest set VSVEROPT_SET=yes ) rem Search Visual Studio Community, Professional or above. for /f "usebackq tokens=*" %%i in (`"%VSWHERE%" %VSVEROPT% -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64 -property installationPath`) do ( set InstallDir=%%i ) if exist "%InstallDir%\VC\Auxiliary\Build\vcvarsall.bat" ( call "%InstallDir%\VC\Auxiliary\Build\vcvarsall.bat" %* goto done ) rem Search Visual Studio 2017 Express. rem (Visual Studio 2017 Express uses different component IDs.) for /f "usebackq tokens=*" %%i in (`"%VSWHERE%" %VSVEROPT% -products Microsoft.VisualStudio.Product.WDExpress -property installationPath`) do ( set InstallDir=%%i ) if exist "%InstallDir%\VC\Auxiliary\Build\vcvarsall.bat" ( call "%InstallDir%\VC\Auxiliary\Build\vcvarsall.bat" %* ) else ( echo Error: vcvarsall.bat not found. rem Set ERRORLEVEL to 1. call ) :done if "%VSWHERE_SET%"=="yes" ( set VSWHERE= set VSWHERE_SET= ) if "%VSVEROPT_SET%"=="yes" ( set VSVEROPT= set VSVEROPT_SET= ) set InstallDir=