nextcloud / nextcloud/client-building
With branding enabled the generated exe is still nextcloud.exe
Open
Nobody has claimed this yet.
- Dominant language
- Batchfile
- Stars
- 40
- Forks
- 41
- Avg merge
- 8h 2m
- Merged PRs (30d)
- 2
Description
I tried compiling the windows package with branding enabled, yet the output generated was nextcloud.exe and the build failed as the script was searching for brandedname.exe
Please advice how to created a branded theme
Contributor guide
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.
Research direction
Start by tracing the Windows package build scripts that handle branding and executable naming. Reproduce a branded build and compare the generated nextcloud.exe with the brandedname.exe the script expects. Done means the branded build completes and produces the consistently named executable; the issue does not identify a specific file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100