Example using a WKT

[thomasvl]

This does not work with the protoc built locally because the WKTs aren't found. If you try building using the env variable to provide a full protoc install, then it works since that bundles all the WKTs and the proto compiler auto finds the bundled files.

See #1943 for some of the research into options in this space.

[FranzBusch]

This does not work with the protoc built locally because the WKTs aren't found

Would be great if we can fix that as well. Is it just about building them and adding a -I?

[thomasvl]

This does not work with the protoc built locally because the WKTs aren't found

Would be great if we can fix that as well. Is it just about building them and adding a -I?

Either we provide a -I directive to point to all the files, or we bundle the files next to the binary the startup code can auto find them.

[FranzBusch]

This does not work with the protoc built locally because the WKTs aren't found

Would be great if we can fix that as well. Is it just about building them and adding a -I?

Either we provide a -I directive to point to all the files, or we bundle the files next to the binary the startup code can auto find them.

I don't think we can move the files next to the binary since when protoc is built from source the binary is somewhere in the build directory. It seems like the best path forward is for the Swift PM plugin to add a -I directive into the submodule where the WKTs are.

[thomasvl]

This does not work with the protoc built locally because the WKTs aren't found

Would be great if we can fix that as well. Is it just about building them and adding a -I?

Either we provide a -I directive to point to all the files, or we bundle the files next to the binary the startup code can auto find them.

I don't think we can move the files next to the binary since when protoc is built from source the binary is somewhere in the build directory. It seems like the best path forward is for the Swift PM plugin to add a -I directive into the submodule where the WKTs are.

The resources support seems like it should do this (not the exact structure we need), but I couldn't figure out how to make SwiftPM resources work at all for the plugin binary.

And I didn't see any way to get a path back to where the sources for the plugin exist on disk.