Skip to content

[opensubdiv] Expose build options via vcpkg package #20871

@thomthom

Description

@thomthom

Is your feature request related to a problem? Please describe.
OpenSubdiv have a number of configuration options.

https://github.com/PixarAnimationStudios/OpenSubdiv/blob/ff76e0f2dc9c9202b7d2f965f264bfd6f41866d5/CMakeLists.txt#L298-L324

Personally I only use the CPU libraries, not any of the GPU libraries. Minimal OSD configuration via CMake:

cmake ^
  -D NO_EXAMPLES=1 ^
  -D NO_TUTORIALS=1 ^
  -D NO_REGRESSION=1 ^
  -D NO_PTEX=1 ^
  -D NO_DOC=1 ^
  -D NO_OMP=1 ^
  -D NO_TBB=1 ^
  -D NO_CUDA=1 ^
  -D NO_OPENCL=1 ^
  -D NO_CLEW=1 ^
  -D NO_OPENGL=1 ^
  -D NO_METAL=1 ^
  -D NO_DX=1 ^
  -D NO_TESTS=1 ^
  -D NO_GLTESTS=1 ^
  -D NO_GLEW=1 ^
  -D NO_GLFW=1 ^
  -D NO_GLFW_X11=1 ^
  ..

Proposed solution
From what I understand vcpkg support "features" that allow you to control options: https://vcpkg.readthedocs.io/en/latest/users/manifests/

Would it be possible to have the OSD options exposed via the vcpkg such that one can easily build with only the options needed?

Describe alternatives you've considered
I guess I building with several of the options enabled would work, but it adds to the build time. Impacting local development and CI builds.

Metadata

Metadata

Assignees

Labels

category:port-featureThe issue is with a library, which is requesting new capabilities that didn’t exist

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions