-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve meson build #31
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like the split of large meson.build into separate files!
I left a few comments mostly regarding file naming and a few questions.
@@ -1,4 +1,4 @@ | |||
<img align="left" width="64" height="64" src="https://raw.githubusercontent.com/starfish-app/starfish/main/data/icons/64.svg"> | |||
<img align="left" width="64" height="64" src="https://raw.githubusercontent.com/starfish-app/starfish/main/data/icons/64/hr.from.josipantolis.starfish.svg"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer not to have project name repeated in too many places, such as icon file names, etc.
Ideally it would only be defined in the project
function call on top of the root meson.build file.
Individual files can be renamed in calls to install_data
function. That approach allows for:
- Shorter file names without repetition. This just makes working with them more comfortable.
- Easier rename of the project in the future. Either if someone wanted to maintain a fork long term, or just easily install 2 versions on the same system.
Admittedly, I haven't followed this rule in all the places myself, but I plan to clean those up over time.
@@ -89,7 +89,7 @@ flatpak run hr.from.josipantolis.starfish | |||
|
|||
## License | |||
|
|||
[GNU GPLv3](COPYING) | |||
[GNU GPLv3](LICENSE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think COPYING is the standard / recommended name for the file containing the full GPL license text.
I'd like to stay aligned with that standard.
'test/Core/GeminiBodyTest.vala', | ||
'test/Core/UriTest.vala' | ||
# Compiling resources | ||
gresource = gnome.compile_resources ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to move this into data/meson.build
as well?
I made a few improvements to your app structure. These are not breaking changes. Let me know if you have any questions 😄
Changelog:
COPYING
toLICENSE
meson.build
filesmeson.build
filespost_install.py
scriptI would be happy to add French translation once this will have been reviewed
I tried to build and run the app locally using both meson and flatpak and I had no issues