• Home
  • Raw
  • Download

Lines Matching +full:debian +full:- +full:vulkan

14 for a particular development environment.  If you are on a Unix-like system such
40 @subsubsection compile_deps_mingw Dependencies for MinGW or MinGW-w64 on Windows
42 Both the MinGW and the MinGW-w64 packages already contain all the necessary
47 @subsubsection compile_deps_mingw_cross Dependencies for MinGW or MinGW-w64 cross-compilation
49 Both Cygwin and many Linux distributions have MinGW or MinGW-w64 packages. For
50 example, Cygwin has the `mingw64-i686-gcc` and `mingw64-x86_64-gcc` packages
51 for 32- and 64-bit version of MinGW-w64, while Debian GNU/Linux and derivatives
52 like Ubuntu have the `mingw-w64` package for both.
55 cross-compilation of Windows binaries. To use these files you need to add a
59 cmake -DCMAKE_TOOLCHAIN_FILE=<toolchain-file> .
63 MinGW-w64 binaries on your system. You can usually see this in the /usr
64 directory. For example, both the Debian/Ubuntu and Cygwin MinGW-w64 packages
65 have `/usr/x86_64-w64-mingw32` for the 64-bit compilers, so the correct
69 cmake -DCMAKE_TOOLCHAIN_FILE=CMake/x86_64-w64-mingw32.cmake .
92 distributions based on Debian GNU/Linux, you need to install the `xorg-dev`
105 compiled binaries. If these are the same, it is called an in-tree build,
106 otherwise it is called an out-of-tree build.
108 One of several advantages of out-of-tree builds is that you can generate files
115 @subsubsection compile_generate_cli Generating files with the CMake command-line tool
117 To make an in-tree build, enter the _root_ directory of the GLFW source tree
123 cd <glfw-root-dir>
127 To make an out-of-tree build, make a directory outside of the source tree, enter
132 mkdir glfw-build
133 cd glfw-build
134 cmake <glfw-root-dir>
169 from there. If you are using the command-line version of CMake you can use the
171 distributions based on Debian GNU/Linux have this tool in a separate
172 `cmake-curses-gui` package.
175 command-line with the `-D` flag.
178 cmake -DBUILD_SHARED_LIBS=ON .
200 `GLFW_VULKAN_STATIC` determines whether to use the Vulkan loader linked
224 high-performance GPU on Nvidia Optimus and AMD PowerXpress systems. These symbols
234 being compiled for and also has optional, platform-specific ones for various
241 macros to be defined on the command-line.
246 - `_GLFW_COCOA` to use the Cocoa frameworks
247 - `_GLFW_WIN32` to use the Win32 API
248 - `_GLFW_X11` to use the X Window System
249 - `_GLFW_WAYLAND` to use the Wayland API (experimental and incomplete)
250 - `_GLFW_MIR` to use the Mir API (experimental and incomplete)
255 If you are linking the Vulkan loader statically into your application then you
261 - `_GLFW_USE_EGLPLATFORM_H` to use `EGL/eglplatform.h` for native handle
267 - `_GLFW_HAS_XF86VM` to use Xxf86vm as a fallback when RandR gamma is broken
273 - `_GLFW_USE_CHDIR` to `chdir` to the `Resources` subdirectory of the
275 - `_GLFW_USE_MENUBAR` to create and populate the menu bar when the first window
277 - `_GLFW_USE_RETINA` to have windows use the full resolution of Retina displays