Merge pull request #1078 from JulianGro/fix_sphinx_warnings

Define code block language to fix sphinx warnings

BUILD.md

@@ -42,15 +42,17 @@ Vircadia uses CMake to generate build files and project files for your platform.
 
 #### Qt
 
-CMake will download Qt 5.12.3 using vcpkg.  
+CMake will download Qt 5.12.3 using vcpkg.
 
-To override this (i.e. use an installed Qt configuration - you will need to set a QT_CMAKE_PREFIX_PATH environment variable pointing to your Qt **lib/cmake** folder.  
+To override this (i.e. use an installed Qt configuration - you will need to set a QT_CMAKE_PREFIX_PATH environment variable pointing to your Qt **lib/cmake** folder.
 This can either be entered directly into your shell session before you build or in your shell profile (e.g.: ~/.bash_profile, ~/.bashrc, ~/.zshrc - this depends on your shell and environment).  The path it needs to be set to will depend on where and how Qt5 was installed. e.g.
 
-    export QT_CMAKE_PREFIX_PATH=/usr/local/Qt5.12.3/gcc_64/lib/cmake
+```bash
-    export QT_CMAKE_PREFIX_PATH=/usr/local/qt/5.12.3/clang_64/lib/cmake/
+export QT_CMAKE_PREFIX_PATH=/usr/local/Qt5.12.3/gcc_64/lib/cmake
-    export QT_CMAKE_PREFIX_PATH=/usr/local/Cellar/qt5/5.12.3/lib/cmake
+export QT_CMAKE_PREFIX_PATH=/usr/local/qt/5.12.3/clang_64/lib/cmake/
-    export QT_CMAKE_PREFIX_PATH=/usr/local/opt/qt5/lib/cmake
+export QT_CMAKE_PREFIX_PATH=/usr/local/Cellar/qt5/5.12.3/lib/cmake
+export QT_CMAKE_PREFIX_PATH=/usr/local/opt/qt5/lib/cmake
+```
 
 #### VCPKG
 
@@ -60,7 +62,9 @@ You do not need to install vcpkg.
 Building the dependencies can be lengthy and the resulting files will be stored in your OS temp directory.
 However, those files can potentially get cleaned up by the OS, so in order to avoid this and having to redo the lengthy build step, you can set the following environment variable:
 
-    export HIFI_VCPKG_BASE=/path/to/directory
+```bash
+export HIFI_VCPKG_BASE=/path/to/directory
+```
 
 Where `/path/to/directory` is the path to a directory where you wish the build files to get stored.
 
@@ -68,45 +72,49 @@ Where `/path/to/directory` is the path to a directory where you wish the build f
 
 ##### Possible Environment Variables
 
-    // The URL to post the dump to.
+```text
-    CMAKE_BACKTRACE_URL
+// The URL to post the dump to.
-    // The identifying tag of the release.
+CMAKE_BACKTRACE_URL
-    CMAKE_BACKTRACE_TOKEN
+// The identifying tag of the release.
-    
+CMAKE_BACKTRACE_TOKEN
-    // The release version, e.g., 2021.3.2.
+
-    RELEASE_NUMBER
+// The release version, e.g., 2021.3.2.
-    // The release name, e.g., Eos.
+RELEASE_NUMBER
-    RELEASE_NAME
+// The release name, e.g., Eos.
-    // The build commit, e.g., use a Git hash for the most recent commit in the branch - fd6973b.
+RELEASE_NAME
-    
+// The build commit, e.g., use a Git hash for the most recent commit in the branch - fd6973b.
-    BUILD_NUMBER
+
-    
+BUILD_NUMBER
-    // The type of release.
+
-    RELEASE_TYPE=PRODUCTION|PR|DEV
+// The type of release.
-    
+RELEASE_TYPE=PRODUCTION|PR|DEV
-    // The Interface will have a custom default home and startup location.
+
-    INITIAL_STARTUP_LOCATION=Location/IP/URL
+// The Interface will have a custom default home and startup location.
-    
+INITIAL_STARTUP_LOCATION=Location/IP/URL
-    // Code-signing environment variables must be set during runtime of CMake AND globally when the signing takes place.
+
-    HF_PFX_FILE=Path to certificate
+// Code-signing environment variables must be set during runtime of CMake AND globally when the signing takes place.
-    HF_PFX_PASSPHRASE=Passphrase for certificate
+HF_PFX_FILE=Path to certificate
-    
+HF_PFX_PASSPHRASE=Passphrase for certificate
-    // Determine the build type
+
-    PRODUCTION_BUILD=0|1
+// Determine the build type
-    PR_BUILD=0|1
+PRODUCTION_BUILD=0|1
-    STABLE_BUILD=0|1
+PR_BUILD=0|1
-    
+STABLE_BUILD=0|1
-    // Determine if to utilize testing or stable Metaverse URLs
+
-    USE_STABLE_GLOBAL_SERVICES=1
+// Determine if to utilize testing or stable Metaverse URLs
-    BUILD_GLOBAL_SERVICES=STABLE
+USE_STABLE_GLOBAL_SERVICES=1
-    
+BUILD_GLOBAL_SERVICES=STABLE
+```
+
 ##### Generate Files
 
 Create a build directory in the root of your checkout and then run the CMake build from there. This will keep the rest of the directory clean.
 
-    mkdir build
+```bash
-    cd build
+mkdir build
-    cmake ..
+cd build
+cmake ..
+```
 
 If CMake gives you the same error message repeatedly after the build fails, try removing `CMakeCache.txt`.
 
@@ -128,7 +136,9 @@ Any variables that need to be set for CMake to find dependencies can be set as E
 
 For example, to pass the QT_CMAKE_PREFIX_PATH variable (if not using the vcpkg'ed version) during build file generation:
 
-    cmake .. -DQT_CMAKE_PREFIX_PATH=/usr/local/qt/5.12.3/lib/cmake
+```bash
+cmake .. -DQT_CMAKE_PREFIX_PATH=/usr/local/qt/5.12.3/lib/cmake
+```
 
 #### Finding Dependencies
 

BUILD_ANDROID.md

@@ -42,11 +42,13 @@ Follow the directions [here](https://developer.android.com/studio/publish/app-si
 
 Create a `gradle.properties` file in the `.gradle` folder (`$HOME/.gradle` on Unix, `Users/<yourname>/.gradle` on Windows). Edit the file to contain the following
 
-    HIFI_ANDROID_PRECOMPILED=<your_home_directory>/Android/hifi_externals
+```properties
-    HIFI_ANDROID_KEYSTORE=<key_store_directory>/<keystore_name>.jks
+HIFI_ANDROID_PRECOMPILED=<your_home_directory>/Android/hifi_externals
-    HIFI_ANDROID_KEYSTORE_PASSWORD=<password>
+HIFI_ANDROID_KEYSTORE=<key_store_directory>/<keystore_name>.jks
-    HIFI_ANDROID_KEY_ALIAS=<key_alias>
+HIFI_ANDROID_KEYSTORE_PASSWORD=<password>
-    HIFI_ANDROID_KEY_PASSWORD=<key_passwords>
+HIFI_ANDROID_KEY_ALIAS=<key_alias>
+HIFI_ANDROID_KEY_PASSWORD=<key_passwords>
+```
 
 Note, do not use $HOME for the path. It must be a fully qualified path name. Also, be sure to use forward slashes in your path.
 
@@ -54,21 +56,26 @@ Note, do not use $HOME for the path. It must be a fully qualified path name. Als
 
 Add these lines to `gradle.properties`
 
-    SUPPRESS_QUEST_INTERFACE
+```properties
-    SUPPRESS_QUEST_FRAME_PLAYER
+SUPPRESS_QUEST_INTERFACE
+SUPPRESS_QUEST_FRAME_PLAYER
+```
 
 #### If you are building for an Oculus Quest
 
 Add these lines to `gradle.properties`
 
-    SUPPRESS_INTERFACE
+```properties
-    SUPPRESS_FRAME_PLAYER
+SUPPRESS_INTERFACE
-
+SUPPRESS_FRAME_PLAYER
+```
 
 #### The Frame Player for both Android Phone and Oculus Quest is optional, so if you encounter problems with these during your build, you can skip them by adding these lines to `gradle.properties`
 
-    SUPPRESS_FRAME_PLAYER
+```properties
-    SUPPRESS_QUEST_FRAME_PLAYER
+SUPPRESS_FRAME_PLAYER
+SUPPRESS_QUEST_FRAME_PLAYER
+```
 
 ### Clone the repository
 

BUILD_OSX.md

@@ -8,22 +8,26 @@ Please read the [general build guide](BUILD.md) for information on dependencies
 
 [Homebrew](https://brew.sh/) is an excellent package manager for macOS. It makes install of some Vircadia dependencies very simple.
 
-    brew install cmake openssl npm
+```bash
+brew install cmake openssl npm
+```
 
 ### Python 3
 
-Download an install Python 3.6.6 or higher from [here](https://www.python.org/downloads/).  
+Download an install Python 3.6.6 or higher from [here](https://www.python.org/downloads/).
 Execute the `Update Shell Profile.command` script that is provided with the installer.
 
 ### OSX SDK
 
 You will need version `10.12` of the OSX SDK for building, otherwise you may have crashing or other unintended issues due to the deprecation of OpenGL on OSX. You can get that SDK from [here](https://github.com/phracker/MacOSX-SDKs). You must copy it in to your Xcode SDK directory, e.g.
 
-    cp -rp ~/Downloads/MacOSX10.12.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
+```bash
+cp -rp ~/Downloads/MacOSX10.12.sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
+```
 
 ### OpenSSL
 
-Assuming you've installed OpenSSL using the homebrew instructions above, you'll need to set OPENSSL_ROOT_DIR so CMake can find your installations.  
+Assuming you've installed OpenSSL using the homebrew instructions above, you'll need to set OPENSSL_ROOT_DIR so CMake can find your installations.
 For OpenSSL installed via homebrew, set OPENSSL_ROOT_DIR via
     `export OPENSSL_ROOT_DIR=/usr/local/opt/openssl`
     or by appending `-DOPENSSL_ROOT_DIR=/usr/local/opt/openssl` to `cmake`
@@ -31,12 +35,14 @@ For OpenSSL installed via homebrew, set OPENSSL_ROOT_DIR via
 ### Xcode
 
 You can ask CMake to generate Xcode project files instead of Unix Makefiles using the `-G Xcode` parameter after CMake. You will need to select the Xcode installation in the terminal first if you have not done so already.
-    
-    sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
-    
-    cmake ../ -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk" -DCMAKE_OSX_DEPLOYMENT_TARGET=10.12 -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -DOSX_SDK=10.12  ..
 
-If `cmake` complains about Python 3 being missing, you may need to update your CMake binary with command `brew upgrade cmake`, or by downloading and running the latest CMake installer, depending on how you originally instaled CMake 
+```bash
+sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
+
+cmake ../ -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk" -DCMAKE_OSX_DEPLOYMENT_TARGET=10.12 -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl -DOSX_SDK=10.12  ..
+```
+
+If `cmake` complains about Python 3 being missing, you may need to update your CMake binary with command `brew upgrade cmake`, or by downloading and running the latest CMake installer, depending on how you originally installed CMake.
 
 After running CMake, you will have the make files or Xcode project file necessary to build all of the components. Open the hifi.xcodeproj file, choose ALL_BUILD from the Product > Scheme menu (or target drop down), and click Run.