Skip to content

Conversation

mgallien
Copy link
Collaborator

@mgallien mgallien commented Jul 1, 2025

will enable having proper PDB files deployed when using craft to deploy client dependencies on Windows

@mgallien mgallien added this to the 3.17.0 milestone Jul 1, 2025
@mgallien mgallien force-pushed the bugfix/buildWithDebugSymbols branch 2 times, most recently from 56777f9 to 309aa00 Compare July 1, 2025 10:23
@mgallien mgallien requested a review from nilsding July 1, 2025 12:25
Copy link
Member

@nilsding nilsding Jul 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having another CraftMaster config in here is a bit too much duplication for my taste :D

I think we should add a new variable to the [Variables] section instead, reference it inside craftmaster.ini as ${Variables:MyVar}, and pass --variables MyVar=true to the CraftMaster command line parameters (before the -c flag, everything after that is passed to the Craft installation created by CraftMaster as-is).
This would allow us to easily decide to whether we want to create a build with debug symbols enabled or without.


Another less-flexible way which will only be useful for CI would be to only add config overrides that are relevant for CI here, i.e. replace this entire file with:

[windows-msvc2022_64-cl]
Packager/DownloadDebugSymbolsCache = False

and change the invocation of CraftMaster.py to include both the default craftmaster.ini and the new craftmaster-CI.ini:

# [...]
      CRAFT_MASTER_CONFIG: ${{ github.workspace }}\craftmaster.ini
      CRAFT_MASTER_CONFIG_CI: ${{ github.workspace }}\craftmaster-CI.ini
# [...]
        shell: pwsh
        run: |
          # [...]
          
          function craft() {
              python "${{ env.CRAFT_MASTER_LOCATION }}\CraftMaster.py" --config "${{ env.CRAFT_MASTER_CONFIG }}" --config-override "${{ env.CRAFT_MASTER_CONFIG_CI }}" --target ${{ env.CRAFT_TARGET }} -c $args
          # [...]

Copy link
Member

@nilsding nilsding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but I think we could even do something better instead

@mgallien mgallien modified the milestones: 3.17.0, 3.18.0 Jul 16, 2025
@nilsding nilsding force-pushed the bugfix/buildWithDebugSymbols branch from a54f0fe to 8acc2d0 Compare July 23, 2025 12:37
@nilsding nilsding requested a review from i2h3 as a code owner July 23, 2025 12:37
Copy link

@mgallien mgallien enabled auto-merge October 2, 2025 12:57
we have a limit in file size to 32 bits integer

this file is more than 2 GBs

Signed-off-by: Matthieu Gallien <[email protected]>
@mgallien mgallien force-pushed the bugfix/buildWithDebugSymbols branch from 605cbf4 to 28b0c34 Compare October 2, 2025 19:25
Copy link

github-actions bot commented Oct 2, 2025

Artifact containing the AppImage: nextcloud-appimage-pr-8423.zip

Digest: sha256:6489f503ecc5f11329b6a1fdcf4505a432af1e1cf4e9319da1436264f1886794

To test this change/fix you can download the above artifact file, unzip it, and run it.

Please make sure to quit your existing Nextcloud app and backup your data.

Copy link

sonarqubecloud bot commented Oct 2, 2025

@mgallien mgallien merged commit 7324b37 into master Oct 2, 2025
22 checks passed
@mgallien mgallien deleted the bugfix/buildWithDebugSymbols branch October 2, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants