[SR-11437] Latest llbuild Package.swift causes resolution errors in SwiftPM & sourcekit-lsp about swift-llbuild HOT 5 CLOSED

Sorry about that! The problem is that the targets have the same name in SwiftPM as they have in tools support core. There are multiple different solutions - each with a drawback. We'll discuss what to do next and revert the dependency from llbuild on tools support core for now: #555

from swift-llbuild.

Comment by Jim Dovey (JIRA)

No worries, I'm glad we were able to get it noticed & fixed quickly. It looks like the commit format for tools-support-core is ultimately to blame, because right now it's just the result of some copying of folders from SwiftPM's Source folder. Unless the Package format allows specifying a different names for the target vs. its source folder, it looks like there's going to be some more hurdles along the road.

Thanks for the quick turnaround.

from swift-llbuild.

That is actually possible. The Package.swift is not generated/copied, just the directories. So we could use different names for the targets and folders in the file system. The problem is that all imports in the source files would need to change to use the same target names as well :/
This will be solved when we remove the code from SwiftPM and it entirely lives in tools-support-core - we need SwiftPM to be able to declare a dependency on tsc first though.

from swift-llbuild.

We merged a temporary workaround of not declaring the new executable in llbuild here. A longer term solution will probably to define a local package for the executable which uses the llbuild package as a dependency.

from swift-llbuild.

Merged the local package in c67ef17

from swift-llbuild.