I just pushed a commit to fix the libextism example on macOS - the only thing I didn't fix is on macOS -framework Security also needs to be linked in the static pkg-config file - what do you think the best way of handling that is?

Thanks! The best way of handling it is probably adding another variable to the template, extism-static-pc.in, and having the cli fill it in like it does for the prefix. Normally it would be empty, but on mac it would have -framework Security

Alright I can add that - I think I can probably do something similar but avoid adding a variable so we maintain compatibility with existing CLI installations

Maintaining compatibility is better, good idea.

Alright, this seems to be working now - let me know if you see anything that looks off @G4Vi (I don't think you can "review" your own PR)

I also have extism/cli#94 ready to merge

Looks good to me. The only thing I wonder about is -framework Security being part of Libs instead of Libs.private, but if it needs to go before libextism when it has to. Have you seen any other pkgconfig that uses it?

If you review I can merge without bypassing branch protections.

Including it in Libs.private still resulted in the linker error but Libs worked - I'm not sure why though. It could be the order of the libraries, but based on this search https://github.com/search?q=%22-framework+Security%22+path%3A*.pc&type=code it looks like people are using both Libs and Libs.private.