| /third_party/ninja/src/ |
| D | clparser_perftest.cc | 26 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\iostrea… in main() 27 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\istrea… in main() 28 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\ostre… in main() 29 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\ios\… in main() 30 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\xlo… in main() 31 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\cl… in main() 32 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\y… in main() 33 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\… in main() 34 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\\… in main() 35 …"Note: including file: C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\INCLUDE\… in main() [all …]
|
| /third_party/skia/third_party/externals/expat/ |
| D | appveyor.yml | 51 # CMake Visual Studio generators: 52 # https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html#visual-studio-generators 55 # Visual Studio 2017 Win32 56 - GENERATOR: Visual Studio 15 2017 59 APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017 61 # Visual Studio 2017 Win32 XML_UNICODE_WCHAR_T 62 - GENERATOR: Visual Studio 15 2017 66 APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017 68 # Visual Studio 2017 x64 69 - GENERATOR: Visual Studio 15 2017 Win64 [all …]
|
| /third_party/json/ |
| D | appveyor.yml | 5 - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015 10 GENERATOR: Visual Studio 14 2015 12 - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015 17 GENERATOR: Visual Studio 14 2015 19 - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015 25 GENERATOR: Visual Studio 14 2015 27 - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017 32 GENERATOR: Visual Studio 15 2017 34 - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2019 39 GENERATOR: Visual Studio 16 2019 [all …]
|
| /third_party/cJSON/ |
| D | appveyor.yml | 1 os: Visual Studio 2015 15 - GENERATOR: "Visual Studio 14 2015" 20 - GENERATOR: "Visual Studio 14 2015" 25 - GENERATOR: "Visual Studio 12 2013" 30 - GENERATOR: "Visual Studio 12 2013" 35 - GENERATOR: "Visual Studio 11 2012" 40 - GENERATOR: "Visual Studio 11 2012" 45 - GENERATOR: "Visual Studio 10 2010" 50 - GENERATOR: "Visual Studio 10 2010" 55 - GENERATOR: "Visual Studio 9 2008" [all …]
|
| /third_party/curl/projects/ |
| D | build-wolfssl.bat | 44 rem Visual Studio was x86-only prior to 14.3 63 set "VC_PATH=Microsoft Visual Studio 10.0\VC" 68 set "VC_PATH=Microsoft Visual Studio 11.0\VC" 73 set "VC_PATH=Microsoft Visual Studio 12.0\VC" 78 set "VC_PATH=Microsoft Visual Studio 14.0\VC" 86 if exist "%PF%\Microsoft Visual Studio\2017\Enterprise\VC" ( 87 set "VC_PATH=Microsoft Visual Studio\2017\Enterprise\VC" 88 ) else if exist "%PF%\Microsoft Visual Studio\2017\Professional\VC" ( 89 set "VC_PATH=Microsoft Visual Studio\2017\Professional\VC" 91 set "VC_PATH=Microsoft Visual Studio\2017\Community\VC" [all …]
|
| D | README.md | 11 from sources using an IDE based development tool such as Visual Studio. 64 different versions of Visual Studio, build helper batch files have been 71 part of Visual Studio. 75 version of Visual C++ that you will be using. Each version of Visual Studio 78 - VC10 (Visual Studio 2010 Version 10.0) 79 - VC11 (Visual Studio 2012 Version 11.0) 80 - VC12 (Visual Studio 2013 Version 12.0) 81 - VC14 (Visual Studio 2015 Version 14.0) 82 - VC14.10 (Visual Studio 2017 Version 15.0) 83 - VC14.30 (Visual Studio 2022 Version 17.0) [all …]
|
| D | build-openssl.bat | 49 rem Visual Studio was x86-only prior to 14.3 63 set "VC_PATH=Microsoft Visual Studio 10.0\VC" 67 set "VC_PATH=Microsoft Visual Studio 11.0\VC" 71 set "VC_PATH=Microsoft Visual Studio 12.0\VC" 75 set "VC_PATH=Microsoft Visual Studio 14.0\VC" 82 if exist "%PF%\Microsoft Visual Studio\2017\Enterprise\VC" ( 83 set "VC_PATH=Microsoft Visual Studio\2017\Enterprise\VC" 84 ) else if exist "%PF%\Microsoft Visual Studio\2017\Professional\VC" ( 85 set "VC_PATH=Microsoft Visual Studio\2017\Professional\VC" 87 set "VC_PATH=Microsoft Visual Studio\2017\Community\VC" [all …]
|
| /third_party/node/tools/gyp/pylib/gyp/ |
| D | MSVSVersion.py | 20 """Information regarding a version of Visual Studio.""" 75 """Returns the path to Visual Studio installation.""" 274 "Visual Studio 2022", 286 "Visual Studio 2019", 298 "Visual Studio 2017", 310 "Visual Studio 2015", 321 "Visual Studio 2013", 332 "Visual Studio 2013", 343 "Visual Studio 2012", 354 "Visual Studio 2012", [all …]
|
| /third_party/node/deps/npm/node_modules/node-gyp/gyp/pylib/gyp/ |
| D | MSVSVersion.py | 20 """Information regarding a version of Visual Studio.""" 75 """Returns the path to Visual Studio installation.""" 274 "Visual Studio 2022", 286 "Visual Studio 2019", 298 "Visual Studio 2017", 310 "Visual Studio 2015", 321 "Visual Studio 2013", 332 "Visual Studio 2013", 343 "Visual Studio 2012", 354 "Visual Studio 2012", [all …]
|
| /third_party/skia/third_party/externals/spirv-cross/ |
| D | appveyor.yml | 6 - GENERATOR: "Visual Studio 12 2013 Win64" 9 - GENERATOR: "Visual Studio 12 2013 Win64" 12 - GENERATOR: "Visual Studio 14 2015 Win64" 15 - GENERATOR: "Visual Studio 14 2015 Win64" 18 - GENERATOR: "Visual Studio 12 2013" 21 - GENERATOR: "Visual Studio 12 2013" 24 - GENERATOR: "Visual Studio 14 2015" 27 - GENERATOR: "Visual Studio 14 2015"
|
| /third_party/glib/ |
| D | README.win32.md | 18 Visual Studio toolchain. For the latter, Visual Studio 2015 and later are 19 recommended. For older Visual Studio versions, see below. 55 when building with Visual Studio. When using the MinGW-GCC toolchain, the CRT 104 Studio project files. 114 ## Building with Visual Studio 2015 or newer 116 Meson is now the only supported method of building GLib using Visual Studio. 120 - Open a Visual Studio (or SDK) command prompt that matches the Visual Studio 138 path. The `--backend=vs` option can be used if the Visual Studio project 144 use `msbuild` or you can open the generated solution in Visual Studio. 146 ## Building with old versions of Visual Studio [all …]
|
| /third_party/protobuf/ |
| D | appveyor.yml | 6 # Only test few combinations: "Visual Studio 2015 (14) + Win64/MinGW + Debug + DLL". We can 11 image: Visual Studio 2015 15 image: Visual Studio 2015 21 image: Visual Studio 2017 27 image: Visual Studio 2017 38 - if %platform%==Win32 set generator=Visual Studio 14 39 - if %platform%==Win64 set generator=Visual Studio 14 Win64
|
| /third_party/skia/third_party/externals/sfntly/doc/ |
| D | build_cpp.md | 53 4. Run the following commands to create the Visual Studio solution files: 68 …Since sfntly use STL extensively, please patch your Visual Studio for any STL-related hotfixes/ser… 74 Visual Studio 2008 and 2010 support command line building, 77 For Visual Studio 2008 (assume its installed at `c:\vs08`) 80 ..\ext\cmake\bin\cmake .. -G "Visual Studio 9 2008" 85 Visual Studio 2008 solution/project files are generated. 90 Please refer to your Visual Studio manual for more details. 92 For Visual Studio 2010 (assume its installed at `c:\vs10`) 96 ..\ext\cmake\bin\cmake .. -G "Visual Studio 10" 100 If you install both Visual Studio 2008 and 2010 on your system, [all …]
|
| /third_party/lz4/build/ |
| D | README.md | 8 - `VS2010` - Visual Studio 2010 project (which also works well with Visual Studio 2012, 2013, 2015) 9 - `VS2017` - Visual Studio 2017 project 12 #### How to compile lz4 with Visual Studio 14 1. Install Visual Studio e.g. VS 2015 Community Edition (it's free). 18 5. Visual Studio will ask about converting VS2010 project to VS2015 and you should agree. 26 The Visual Studio solution file `lz4.sln` contains many projects that will be compiled to the 48 …be found in Project Properties of Visual Studio IDE in the `C/C++` Property Pages on the `General`…
|
| /third_party/protobuf/kokoro/release/python/windows/ |
| D | build_single_artifact.bat | 3 if %PYTHON%==C:\python35_32bit set generator=Visual Studio 14 6 if %PYTHON%==C:\python35 set generator=Visual Studio 14 Win64 9 if %PYTHON%==C:\python36_32bit set generator=Visual Studio 14 12 if %PYTHON%==C:\python36 set generator=Visual Studio 14 Win64 15 if %PYTHON%==C:\python37_32bit set generator=Visual Studio 14 18 if %PYTHON%==C:\python37 set generator=Visual Studio 14 Win64 21 if %PYTHON%==C:\python38_32bit set generator=Visual Studio 14 24 if %PYTHON%==C:\python38 set generator=Visual Studio 14 Win64
|
| /third_party/benchmark/ |
| D | appveyor.yml | 3 image: Visual Studio 2017 12 generator: "Visual Studio 15 2017" 15 generator: "Visual Studio 15 2017 Win64" 18 generator: "Visual Studio 14 2015" 21 generator: "Visual Studio 14 2015 Win64" 26 APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015
|
| /third_party/protobuf/cmake/ |
| D | README.md | 3 and using an *Visual Studio* IDE. 5 You need to have [CMake](http://www.cmake.org), [Visual Studio](https://www.visualstudio.com) 18 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional> 22 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional>cd C:\Path\to 88 [Visual Studio](http://www.cmake.org/cmake/help/latest/manual/cmake-generators.7.html#visual-studio… 121 To create *Visual Studio* solution file: 124 C:\Path\to\protobuf\cmake\build\solution>cmake -G "Visual Studio 16 2019" ^ 128 It will generate *Visual Studio* solution file *protobuf.sln* in current directory. 133 To make a *Visual Studio* file for Visual Studio 16 2019, create the *Visual Studio* 138 Then create the *Visual Studio* solution file again [all …]
|
| /third_party/node/deps/npm/node_modules/node-gyp/lib/ |
| D | find-visualstudio.js | 37 `- looking for Visual Studio version ${this.configVersionYear}`) 41 `- looking for Visual Studio installed in "${this.configPath}"`) 105 'You need to install the latest version of Visual Studio', 113 throw new Error('Could not find any Visual Studio installation to use') 116 // Invoke the PowerShell script to get information about Visual Studio 2017 136 // of Visual Studio 2017 or newer to use 142 …'could not use PowerShell to find Visual Studio 2017 or newer, try re-running with \'--loglevel si… 195 this.addLog('- found "Visual Studio C++ core features"') 197 this.addLog('- "Visual Studio C++ core features" missing') 223 'could not find a version of Visual Studio 2017 or newer to use') [all …]
|
| /third_party/gn/src/gn/ |
| D | visual_studio_writer.h | 29 Vs2013 = 1, // Visual Studio 2013 30 Vs2015, // Visual Studio 2015 31 Vs2017, // Visual Studio 2017 32 Vs2019, // Visual Studio 2019 33 Vs2022, // Visual Studio 2022 36 // Writes Visual Studio project and solution files. |sln_name| is the optional 42 // which will be used by Visual Studio IntelliSense. 144 // Visual Studio version string.
|
| D | visual_studio_writer.cc | 73 const char kToolsetVersionVs2013[] = "v120"; // Visual Studio 2013 74 const char kToolsetVersionVs2015[] = "v140"; // Visual Studio 2015 75 const char kToolsetVersionVs2017[] = "v141"; // Visual Studio 2017 76 const char kToolsetVersionVs2019[] = "v142"; // Visual Studio 2019 77 const char kToolsetVersionVs2022[] = "v143"; // Visual Studio 2022 78 const char kProjectVersionVs2013[] = "12.0"; // Visual Studio 2013 79 const char kProjectVersionVs2015[] = "14.0"; // Visual Studio 2015 80 const char kProjectVersionVs2017[] = "15.0"; // Visual Studio 2017 81 const char kProjectVersionVs2019[] = "16.0"; // Visual Studio 2019 82 const char kProjectVersionVs2022[] = "17.0"; // Visual Studio 2022 [all …]
|
| /third_party/skia/third_party/externals/libpng/projects/vstudio/ |
| D | README.txt | 1 Instructions for building libpng using Microsoft Visual Studio 12 Visual Studio 2010. It may also work under later versions of Visual 13 Studio. You should be familiar with Visual Studio before using this 37 Studio. In particular the runtime library is the "MultiThreaded DLL" 38 version. If you use Visual Studio defaults to build your application, 41 If you don't use the Visual Studio defaults your application must still
|
| /third_party/libsnd/Win32/ |
| D | README-precompiled-dll.txt | 4 In order to use this pre-compiled DLL with Visual Studio, you will need to 24 environment variable. Another alternative is to use the "Visual Studio 2005 29 Visual Studio 2005 -> 30 Visual Studio Tools -> 31 Visual Studio 2005 Command Prompt
|
| /third_party/curl/winbuild/ |
| D | README.md | 12 (part of Visual Studio 6). However using a more recent version is strongly 16 full Visual Studio or Visual C++ if all you want is to build curl. 47 Open a Visual Studio Command prompt: 50 [version} is the Visual Studio version. The developer prompt at default uses 53 Visual Studio versions. 56 Studio](https://docs.microsoft.com/en-us/dotnet/framework/tools/developer-command-prompt-for-vs) 61 where [version] is the Visual Studio version, [platform] is e.g. x64 and 63 exist in all Visual Studio versions. 131 ## Building your own application with libcurl (Visual Studio example) 139 Studio 2010 x64 Win64 Command Prompt: [all …]
|
| /third_party/vulkan-loader/ |
| D | BUILD.md | 28 - [Windows Build - Microsoft Visual Studio](#windows-build---microsoft-visual-studio) 30 …- [Use `CMake` to Create the Visual Studio Project Files](#use-cmake-to-create-the-visual-studio-p… 32 - [Build the Solution With Visual Studio](#build-the-solution-with-visual-studio) 268 - Microsoft [Visual Studio](https://www.visualstudio.com/) 279 - Some IDEs (e.g., [Visual Studio](https://www.visualstudio.com/), 283 ### Windows Build - Microsoft Visual Studio 285 The general approach is to run CMake to generate the Visual Studio project 287 command line or use the Visual Studio IDE to open the generated solution and 300 The above commands instruct CMake to find and use the default Visual Studio 301 installation to generate a Visual Studio solution and projects for the x64 [all …]
|
| /third_party/zlib/contrib/vstudio/ |
| D | readme.txt | 17 Build instructions for Visual Studio 2008 (32 bits or 64 bits) 23 Build instructions for Visual Studio 2010 (32 bits or 64 bits) 28 Build instructions for Visual Studio 2012 (32 bits or 64 bits) 33 Build instructions for Visual Studio 2013 (32 bits or 64 bits) 38 Build instructions for Visual Studio 2015 (32 bits or 64 bits) 43 Build instructions for Visual Studio 2022 (64 bits) 80 Visual Studio 2013, 2015, and 2022 Projects from Sean Hunt
|