Skip to content

Conversation

@PVermeer
Copy link
Contributor

@PVermeer PVermeer commented Oct 8, 2025

Description

As mentioned in PR #4304 this PR is meant to fix the libicu issue on debian. After some further investigation I noticed that

# This should automatically figure out dependencies, doesn't work with the current config
set(CPACK_DEBIAN_PACKAGE_SHLIBDEPS OFF)
is turned off because of config issue.

The only issue I could find right now is that it needs the file package on Debian-based distros. So adding the file to the build dependencies and running all the builds again fixes this issue (+ maybe some future issues).

If this is not acceptable I also have a fix specifically for libicu in b7b9e44 using the FindICU module.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

@codecov
Copy link

codecov bot commented Oct 8, 2025

Bundle Report

Bundle size has no change ✅

@codecov
Copy link

codecov bot commented Oct 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 11.98%. Comparing base (f52891d) to head (4f7cbb1).
⚠️ Report is 80 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff            @@
##           master    #4323    +/-   ##
========================================
  Coverage   11.98%   11.98%            
========================================
  Files          87       87            
  Lines       17572    17572            
  Branches     8076     8076            
========================================
  Hits         2106     2106            
+ Misses      14748    14569   -179     
- Partials      718      897   +179     
Flag Coverage Δ
Linux-AppImage 11.49% <ø> (ø)
Windows-AMD64 13.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 21 files with indirect coverage changes

@PVermeer PVermeer changed the title build(linux): enable deb package auto dependency list build(linux): enable cpack auto dependencies Oct 9, 2025
@PVermeer PVermeer force-pushed the build_linux_boost_libicu branch from f87f116 to 4f7cbb1 Compare October 9, 2025 12:42
@sonarqubecloud
Copy link

sonarqubecloud bot commented Oct 9, 2025

@ReenigneArcher ReenigneArcher merged commit ed7b78f into LizardByte:master Oct 9, 2025
47 checks passed
@PVermeer PVermeer deleted the build_linux_boost_libicu branch October 9, 2025 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants