Fix issue where incremental dynamic builds do not link to static dependencies. #2196
Conversation
…ndencies. After the recent change to building dynamic frameworks and dylibs as targets built by linking to a static library dependency, incremental builds do not correctly link the dynamic frameworks and dylibs to the rebuilt static library. - Delete dynamic target outputs during static target builds. - Run platform schemes sequentially in manual order. - Build the dynamic framework before the dylib. - Clean up Xcode Scheme organization. It is not entirely obvious what the dependency problem is, and why these particular changes work. A lot of trial-and-error was required. It's possible that Xcode dependency analysis does not correctly analyze the flow used in MoltenVK builds.
|
I wonder if the problem is not having any source files to compile for the dylib target. As a quick and dirty test, I removed the libMoltenVK.a static library from the Link Binary with Libraries area under Build Phases, and added all the MoltenVK source and header files directly to the MoltenVK-macOS-dylib target. This may be duplicating things (I'm not sure actually), but incremental builds do begin working properly after that. UPDATE - Unfortunately it does look like XCode is duplicating the work. I was hoping that it would be a bit smarter about compilation of like units for different targets. Darn. However, I wonder if some smaller source code unit could be created that would force Xcode to see the dependency on a changed libMoltenVK.a? Not sure. In any case, what you have accomplished with your fix works well and is probably the most efficient solution for minimizing compilation time. |
|
@SRSaunders Thanks for looking into options and testing them.
Yeah. It would be nice, especially for the individual object-file compiles. But it appears that in...
...Xcode tracks each target build separately. |
After the recent change to building dynamic frameworks and dylibs as targets built by linking to a static library dependency, incremental builds do not correctly link the dynamic frameworks and dylibs to the rebuilt static library.
It is not entirely obvious what the dependency problem is, and why these particular changes work. A lot of trial-and-error was required. It's possible that Xcode dependency analysis does not correctly analyze the flow used in MoltenVK builds.
This should fix issue #2186.