| 22 Dec 2025 |
 @bandithedoge:matrix.org | also you might want to update meta.mainProgram | 15:04:29 |
| @bandithedoge:matrix.org | 
Download image.png | 15:05:37 |
 magnetophon | You mean, with this, it builds?
I'm trying it now.
Thank you! | 15:13:59 |
| magnetophon | I don't understand.
What are they doing wrong, and how can you tell? | 15:15:09 |
| @bandithedoge:matrix.org | yeah that's the only change needed | 15:15:31 |
| @bandithedoge:matrix.org | by building those packages locally and looking at their file structure | 15:16:47 |
| @bandithedoge:matrix.org | let's say you run nix build nixpkgs#sord.dev && tree result-dev | 15:17:32 |
| @bandithedoge:matrix.org | you'll see something like this:
result-dev
├── include
│ └── sord-0
│ └── sord
│ ├── sord.h
│ └── sordmm.hpp
├── lib
│ └── pkgconfig
│ └── sord-0.pc
└── nix-support
└── propagated-build-inputs
| 15:17:56 |
| @bandithedoge:matrix.org | ardour's build scripts expect .../include/sord/sord.h but the package has .../include/sord-0/sord/sord.h | 15:18:33 |
| @bandithedoge:matrix.org | if you look at the sord-0.pc file you'll notice that it contains Cflags: -I${includedir}/sord-0, which is the correct path | 15:19:05 |
| @bandithedoge:matrix.org | but the build system ignores that | 15:19:30 |
| magnetophon | IIUC, that would mean they broke their build scripts going from ardour8 to 9?
Seems weird, no? | 15:19:53 |
| @bandithedoge:matrix.org | again, this is just a guess, i don't even know if they're actually using pkg-config for these libraries | 15:20:06 |
| @bandithedoge:matrix.org | either that or the packaging of these libraries changed | 15:20:34 |
| @bandithedoge:matrix.org | although that would also break ardour 8 | 15:20:40 |
| magnetophon | This looks like pkg-config output, no?
ardour> Checking for 'serd-0' >= 0.14.0 : yes | 15:21:12 |
| @bandithedoge:matrix.org | idk, i think you should tell them about this | 15:21:19 |
| @bandithedoge:matrix.org | probably | 15:21:24 |
| magnetophon | To be honest, I don't feel very confident in my abilities to explain the problem and to answer any follow-up questions.
Would you be willing to tell them?
https://tracker.ardour.org/ | 15:23:14 |
| magnetophon | I'll try building ardour8 next, just to double-check. | 15:24:29 |
| @bandithedoge:matrix.org | for all i know this could also be a waf issue as i can't see any notable changes in the build script, sord in nixpkgs or sord upstream | 15:43:40 |
| magnetophon | You mean a bug that should be reported to the makers of the waf build system? | 15:50:40 |
| magnetophon | In the meantime ardour9 finished building and I did a quick test run.
Now I'm building ardour8. | 15:51:33 |
| @bandithedoge:matrix.org | i don't know, they're using autowaf to find the packages but i'm not familiar with this tool at all https://github.com/Ardour/ardour/blob/adf0d528721917490080199ae80231b952c9c14e/libs/ardour/wscript#L316 | 15:55:49 |
| magnetophon | OK, so what do we do now?
Are you ok with reporting this to ardour, because I don't know what to tell them. | 15:59:04 |
| @bandithedoge:matrix.org | i don't think we have enough information for a proper bug report but you could mention it on their irc channel | 16:06:37 |
| magnetophon | Again: I'm not sure what to say and I won't be able t answer follow up questions.
Could you tell them? | 16:07:48 |
| @bandithedoge:matrix.org | i'm not at home atm, might do that later | 16:08:57 |
| magnetophon | Ardour 8 just finished building, so it seems the issue is just with ardour9 | 16:09:15 |
| magnetophon | Cool, thank you!!!! | 16:09:30 |
