Remove papilo from getting added to packaging

[ramakrishnap-nv]

Description

A follow-up PR for #507, this PR uses EXCLUDE_FROM_ALL on papilo.

Checklist

• I am familiar with the Contributing Guidelines.
• Testing
  • New or existing tests cover these changes
  • Added tests
  • Created an issue to follow-up
  • NA
• Documentation
  • The documentation is up to date with these changes
  • Added new documentation
  • NA

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes adjust how papilo dependencies are handled during wheel packaging and build. A shell script re-enables libpapilo-core.a inclusion, CMakeLists.txt marks papilo to be excluded from default top-level builds, and pyproject.toml removes directory exclusions for papilo cmake artifacts.

Changes

Cohort / File(s)	Change Summary
Build wheel configuration ci/build_wheel_libcuopt.sh, python/libcuopt/pyproject.toml	Commented out libpapilo-core.a exclusion in shell script; removed papilo cmake directory exclusions from wheel packaging configuration
CMake build system cpp/CMakeLists.txt	Added EXCLUDE_FROM_ALL flag to papilo FetchContent_Declare to prevent default top-level build inclusion

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A wheel now rolls with papilo inside,
Build flags whisper, exclusions subside,
CMake declares what should not build by default,
While dependencies settle, snug in their vault! 🛞

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Remove papilo from getting added to packaging" is clearly related to the changeset's main objective. The pull request implements changes across three files to prevent papilo from being included in the final wheel package: adding EXCLUDE_FROM_ALL to the CMakeLists.txt to prevent papilo from being built during top-level build, commenting out the libpapilo-core.a exclusion in the build script (since it won't be built anyway), and removing papilo-related exclusion entries from pyproject.toml. The title concisely captures this primary goal and is specific enough that a reviewer can understand the main intent.
Description Check	✅ Passed	The description "A follow-up PR for #507, this PR uses EXCLUDE_FROM_ALL on papilo" is directly related to the changeset. It provides meaningful context by referencing the related issue for package size reduction and describing the specific implementation approach (EXCLUDE_FROM_ALL), which is the core mechanism underlying all three file changes. The description meaningfully connects to the actual changes being made, even though it is brief.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ramakrishnap-nv]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[vyasr]

Looks good, thanks for the fix.

[ramakrishnap-nv]

/merge