Closed WebDrake closed 3 years ago
I'm a bit mystified as to why this PR is continuously failing, as it works fine when building locally. Something to do with Azure Pipelines, perhaps?
OK, seems that the failure here is due to how snapcraft treats environment variables created by Azure Pipelines: https://forum.snapcraft.io/t/cmake-plugin-failure-in-azure-pipelines/15825
The drop!
patches can therefore be abandoned, and we can return to this PR once snapcraft itself is fixed.
Rebased and retargeted on 1.20
and dropped all the unnecessary drop!
patches.
Closing as superseded by more recent changes.
snapcraft
now actively supports using the ninja cmake backend, so in general we do not need tooverride-build
to use this. This allows us to go back to regularconfigflags
settings for theldc-bootstrap
andllvm
parts, although we have to addsource-subdir
settings tollvm
because itsCMakeLists.txt
file is not in the source root.For the
ldc
part we can move all the cmake config flags and simplify theoverride-build
to just runsnapcraftctl build
followed by the search-and-replace dmd-testsuite workaround, and the call toctest
.We also need to make one small tweak to the
ldc
partconfigflags
: when settingDLIB_SUFFIX
, we need to use$$
to escape the$
for ninja, and drop the surrounding quotes in order to ensure the scripted segment is passed to cmake correctly by snapcraft.