3D图形开源压缩库Draco.zip

<p align="center"> <img src="docs/DracoLogo.jpeg" /> </p> News ======= ### Version 1.3.5 release * Added option to build Draco for Universal Scene Description * Code cleanup * Bug fixes ### Version 1.3.4 release * Released Draco Animation code * Fixes for Unity * Various file location and name changes ### Version 1.3.3 release * Added ExpertEncoder to the Javascript API * Allows developers to set quantization options per attribute id * Bug fixes ### Version 1.3.2 release * Bug fixes ### Version 1.3.1 release * Fix issue with multiple attributes when skipping an attribute transform ### Version 1.3.0 release * Improved kD-tree based point cloud encoding * Now applicable to point clouds with any number of attributes * Support for all integer attribute types and quantized floating point types * Improved mesh compression up to 10% (on average ~2%) * For meshes, the 1.3.0 bitstream is fully compatible with 1.2.x decoders * Improved Javascript API * Added support for all signed and unsigned integer types * Added support for point clouds to our Javascript encoder API * Added support for integer properties to the PLY decoder * Bug fixes ### Previous releases https://github.com/google/draco/releases Description =========== Draco is a library for compressing and decompressing 3D geometric [meshes] and [point clouds]. It is intended to improve the storage and transmission of 3D graphics. Draco was designed and built for compression efficiency and speed. The code supports compressing points, connectivity information, texture coordinates, color information, normals, and any other generic attributes associated with geometry. With Draco, applications using 3D graphics can be significantly smaller without compromising visual fidelity. For users, this means apps can now be downloaded faster, 3D graphics in the browser can load quicker, and VR and AR scenes can now be transmitted with a fraction of the bandwidth and rendered quickly. Draco is released as C++ source code that can be used to compress 3D graphics as well as C++ and Javascript decoders for the encoded data. _**Contents**_ * [Building](#building) * [CMake Basics](#cmake-basics) * [Mac OS X](#mac-os-x) * [Windows](#windows) * [CMake Build Configuration](#cmake-build-configuration) * [Debugging and Optimization](#debugging-and-optimization) * [Googletest Integration](#googletest-integration) * [Javascript Encoder/Decoder](#javascript-encoderdecoder) * [Android Studio Project Integration](#android-studio-project-integration) * [Native Android Builds](#native-android-builds) * [Usage](#usage) * [Command Line Applications](#command-line-applications) * [Encoding Tool](#encoding-tool) * [Encoding Point Clouds](#encoding-point-clouds) * [Decoding Tool](#decoding-tool) * [C++ Decoder API](#c-decoder-api) * [Javascript Encoder API](#javascript-encoder-api) * [Javascript Decoder API](#javascript-decoder-api) * [Javascript Decoder Performance](#javascript-decoder-performance) * [Metadata API](#metadata-api) * [NPM Package](#npm-package) * [three.js Renderer Example](#threejs-renderer-example) * [Support](#support) * [License](#license) * [References](#references) Building ======== For all platforms, you must first generate the project/make files and then compile the examples. CMake Basics ------------ To generate project/make files for the default toolchain on your system, run `cmake` from a directory where you would like to generate build files, and pass it the path to your Draco repository. ~~~~~ bash $ cmake path/to/draco ~~~~~ On Windows, the above command will produce Visual Studio project files for the newest Visual Studio detected on the system. On Mac OS X and Linux systems, the above command will produce a `makefile`. To control what types of projects are generated, add the `-G` parameter to the `cmake` command. This argument must be followed by the name of a generator. Running `cmake` with the `--help` argument will list the available generators for your system. Mac OS X --------- On Mac OS X, run the following command to generate Xcode projects: ~~~~~ bash $ cmake path/to/draco -G Xcode ~~~~~ Windows ------- On a Windows box you would run the following command to generate Visual Studio 2015 projects: ~~~~~ bash C:\Users\nobody> cmake path/to/draco -G "Visual Studio 14 2015" ~~~~~ To generate 64-bit Windows Visual Studio 2015 projects: ~~~~~ bash C:\Users\nobody> cmake path/to/draco -G "Visual Studio 14 2015 Win64" ~~~~~ CMake Build Configuration ------------------------- Debugging and Optimization -------------------------- Unlike Visual Studio and Xcode projects, the build configuration for make builds is controlled when you run `cmake`. The following examples demonstrate various build configurations. Omitting the build type produces makefiles that use release build flags by default: ~~~~~ bash $ cmake path/to/draco ~~~~~ A makefile using release (optimized) flags is produced like this: ~~~~~ bash $ cmake path/to/draco -DCMAKE_BUILD_TYPE=release ~~~~~ A release build with debug info can be produced as well: ~~~~~ bash $ cmake path/to/draco -DCMAKE_BUILD_TYPE=relwithdebinfo ~~~~~ And your standard debug build will be produced using: ~~~~~ bash $ cmake path/to/draco -DCMAKE_BUILD_TYPE=debug ~~~~~ To enable the use of sanitizers when the compiler in use supports them, set the sanitizer type when running CMake: ~~~~~ bash $ cmake path/to/draco -DSANITIZE=address ~~~~~ Googletest Integration ---------------------- Draco includes testing support built using Googletest. To enable Googletest unit test support the ENABLE_TESTS cmake variable must be turned on at cmake generation time: ~~~~~ bash $ cmake path/to/draco -DENABLE_TESTS=ON ~~~~~ When cmake is used as shown in the above example the Draco cmake file assumes that the Googletest source directory is a sibling of the Draco repository. To change the location to something else use the GTEST_SOURCE_DIR cmake variable: ~~~~~ bash $ cmake path/to/draco -DENABLE_TESTS=ON -DGTEST_SOURCE_DIR=path/to/googletest ~~~~~ To run the tests just execute `draco_tests` from your toolchain's build output directory. Javascript Encoder/Decoder ------------------ The javascript encoder and decoder can be built using the existing cmake build file by passing the path the Emscripten's cmake toolchain file at cmake generation time in the CMAKE_TOOLCHAIN_FILE variable. In addition, the EMSCRIPTEN environment variable must be set to the local path of the parent directory of the Emscripten tools directory. ~~~~~ bash # Make the path to emscripten available to cmake. $ export EMSCRIPTEN=/path/to/emscripten/tools/parent # Emscripten.cmake can be found within your Emscripten installation directory, # it should be the subdir: cmake/Modules/Platform/Emscripten.cmake $ cmake path/to/draco -DCMAKE_TOOLCHAIN_FILE=/path/to/Emscripten.cmake # Build the Javascript encoder and decoder. $ make ~~~~~ WebAssembly Decoder ------------------- The WebAssembly decoder can be built using the existing cmake build file by passing the path the Emscripten's cmake toolchain file at cmake generation time in the CMAKE_TOOLCHAIN_FILE variable and enabling the WASM build option. In addition, the EMSCRIPTEN environment variable must be set to the local path of the parent directory of the Emscripten tools directory. Make sure to have the correct version of Emscripten installed for WebAssembly builds. See https://developer.mozilla.org/en-US/docs/WebAssembly. ~~~~~ bash # Make the path to emscripten available to cmake. $ export EMSCRIPTEN=/path/to/emscripten/tools/parent # Emscripten.cmake can be found within your Emscripten installation directory, # it should be the subdir: cmake/Modules/Platform/Emscripten.cmake $ cmake path/to/draco -DCMAKE_TOOLCHAIN_FILE=/path/to/Emscripten.cmake -DENABLE_WASM=ON # Build the WebAssembly decoder. $ make # Run the J