-
Notifications
You must be signed in to change notification settings - Fork 6
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
Move to meson #29
base: main
Are you sure you want to change the base?
Move to meson #29
Conversation
f1d5a82
to
bdf3cca
Compare
for now I don't install the .desktop and icons but the app build just fine |
it does require ahshabbir/ddcbc-api#2 to build |
I'm not sure how to handle the udev rules, I'm new to meson for now I haven't really looked at packaging, didn't figure out how deb generation works from reading the archwiki I got this for the pkgbuild :
|
Hey @liz-desartiges , My goals were shifting to meson, I see you have fixed out the C code a lot including the warnings during build, amazing work and sorry for my messy C code, I have pushed my implementation to and also the deb, rpm and maybe even arch packaging / push will need to be done, Let me know if you would prefer incorporating changes from my branch to yours and then we merge in your PR or if you would rather I incorporate changes from yout PR to mine, up to you :) |
I spent way more time than I though I would on this, I don't mind if you take this pr and incorporate your changes to it |
for deb I found that debhelper support meson I just haven't figured out how it works, and there is a rpm package for meson to build them, as for arch what I posted above should do the trick |
Cool, I guess I will update the arch pkgbuild once these changes are ready and merged, |
No I don't think so packaging is not really up my alley
|
Oops meson rpm module was removed : https://mesonbuild.com/Release-notes-for-0-62-0.html#removal-of-the-rpm-module |
The packaging rules for fedora and meson : https://docs.fedoraproject.org/en-US/packaging-guidelines/Meson/ |
@liz-desartiges can you separate the C code changes including breaking things into header files into a separate PR that I can merge in first and then handle the meson setup ? |
I did both at the same time because I didn't know how to handle things without the separation between header and the rest
-------- Original Message --------On 7/6/24 13:04, Swapnil Devesh wrote:
@liz-desartiges can you separate the C code changes including breaking things into header files into a separate PR that I can merge in first and then handle the meson setup ?
I will tackale the rpm and deb packaging through meson after the C code fixes and and meson config for building and installing the app is merged into main branch.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#29 (comment)",
"url": "#29 (comment)",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
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.
this file has mixed tabs and spaces
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.
same here
also move things that should be in header in header
fix #16