For a certain project, I've been building the CF opensource drop from opensource.apple.com for years. After swift-corelibs-foundation got released, Apple appears to have stopped releasing CF (there haven't been any releases since 10.10), which makes me sad because I'm missing out on any of the new functionality. I was pleased to see that the CoreFoundation source code in swift-corelibs-foundation actually appears to be far more complete than the CFLite that used to get released, but the build is now very different and it seems quite difficult to wrangle it into producing the .framework properly for me.
I've tried amending the CoreFoundation/build.py to create a Framework instead of a DynamicLibrary, but unfortunately the resulting ninja build file is broken and doesn't work. I'm currently hacking up the DynamicLibrary build and manually copying the dynamic library and headers to the correct locations in CoreFoundation.framework, but this feels hacky and frustrating when the build system is already so close to producing a legit .framework and clearly supports the functionality already (even separating private headers from public ones!).
Are there plans to make the CoreFoundation build in swift-corelibs-foundation more of its own standalone thing? When I tried to build it yesterday, I noticed the build was actually broken (I submitted a PR which is now merged), so I get the sense that nobody uses it except paired with Foundation, for Swift. On one hand, I don't want to go "against the grain", but on the other hand, the lack of CF releases on opensource.apple.com leaves me little choice.
I do realize that this isn't really a supported use case, but it's also so close to being possible that I'd be willing to put in the work to make a separate CoreFoundation.framework build working, if folks at Apple would be willing to accept PRs toward that goal.