| /third_party/zlib/contrib/vstudio/ |
| D | readme.txt | 5 Microsoft Visual C++ 9.0/10.0.
17 Build instructions for Visual Studio 2008 (32 bits or 64 bits)
20 - Open contrib\vstudio\vc9\zlibvc.sln with Microsoft Visual C++ 2008
23 Build instructions for Visual Studio 2010 (32 bits or 64 bits)
26 - Open contrib\vstudio\vc10\zlibvc.sln with Microsoft Visual C++ 2010
28 Build instructions for Visual Studio 2012 (32 bits or 64 bits)
31 - Open contrib\vstudio\vc11\zlibvc.sln with Microsoft Visual C++ 2012
33 Build instructions for Visual Studio 2013 (32 bits or 64 bits)
36 - Open contrib\vstudio\vc12\zlibvc.sln with Microsoft Visual C++ 2013
38 Build instructions for Visual Studio 2015 (32 bits or 64 bits)
[all …]
|
| /third_party/mesa3d/src/mesa/main/ |
| D | framebuffer.c | 60 if (fb->Visual.depthBits == 0) { in compute_depth_max()
67 else if (fb->Visual.depthBits < 32) { in compute_depth_max()
68 fb->_DepthMax = (1 << fb->Visual.depthBits) - 1; in compute_depth_max()
121 fb->Visual = *visual; in _mesa_initialize_window_framebuffer()
419 memset(&fb->Visual, 0, sizeof(fb->Visual)); in _mesa_update_framebuffer_visual()
432 fb->Visual.samples = rb->NumSamples; in _mesa_update_framebuffer_visual()
435 fb->Visual.redBits = _mesa_get_format_bits(fmt, GL_RED_BITS); in _mesa_update_framebuffer_visual()
436 fb->Visual.greenBits = _mesa_get_format_bits(fmt, GL_GREEN_BITS); in _mesa_update_framebuffer_visual()
437 fb->Visual.blueBits = _mesa_get_format_bits(fmt, GL_BLUE_BITS); in _mesa_update_framebuffer_visual()
438 fb->Visual.alphaBits = _mesa_get_format_bits(fmt, GL_ALPHA_BITS); in _mesa_update_framebuffer_visual()
[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 | 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/cef/ |
| D | CMakeLists.txt.in | 16 # Windows: Ninja, Visual Studio 2019+
57 # Visual Studio 2019 or newer building on Windows 7 or newer. Windows 10
99 # Using the Visual Studio 2019 IDE:
100 # > cmake -G "Visual Studio 16" -A Win32 ..
101 # Open build\cef.sln in Visual Studio and select Build > Build Solution.
103 # Using Ninja with Visual Studio 2019 command-line tools:
104 # (this path may be different depending on your Visual Studio installation)
105 # > "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvars…
110 # Using the Visual Studio 2019 IDE:
111 # > cmake -G "Visual Studio 16" -A x64 ..
[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
41 #### Using LZ4 DLL with Microsoft Visual C++ project
45 compile a project using Visual C++.
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/node/deps/v8/tools/visual_studio/ |
| D | README.txt | 1 The Microsoft Visual Studio project files for including V8 in a Visual
2 Studio/Visual C++ Express solution has been retired. If a Visual
8 Generating Visual Studio projects using GYP is how the Chromium
|
| /third_party/skia/third_party/externals/sfntly/doc/ |
| D | build_cpp.md | 7 * Windows: Visual C++ 2008, Visual C++ 2010
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"
[all …]
|
| /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
103 installed with `pip3`. You can skip this step if you want to generate Visual
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/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/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
36 builds a DLL for libpng with the default runtime options used by Visual
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/spirv-tools/utils/vscode/ |
| D | README.md | 1 # Visual Studio Code extension for SPIR-V disassembly files
3 This directory holds a Visual Studio Code language server extension for SPIR-V assembly files (`.sp…
15 In order to build and install the Visual Studio Code language server extension, you will need to in…
|
| /third_party/skia/third_party/externals/swiftshader/third_party/SPIRV-Tools/utils/vscode/ |
| D | README.md | 1 # Visual Studio Code extension for SPIR-V disassembly files
3 This directory holds a Visual Studio Code language server extension for SPIR-V assembly files (`.sp…
15 In order to build and install the Visual Studio Code language server extension, you will need to in…
|
| /third_party/skia/third_party/externals/spirv-tools/utils/vscode/ |
| D | README.md | 1 # Visual Studio Code extension for SPIR-V disassembly files
3 This directory holds a Visual Studio Code language server extension for SPIR-V assembly files (`.sp…
15 In order to build and install the Visual Studio Code language server extension, you will need to in…
|
| /third_party/lz4/lib/dll/example/ |
| D | README.md | 8 - `dll\liblz4.dll.a` : The import library of LZ4 library for Visual C++
49 #### The example of usage of static and dynamic LZ4 libraries with Visual C++
52 dynamic LZ4 library from the `dll` directory. The solution works with Visual C++
53 2010 or newer. When one will open the solution with Visual C++ newer than 2010
57 #### Using LZ4 DLL with Visual C++
60 are required to compile a project using Visual C++.
|
| /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/skia/third_party/externals/expat/expat/ |
| D | CMake.README | 3 The cmake based buildsystem for expat works on Windows (cygwin, mingw, Visual
35 Visual Studio Command Prompt or when using mingw, you must open a cmd.exe and
38 for Visual Studio builds do:
39 cmake .. -G "Visual Studio 15 2017" && msbuild /m expat.sln
|
| /third_party/vulkan-loader/ |
| D | BUILD.md | 20 - [Windows Build - Microsoft Visual Studio](#windows-build---microsoft-visual-studio)
22 - [CMake Visual Studio Generators](#cmake-visual-studio-generators)
244 - Microsoft [Visual Studio](https://www.visualstudio.com/)
256 - Some IDEs (e.g., [Visual Studio](https://www.visualstudio.com/),
260 ### Windows Build - Microsoft Visual Studio
262 The general approach is to run CMake to generate the Visual Studio project
264 command line or use the Visual Studio IDE to open the generated solution and
277 The above commands instruct CMake to find and use the default Visual Studio
278 installation to generate a Visual Studio solution and projects for the x64
286 #### Use `CMake` to Create the Visual Studio Project Files
[all …]
|
| /third_party/mbedtls/scripts/ |
| D | windows_msbuild.bat | 1 @rem Build and test Mbed TLS with Visual Studio using msbuild.
3 @rem RETARGET: version of Visual Studio to emulate
9 set "vcvarsall=C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vc…
|
| /third_party/googletest/ci/ |
| D | windows-presubmit.bat | 36 :: CMake Visual Studio 15 2017 Win64
41 -G "Visual Studio 15 2017 Win64" ^
60 :: Bazel Visual Studio 15 2017 Win64
62 SET BAZEL_VC=C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC
|
| /third_party/protobuf/csharp/ |
| D | README.md | 27 You should be able to use Protocol Buffers in Visual Studio 2012 and
34 Open the `src/Google.Protobuf.sln` solution in Visual Studio 2017 or
37 Although *users* of this project are only expected to have Visual
39 have Visual Studio 2017 or later, as the library uses C# 6 features
40 in its implementation, as well as the new Visual Studio 2017 csproj
54 run using the Visual Studio Test Explorer or `dotnet test`.
|
| /third_party/skia/third_party/externals/expat/expat/win32/ |
| D | README.txt | 3 using MS Visual Studio .NET or Cygwin.
8 * MS Visual Studio 2013, 2015 and 2017:
9 Use CMake to generate a solution file for Visual Studio, then use msbuild
14 cmake -G"Visual Studio 15 2017" -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
|
| /third_party/skia/third_party/externals/swiftshader/src/Main/ |
| D | libX11.hpp | 36 Visual *(*XDefaultVisual)(Display *display, int screen_number);
39 …XImage *(*XCreateImage)(Display *display, Visual *visual, unsigned int depth, int format, int offs…
45 …XImage *(*XShmCreateImage)(Display *display, Visual *visual, unsigned int depth, int format, char …
|
| D | libX11.cpp | 30 …XDefaultVisual = (Visual *(*)(Display*, int screen_number))getProcAddress(libX11, "XDefaultVisual"… in LibX11exports()
33 …XCreateImage = (XImage *(*)(Display*, Visual*, unsigned int, int, int, char*, unsigned int, unsign… in LibX11exports()
39 …XShmCreateImage = (XImage *(*)(Display*, Visual*, unsigned int, int, char*, XShmSegmentInfo*, unsi… in LibX11exports()
|