Lines Matching +full:default +full:- +full:build +full:- +full:release

7 you to build project/make files for any platform. For details on `cmake`, see
11     cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release
12     cmake -G "Visual Studio 10" -DCMAKE_BUILD_TYPE=Release
13     cmake -G "Xcode" -DCMAKE_BUILD_TYPE=Release
15 Then, build as normal for your platform. This should result in a `flatc`
19 `CC=/usr/bin/clang CXX=/usr/bin/clang++ cmake -G "Unix Makefiles"`.
34 By default all Flatbuffers `cmake` targets are **not** built with the `-Werror` 
37 may add new warnings that would cause a build failure.
39 To enable a stricter build that does treat warnings as errors, set the
43 cmake . -DFLATBUFFERS_STRICT_MODE=ON
57     ./bootstrap-vcpkg.sh
66 [GitHub release page](https://github.com/google/flatbuffers/releases).
68 …(slsa.dev) using the OpenSSF's [slsa-framework/slsa-github-generator](https://github.com/slsa-fram…
69 …tall the verification tool from [slsa-framework/slsa-verifier#installation](https://github.com/sls…
70 1. Download the file named `attestation.intoto.jsonl` from the GitHub release
73 $ slsa-verifier -artifact-path <downloaded.zip> -provenance attestation.intoto.jsonl -source github…
78 There is a `flatbuffers/android` directory that contains all you need to build
85 `flatbuffers/samples/android` folder and build the sample with the
102 ### Using in CMake-based projects
104 robust and flexible approach is to build FlatBuffers as part of that project directly.
105 This is done by making the FlatBuffers source code available to the main build
109 incompatible libraries (eg debug/release), etc. are avoided. This is
113 To build it as part of your project, add following code to your `CMakeLists.txt` file:
115 # Add FlatBuffers directly to our build. This defines the `flatbuffers` target.
117                  ${CMAKE_CURRENT_BINARY_DIR}/flatbuffers-build
124 When build your project the `flatbuffers` library will be compiled and linked 
127 #### Override default depth limit of nested objects