Sorry for the loooong delay, been very busy these last weeks, could not find the time to just upload and post it.
So, here it is : julienblanc/Subsoniq: Fork of https://github.com/Znurre/Subsoniq , to compile with latest SFOS versions. - Codeberg.org . That’s basically Znurr’s work, with only a few modifications to compile it with latest SDK. I planned to also share compiled rpms, but obviously won’t have time for that yet.
Do you want me to create a package in Chum:testing? I can do that immediately as I already have credentials there, then SFOS users could install it but with a very clear “use at own risk” label.
Chum’s OBS can compile it. Worth a try.
Which architectures/SFOS versions are most likely to compile/work?
Sorry if I raised false hope, I was indeed writing out my arse.
That wasn’t directed at you, just at my own comment, where I wrote some nonsense. In my defense, I’ve already implemented the usage of the encrypted storage for passwords, so only the application will be able to use it (and will re-check if it can after restart). After some testing, I think we will be able to release it to Open Repos.
if it is about submusic – I’d say it’s worth cleaning up the backlog a bit before renaming the package (which is needed to pass SFOS requirements for RPM installed from repository services), but the final decision must be made by @ScaleneVirus288
p.s. maybe it’s worth creating a separate thread for submusic to not mess everything in a single pile
Sure, if you can package it, go ahead ! It’s not my work, it’s Znurr’s, and i think it’s in an abandoned state. I merely adapted it so that it can compile, and checked it works (i use it, but very occasionally).
Um, I was replying to @JulienBlanc, using Openrepos or Chum is a dev’s preference, I’m not implying that Openrepos is inferior or anything.
BTW if you’re talking about renaming the package to harbour-…, that is not a requirement with Chum.
Thanks again, looking forward to new releases (wink wink, nudge nudge)!
I just tried with this source but it seems the submodule QJsonSerializer refers to a commit that does not exist?
If you say you managed to compile it just last week, I have no idea what’s going on here.
This is what trying to build it returns:
Handling Subsoniq
fetch: Fetching all references…
Already on ‘master’
Your branch is up to date with ‘origin/master’.
HEAD is now at 273c12b Update for compilation on modern SFOS
fetch: Fetching all references…
fatal: remote error: upload-pack: not our ref 29496527e67e97d1f3aadd2b5f69e6f54611bcf9
Fetched in submodule path ‘QJsonSerializer’, but it did not contain 29496527e67e97d1f3aadd2b5f69e6f54611bcf9. Direct fetching of that commit failed.
ERROR: Something went wrong handling submodule QJsonSerializer fromhttps://github.com/Znurre/QJsonSerializer.git(submodule update return code 1).
Should be fixed. I forgot to also change the submodule uri, it now points to my fork of QJsonSerializer, which is needed as well to compile.
Nice. Unfortunately the build for aarch64 fails:
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.9Jg7Sq (%build)
Messages from sb2:
(WARNING) qmake[3321/-143505600] Path not found for FD -100, for __fxstatat64()
# exit 1 (1)
It seems to be coming from the subpackage, but beyond that I have no idea.
Looks that a dependency was missing in the spec file. I’ve pushed a fix, this one should be ok. I don’t remember how to do a build on a fresh sdk, without reinstalling it (i’m pretty sure there’s a way, just can’t remember which).
I think I figured out my repos now, so I can finally reply.
Looks that a dependency was missing in the spec file.
Which spec file? Subsoniq’s or QJsonSerializer’s? I notice that the latter doesn’t even have a .spec file; maybe this needs to exist in the /rpm directory? pretty sure that’s the case for main code repos.
Subsoniq still fails to build (you can click on the red ‘failed’ for full logs), afaics with the same message.
Searching ‘error’ in the log for aarch64, I get:
Project ERROR: Unknown module(s) in QT: multimedia [dbus]
mentioned on line 653 and 658, referencing Makefile lines 45 and 70.
Later (line 669)
make[1]: Leaving directory ‘/home/abuild/rpmbuild/BUILD/harbour-subsoniq-0.1+master.20260424055542.5b719f0/QJsonSerializer’
error: Bad exit status from /var/tmp/rpm-tmp.RlUY0b (%build)
I hope that helps.
The log file sucks because the first half seems to be related only to booting up the VM. I think.
Good catch, need to add it in Subsoniq’s spec file as well. Will do that tomorrow.
Done (with a few others as well). I hope it’s ok now.
Still fails, this time at (%install) instead of (%build).
Grepping for ‘error’:
_log:971: [ 90s] collect2: error: ld returned 1 exit status
_log:972: [ 90s] make[1]: *** [: ../QJsonSerializer/lib/QJsonSerializer] Error 1
_log:974: [ 90s] make: *** [Makefile:82: sub-sailfish-install_subtargets] Error 2
_log:975: [ 90s] error: Bad exit status from /var/tmp/rpm-tmp.Kz9rbb (%install)
_log:978: [ 90s] RPM build errors:
Looks like it tries to compile QJsonSerializer, but it should not. There are link errors, but they refer to libstdc++ or QtCore, which means there’s a problem with compile options.
What is the build process in OBS ? With the fixes made, a simple sfdk package should now work, even on a clean sdk.
It should not? I’m confused. The repo looks very much like to-be-compiled C++ software.
Or do you mean it shouldn’t try to compile QJsonSerializer separately? It should just pull the submodule into the main repo as is, and everything gets compiled together as one?
Apparently the SDK does it that way or has an option to do so? Could you look through the config for this project if something jumps out?
In OBS, I guess I’d need to edit the _service file (some documentation).
The second. It should only try to compile the main repo, not the submodule. But i don’t see why it would, there’s nothing in the service file that tells it to.
Need to investigate this further. Will try to start with a clean sdk.
gcc ../QJsonSerializer/lib/QJsonSerializer.o -o ../QJsonSerializer/lib/QJsonSerializer
I don’t get a clue where that line comes from. It does not try to do that when compiling with sfdk, looks like obs uses rpmbuild, i have no experience with it.
Either someone more knowledgeable that me can have a look, or i’ll need to switch to cmake for both projects (my qmake is pretty bad as well).
I pushed a new version, which uses cmake to build. It builds fine with sfdk, can you try with obs ?
Yay, it compiles and - it works!
The rpm is currently private, but I uploaded it here.
I’m requesting this to go to Chum Testing straight away.
Hi, i was reviewing the chum request.
You need to set the license. Also, you could drop the yaml and just maintain the .spec. And, if you want to display nicely in chum gui, you need to add the chum metadata.