composing cps files (or how to handle debug builds created seperately)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system
Research direction
Review the sample CPS configuration in the issue and investigate how separate Meson debug and optimized builds are represented. Determine whether CPS should define a composition mechanism for separate files or discontinue reporting both configurations in one file; the issue is done when one approach is specified clearly.
Written by the indexing model from the issue text.
Description
Meson doesn't have (by design) a way to generate debug and optimized targets in the same build, instead we would recommend two separate builds for that (we only have out of tree builds, so this is super trivial for us).
The sample has this:
{
"sample-shared": {
"Type": "dylib",
"Requires": [ ":sample-core" ],
"Configurations": {
"Optimized": {
"Location": "@prefix@/lib64/libsample.so.1.2.0"
},
"Debug": {
"Location": "@prefix@/lib64/libsample_d.so.1.2.0"
}
}
}
}
It would be impossible for meson to generate this CPS file, however, because of that design decision. For us we would either need a standard way to compose cps files, or to drop the ability to report debug and optimized in a single cps file.
- Dominant language
- Python
- Stars
- 191
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cps-org/cps
-
Spec: `c-runtime-vendor` field also should document the "musl" typical value and "bionic"Possibly taken @leha-bot claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 40/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jbacalso24/mimry#291 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Under an hour Newbie friendliness 82/100
eli-alvarado/us-watchlist-alerts#14 ·
Maintainers usually reply within 1 day
-
from-review-extraction python severity:nit
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
LearningCircuit/local-deep-research#7462 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cathrynlavery/diagram-design#441 ·
Maintainers usually reply within 2 days
-
[Cleanup] Include the public header in work_split.cppPossibly taken @blozano-tt claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tenstorrent/tt-metal#60850 ·
Maintainers usually reply within 1 day