mozilla
/
msvc-dev-cmd
зеркало из https://github.com/mozilla/msvc-dev-cmd.git
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
GitHub Action to setup Developer Command Prompt for Microsoft Visual C++
34 коммитов 5 Ветки 11 Теги 153 KiB
JavaScript 98.3%
C 1.7%
Перейти к файлу
Alexei Lozovsky dd5e2fa0a7
Autodetect variables to export (#32) 
Instead of using a hardcoded list of variables to export, use a more
smart approach: first inspect the original environment, then look what
variables have changed as a result of "vcvarsall.bat" invocation, and
export all those new values.

Also, log the variables we export to be more debugging-friendly.
 		2021-03-20 10:49:55 +02:00
.github/workflows Architecture aliases: Win32 & Win64 (#29) 2021-03-07 08:23:48 +02:00
node_modules/@actions/core Add node_modules on master with up-to-date deps 2020-12-11 20:05:07 +09:00
.eslintrc.json Initial action stub 2019-10-01 22:15:47 +03:00
.gitignore Initial action stub 2019-10-01 22:15:47 +03:00
LICENSE Initial action stub 2019-10-01 22:15:47 +03:00
README.md Describe conflicts with "shell: bash" (#31) 2021-03-19 14:26:39 +02:00
action.yml Initial action stub 2019-10-01 22:15:47 +03:00
hello.c Verify configured environment 2019-10-02 00:53:54 +03:00
index.js Autodetect variables to export (#32) 2021-03-20 10:49:55 +02:00
package-lock.json Bump @actions/core from 1.2.2 to 1.2.6 (#13) 2020-10-01 22:32:34 +03:00
package.json Prepare for next release 2020-03-19 09:03:19 +02:00

README.md

GitHub Actions status

msvc-dev-cmd

GitHub Action for configuring Developer Command Prompt for Microsoft Visual C++.

This sets up the environment for compiling C/C++ code from command line.

Supports Windows. Does nothing on Linux and macOS.

Inputs

  • arch – target architecture
    • native compilation:
      • x64 (default) or its synonyms: amd64, win64
      • x86 or its synonyms: win32
    • cross-compilation: x86_amd64, x86_arm, x86_arm64, amd64_x86, amd64_arm, amd64_arm64
  • sdk – Windows SDK to use
    • do not specify to use the default SDK
    • or specify full Windows 10 SDK number (e.g, 10.0.10240.0)
    • or write 8.1 to use Windows 8.1 SDK
  • toolset – select VC++ compiler toolset version
    • do not specify to use the default toolset
    • 14.0 for VC++ 2015 Compiler Toolset
    • 14.XX for the latest 14.XX toolset installed (e.g, 14.11)
    • 14.XX.YYYYY for a specific full version number (e.g, 14.11.25503)
  • uwp – set true to build for Universal Windows Platform (i.e., for Windows Store)
  • spectre – set true to use Visual Studio libraries with Spectre mitigations

Example usage

jobs:
  test:
    - uses: actions/checkout@v1
    - uses: ilammy/msvc-dev-cmd@v1
    - name: Build something requiring CL.EXE
      run: |
        cmake -G "NMake Makefiles" .
        nmake        
    # ...

Caveats

Name conflicts with shell: bash

Using shell: bash in Actions may shadow some of the paths added by MSVC. In particular, link.exe (Microsoft C linker) is prone to be shadowed by /usr/bin/link (GNU filesystem link tool).

Unfortunately, this happens because GitHub Actions unconditionally prepend GNU paths when shell: bash is used, on top of any paths set by msvc-dev-cmd, every time at the start of each new step. Hence, there aren't many non-destructive options here.

If you experience compilation errors where link complains about unreasonable command-line arguments, “extra operand something-something” – that's probably it. Recommended workaround is to remove /usr/bin/link if that interferes with your builds. If this is not acceptable, please file an issue, then we'll figure out something better.

License

MIT, see LICENSE.