moltenvk

These external open-source libraries are maintained in the External directory. To retrieve these libraries from their sources, run the fetchDependencies script in the main repository directory:

./fetchDependencies

Updating External Library Versions

To maintain consistency between the libraries, MoltenVK retrieves specific versions of each external library. The version of each external library is determined as follows:

cereal: a GitHub repository commit identifier found in the ExternalRevisions/cereal_repo_revision file.
Vulkan-Headers: a GitHub repository commit identifier found in the ExternalRevisions/Vulkan-Headers_repo_revision file.
SPIRV-Cross: a GitHub repository commit identifier found in the ExternalRevisions/SPIRV-Cross_repo_revision file.
glslang: a GitHub repository commit identifier found in the ExternalRevisions/glslang_repo_revision file.
SPIRV-Tools: automatically retrieved by the glslang repository.
SPIRV-Headers: automatically retrieved by the glslang repository.
Vulkan-Tools: a GitHub repository commit identifier found in the ExternalRevisions/Vulkan-Tools_repo_revision file.
VulkanSamples: a GitHub repository commit identifier found in the ExternalRevisions/VulkanSamples_repo_revision file.

You can update which versions of the cereal, Vulkan-Headers, SPIRV-Cross, glslang, Vulkan-Tools, or VulkanSamples libraries are retrieved by changing the value held in the corresponding *_repo_revision file listed above.

The version of the SPIRV-Tools and SPIRV-Headers libraries is automatically determined by the version of the glslang library you have retrieved.

Once you have made changes to the *_repo_revision files, you can retrieve the updated library versions by running the fetchDependencies script again.

Note: If, after updating to new versions of the external libraries, you encounter build errors when building MoltenVK, review the instructions in the sections below to ensure all necessary external library files are included in the MoltenVK builds.

Adding the cereal Library to the MoltenVK Xcode Project

The MoltenVK Xcode project is already configured to use the cereal library. However, after updating the version of cereal, as described above, if you encounter any building errors, you may need to re-add the cereal library to the MoltenVK Xcode project as follows:

In the Project Navigator panel, select the MoltenVK Xcode project, then the MoltenVK project target, and open the Build Settings tab. Locate the build setting entry Header Search Paths (HEADER_SEARCH_PATHS) and add the following paths:
```
 "$(SRCROOT)/../External/cereal/include"
```

Adding the SPIRV-Cross Library to the MoltenVKShaderConverter Xcode Project

The MoltenVKShaderConverter Xcode project is already configured to use the SPIRV-Cross library. However, after updating the version of SPIRV-Cross, as described above, if you encounter any building errors, you may need to re-add the SPIRV-Cross library to the MoltenVKShaderConverter Xcode project as follows:

In the Project Navigator, remove all of the files under the Group named MoltenVKSPIRVToMSLConverter/SPIRV-Cross.
Drag the following files from the External/SPIRV-Cross directory to the SPIRV-Cross group in the Project Navigator panel:
```
 spirv_cfg.cpp
 spirv_cfg.hpp
 spirv_common.hpp
 spirv_cross.cpp
 spirv_cross.hpp
 spirv_glsl.cpp
 spirv_glsl.hpp
 spirv_msl.cpp
 spirv_msl.hpp
```
In the Choose options for adding these files dialog that opens, select the Create groups option, add the files to both the MoltenVKSPIRVToMSLConverter-iOS and MoltenVKSPIRVToMSLConverter-macOS targets, and click the Finish button.
(Optional) To simplify the paths used within Xcode to reference the added files, perform the following steps:
1. Create a backup of your project! This is an intrusive and dangerous operation!
2. In the Finder, right-click your MoltenVKShaderConverter.xcodeproj file and select Show Package Contents.
3. Open the project.pbxproj file in a text editor.
4. Remove all occurrences of path-to-SPIRV-Cross-repo-folder from the paths to the files added above.

Regression Testing Your Changes to SPIRV-Cross

If you make changes to the SPIRV-Cross repository, you can regression test your changes using the following steps:

Load and build the versions of SPRIV-Tools and glslang that are used by the SPIRV-Cross tests:

 cd External/SPIRV-Cross
 ./checkout_glslang_spirv_tools.sh
 ./build_glslang_spirv_tools.sh

Build SPIRV-Cross:
```
 make
```
Run the regression tests:
```
 ./test_shaders.sh
```
If your changes result in different expected output for a reference shader, and the new results are correct, you can update the reference shader for a particular regression test by deleting that reference shader, in either External/SPIRV-Cross/reference/shaders-msl or External/SPIRV-Cross/reference/opt/shaders-msl, and running the test again. The test will replace the deleted reference shader.

Adding the glslang Library to the MoltenVKShaderConverter Xcode Project

The MoltenVKShaderConverter Xcode project is already configured to use the glslang library. However, after updating the version of glslang, as described above, if you encounter any building errors, you may need to re-add the glslang library to the MoltenVKShaderConverter Xcode project as follows:

In the Project Navigator, remove all Groups from under the Group named MoltenVKGLSLToSPIRVConverter/glslang.
Drag the following folders from the External/glslang file folder to the glslang Group in the Project Navigator panel:
```
 glslang
 OGLCompilersDLL
 SPIRV
```
In the Choose options for adding these files dialog that opens, select the Create groups option, add the files to both the MoltenVKGLSLToSPIRVConverter-iOS and MoltenVKGLSLToSPIRVConverter-macOS targets, and click the Finish button.
In the Project Navigator panel, remove the references to the following files and folders:
```
 glslang/glslang/MachineIndependant/glslang.y
 glslang/glslang/OSDependent/Windows
```
(Optional) To simplify the paths used within Xcode to reference the added files, perform the following steps:
1. Create a backup of your project! This is an intrusive and dangerous operation!
2. In the Finder, right-click your MoltenVKShaderConverter.xcodeproj file and select Show Package Contents.
3. Open the project.pbxproj file in a text editor.
4. Remove all occurrences of path-to-glslang-repo-folder from the paths to the glslang, OGLCompilersDLL, and SPIRV directories added above.

Adding the SPIRV-Tools Library to the MoltenVKShaderConverter Xcode Project

The MoltenVKShaderConverter Xcode project is already configured to use the SPIRV-Tools library. However, after updating the version of SPIRV-Tools, as described above, if you encounter any building errors, you may need to re-add the SPIRV-Tools library to the MoltenVKShaderConverter Xcode project as follows:

In the Project Navigator, remove the Group named source from under the Group named MoltenVKSPIRVToMSLConverter/SPIRV-Tools.
Drag the External/glslang/Extermal/spirv-tools/source file folder to the SPIRV-Tools group in the Project Navigator panel. In the Choose options for adding these files dialog that opens, select the Create groups option, add the files to both the MoltenVKSPIRVToMSLConverter-iOS and MoltenVKSPIRVToMSLConverter-macOS targets, and click the Finish button.
In the Project Navigator panel, select the MoltenVKShaderConverter Xcode project, then select the MoltenVKSPIRVToMSLConverter-macOS target, and open the Build Settings tab. Locate the build setting entry Header Search Paths (HEADER_SEARCH_PATHS) and add the following paths:
```
 "$(SRCROOT)/glslang/External/spirv-tools"
 "$(SRCROOT)/glslang/External/spirv-tools/include"
 "$(SRCROOT)/glslang/External/spirv-tools/external/spirv-headers/include"
 "$(SRCROOT)/glslang/build/External/spirv-tools"
```
Repeat Step 3 for the MoltenVKSPIRVToMSLConverter-iOS target within the MoltenVKShaderConverter Xcode project
(Optional) To simplify the paths used within Xcode to reference the added files, perform the following steps:
1. Create a backup of your project! This is an intrusive and dangerous operation!
2. In the Finder, right-click your MoltenVKShaderConverter.xcodeproj file and select Show Package Contents.
3. Open the project.pbxproj file in a text editor.
4. Remove all occurrences of path-to-SPIRV-Tools-repo-folder from the paths to the source directory added above.

README.md