ENH: Add support to find Headers in Apple Frameworks by hjmjohnson · Pull Request #448 · cppcheck-opensource/simplecpp
added a commit to hjmjohnson/PythonQt that referenced this pull request
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: cppcheck-opensource/simplecpp#448
hjmjohnson added a commit to hjmjohnson/PythonQt that referenced this pull request
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: cppcheck-opensource/simplecpp#448
hjmjohnson added a commit to hjmjohnson/PythonQt that referenced this pull request
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: cppcheck-opensource/simplecpp#448
hjmjohnson added a commit to hjmjohnson/PythonQt that referenced this pull request
Add specific framework path handling Refactor include directory parsing to support multiple candidate paths for headers and introduce macOS-specific logic for resolving framework-relative header paths. Enhance generator flexibility and robustness for cross-platform usage. Push upstream fix via: cppcheck-opensource/simplecpp#448
The header locations in apple frameworks require manipulation of the directory name in a '<pkg/myhdr.h>' include defintion. The header file is located at <pkg.framework/Headers/myhdr.h> in a framework.
This was referenced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters