Skip to content
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

[cppgraphqlgen] Expose clientgen/schemagen features #42267

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cosmopetrich
Copy link

Disabling both of these allows building a version of the library which does not depend on boost. The clientgen/schemagen CLI tools are generally only required in development environments and CI. Thus it may be preferable to link against a boostless cppgraphqlgen when building for release.

Default behaviour for vcpkg users who do not disable default-features when installing cppgraphqlgen remains unchanged.

The flags in question can be found here - https://github.com/microsoft/cppgraphqlgen/blob/681b0e1942521d4dd7806a4badfce9aa703f6dcf/CMakeLists.txt#L37. In testing this works as expected when building both with and without the default feature list. However, I am not very familiar with CMake et al, so please let me know if there are any issues with my implementation.

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

Disabling both of these allows building a version of the library which
does not depend on boost, which can be nice for production deployments.

The default behaviour is unchanged.
@cosmopetrich
Copy link
Author

@microsoft-github-policy-service agree

@WangWeiLin-MV WangWeiLin-MV added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Nov 21, 2024
@BillyONeal
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Comment on lines +20 to +22
"clientgen",
"rapidjson",
"schemagen"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants