Xcode has a field FRAMEWORK_SEARCH_PATHS, which is used to search header files inside frameworks. right now we have LIBRARY_SEARCH_PATHS, but FRAMEWORK_SEARCH_PATHS will allow searching within the .framework.
So I made it so FRAMEWORK_SEARCH_PATHS will have the same contents as LIBRARY_SEARCH_PATHS.
An example of this would be SDL2.framework header files, they have<SDL2/SDL_main.h> now, by pointing LIBRARY_SEARCH_PATHS to SDL2.framework/headers it wouldn't work. However, by pointing FRAMEWORK_SEARCH_PATHS to the root folder where SDL2.framework file is, it will work. This fixed my building projects at least.
I guess we could also have a separate field for FRAMEWORK_SEARCH_PATHS, but I feel like pulling the values there as well we don't have to change any existing scripts for anyone switching from a dylib to a .framework.
Let me know your thoughts. Thanks for considering.
Xcode has a field FRAMEWORK_SEARCH_PATHS, which is used to search header files inside frameworks. right now we have LIBRARY_SEARCH_PATHS, but FRAMEWORK_SEARCH_PATHS will allow searching within the .framework.
https://help.apple.com/xcode/mac/11.4/#/itcaec37c2a6
So I made it so FRAMEWORK_SEARCH_PATHS will have the same contents as LIBRARY_SEARCH_PATHS.
An example of this would be SDL2.framework header files, they have<SDL2/SDL_main.h> now, by pointing LIBRARY_SEARCH_PATHS to SDL2.framework/headers it wouldn't work. However, by pointing FRAMEWORK_SEARCH_PATHS to the root folder where SDL2.framework file is, it will work. This fixed my building projects at least.
I guess we could also have a separate field for FRAMEWORK_SEARCH_PATHS, but I feel like pulling the values there as well we don't have to change any existing scripts for anyone switching from a dylib to a .framework.
Let me know your thoughts. Thanks for considering.