tauri-apps / tauri-apps/tauri-docs
Add copy-pastable `.gitlab-ci.yml` for cross building and bundling to building documentation
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
Motivation
There is a way to cross build and bundle Tauri applications, but it's limited to GitHub.
(See documentation/guide here)
However, a lot of (self-host) people and companies use GitLab, therefore it would be great to have a copy-pastable
configuration (.gitlab-ci.yml) for each target OS.
Ideally all available bundle types should be built.
Issue
Cross building is not easy, and one has to read through quite some documentation and try a lot
of things to get GitLab pipelines running.
I was searching for a Tauri project hosted on GitLab, but was not able to find one which also
has cross building and bundling in there pipelines.
I tried writing a GitLab pipeline, which somehow even got a Windows .exe as an GitLab pipeline artifact, but sadly it complains about a missing .dll file.
Considerations
A default pipeline would be quite inefficient, as packages have to be reinstalled or even compiled every time (on top of the rust container).
A custom container would be better, but is an increadible effort, which is why I would consider it out of scope. In a similiar matter, caching would have to be configured.
However, both problems could be considerd to be solved by the user.
Possible solution
Reconstructing the commands taken in the GitHub actions, putting those into a valid .gitlab-ci.yml (or n yaml files, for each target OS) and reference it on documentation: Cross-Platform Compilation
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 with the documentation/guide for Cross-Platform Compilation and the existing GitHub Actions commands it describes. Map those commands into copy-pastable .gitlab-ci.yml configuration for each target OS, including the available bundle types. Done means the documentation provides valid GitLab pipeline examples that produce the intended artifacts without requiring an undocumented custom container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, gitlab, rust
- Domain
- build-system, ci-cd, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100