[New build system] CPack variables as cache variables

Open
#201 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cmake
Domain
build-system

Research direction

Start by locating the new build system's CPack configuration and identify which CPack variables are currently fixed rather than exposed as cache variables. Compare the handling of CPACK_PACKAGE_INSTALL_DIRECTORY with the other CPack settings, then define a clear set of configurable variables and verify that packaging configuration uses them.

Written by the indexing model from the issue text.

Description

project: hipblas-common

[Migrated from original issue] ROCm/hipBLAS-common#20

Original issue author: @ellosel

Some of the CPack variables in the new build system should probably be configurable cache variables such as CPACK_PACKAGE_INSTALL_DIRECTORY .

Dominant language
Assembly
Stars
431
Forks
407
Avg merge
3d 7h
Merged PRs (30d)
441

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ROCm/rocm-libraries

All issues in ROCm/rocm-libraries

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.