https://github.com/pop-os/popsicle
Multiple USB File Flasher
https://github.com/pop-os/popsicle
Last synced: 8 days ago
JSON representation
Multiple USB File Flasher
- Host: GitHub
- URL: https://github.com/pop-os/popsicle
- Owner: pop-os
- License: mit
- Created: 2017-10-03T20:12:37.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2025-04-08T16:07:15.000Z (13 days ago)
- Last Synced: 2025-04-14T01:57:38.862Z (8 days ago)
- Language: Rust
- Homepage:
- Size: 1.39 MB
- Stars: 690
- Watchers: 32
- Forks: 83
- Open Issues: 29
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome-rust - pop-os/popsicle
- fucking-Awesome-Linux-Software - .
## Build Dependencies
If building the GTK front end, you will be required to install the development dependencies for GTK and D-Bus, usually named `libgtk-3-dev` and `libdbus-1-dev`, respectively. No other dependencies are required to build the CLI or GTK front ends, besides Rust's `cargo` utility.
For those who need to vendor Cargo's crate dependencies which are fetched from [Crates.io](https://crates.io/), you will need to install [cargo-vendor](https://github.com/alexcrichton/cargo-vendor), and then run `make vendor`.
## Installation Instructions
A makefile is included for simply building and installing all required files into the system. You may either build both the CLI and GTK workspace, just the CLI workspace, or just the GTK workspace.
- `make cli && sudo make install-cli` will build and install just the CLI workspace
- `make gtk && sudo make install-gtk` will build and install just the GTK workspace
- `make && sudo make install` will build and install both the CLI and GTK workspaces## Screenshots
### Image Selection

### Device Selection

The list will also dynamically refresh as devices are added and removed

### Device Flashing

### Summary

## Translators
Translators are welcome to submit translations directly as a pull request to this project. It is generally expected that your pull requests will contain a single commit for each language that was added or improved, using a syntax like so:
```
i18n(eo): Add Esperanto language support
```Translation files can be found [here](./i18n/). We are using [Project Fluent](https://projectfluent.org) for our translations, which should be easier than working with gettext.