41ba4e7d11* ## Summary I've implemented the fix for issue #4575. Here's what was changed: ### Changes Made **File: `v3/internal/commands/build_assets/linux/Taskfile.yml`** 1. Added `generate:dotdesktop` as a dependency to `build:native` task (line 45) 2. Added `generate:dotdesktop` as a dependency to `build:docker` task (line 63) This ensures that the `.desktop` file is generated during every Linux build (both native and Docker-based), not just during packaging operations. ### How it works - When running `wails build` or `wails dev` on Linux, the build process now automatically generates a `.desktop` file at `build/linux/<app-name>.desktop` - The `.desktop` file contains: - Application name - Executable path - Icon reference - Categories (defaulting to "Development") - This allows Linux desktop environments to properly display the application icon and metadata even during development ### Testing To test the changes: 1. Create a new Wails v3 project: `wails3 init -n testapp` 2. Build it: `cd testapp && wails3 build` 3. Verify the `.desktop` file exists: `cat build/linux/testapp.desktop` Would you like me to run a test or make any additional changes? * feat(linux): generate .desktop file during build (#4575) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build | ||
| frontend | ||
| .gitignore | ||
| go.mod | ||
| go.sum | ||
| greetservice.go | ||
| ios_runtime_events_ios.go | ||
| ios_runtime_events_stub.go | ||
| main.go | ||
| README.md | ||
| Taskfile.yml | ||
Welcome to Your New Wails3 Project!
Congratulations on generating your Wails3 application! This README will guide you through the next steps to get your project up and running.
Getting Started
-
Navigate to your project directory in the terminal.
-
To run your application in development mode, use the following command:
wails3 devThis will start your application and enable hot-reloading for both frontend and backend changes.
-
To build your application for production, use:
wails3 buildThis will create a production-ready executable in the
builddirectory.
Exploring Wails3 Features
Now that you have your project set up, it's time to explore the features that Wails3 offers:
-
Check out the examples: The best way to learn is by example. Visit the
examplesdirectory in thev3/examplesdirectory to see various sample applications. -
Run an example: To run any of the examples, navigate to the example's directory and use:
go run .Note: Some examples may be under development during the alpha phase.
-
Explore the documentation: Visit the Wails3 documentation for in-depth guides and API references.
-
Join the community: Have questions or want to share your progress? Join the Wails Discord or visit the Wails discussions on GitHub.
Project Structure
Take a moment to familiarize yourself with your project structure:
frontend/: Contains your frontend code (HTML, CSS, JavaScript/TypeScript)main.go: The entry point of your Go backendapp.go: Define your application structure and methods herewails.json: Configuration file for your Wails project
Next Steps
- Modify the frontend in the
frontend/directory to create your desired UI. - Add backend functionality in
main.go. - Use
wails3 devto see your changes in real-time. - When ready, build your application with
wails3 build.
Happy coding with Wails3! If you encounter any issues or have questions, don't hesitate to consult the documentation or reach out to the Wails community.