-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need cmake to "install" cert tool to proper location #186
Comments
I don't think anybody outside of Valve has used any of the PKI, to be honest. So this tool (and the PKI) does work, because we use it -- but you should know that you might be one of the first people to actually use it outside of Valve. We probably should have a way to build it in cmake. |
yes you're right indeed, i see your point. |
Added the help wanted label. This should be a pretty straightforward job for anybody with basic cmake knowledge. |
Added MSVC_CRT_STATIC option. Defaults to off. Should help with linking against protobuf or other situations. Added BUILD_STATIC_LIB and BUILD_SHARED_LIB options. (Fixes issue #191) I think I probably also need to add an option to build the cert tool and maybe package it up, too (issue #186) but that isn't included in this change.
This is progress towards fixing #186. However, I need some help publishing/installing (or whatever it's called) properly, and there is probably a better way to integrate with picojson than using a git submodule.
You can now build the cert tool by initializing the picojson git submodule and passing -DBUILD_TOOLS=ON to cmake. I could use some help from somebody who knows cmake and/or vcpkg to "publish/install" the tool in the appropriate place and integrate with vcpkg better. |
OK, dc80d53 fixes a compile issue on Windows. The vcpkg.info file has a "feature" for tools. So I think the last step is just that I just need to know the proper way to "install" the tool. Changing the title of this bug to reflect what is missing. |
When running the 'vcpkg' building, i was looking to the tests provided and realized that steamnetworkingsockets_certtool.exe was missing, GameNetworkingSockets.dll althougt was sucessfully created. So i have a simple question:
-- Is this behaviour intended on purpose or it has not been included into this build proccess ?
Thanks in advance.
Building on Windows x64
The text was updated successfully, but these errors were encountered: