SFTtech / SFTtech/openage

Saving debug symbols

Open
#542 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: buildsystem improvement just do it
Dominant language
Python
Stars
14.4k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Description

Even the release build of libopenage should be probably producing a separate file with debug symbols. And this file should be installed/distributed with the rest of the binaries.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by tracing how the release build of libopenage is configured and how its binaries are installed and distributed. Done means the release build produces a separate debug-symbol file and that file is included with the distributed binaries.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.