Getting green ticks on the SPI build matrix #6
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, it's great to see this package on swift.org but I noticed that we're currently showing all grey boxes over on the SPI compatibility matrix:
We currently don't support adding OS level dependencies for build on Apple platforms but our Linux builders are a bit more flexible. I've tried running a build locally with the dependencies set up but I'm getting build errors:
Here are the steps to reproduce:
It looks like
libadwaita-1-devisn't the correct dependency. Do you know what dev package needs to be installed on Ubuntu?Thanks for looking into this!
I think it is
libadwaita-1-dev, but probably, the Ubuntu version is not yet on the latest version? This package requires Libadwaita 1.5 (it is normally used inside a Flatpak, and Homebrew is already on version 1.5). The latest version seems to be Beta on Ubuntu packages.Oh, I see, thanks for checking that. Is there a way to get the beta package on jammy?
The alternative would be to use a
noblebase image but there isn't one yet with Swift on it, so it'd be a whole different thing to get that set up 😕@finestructure I'd like to move to DocC for the documentation and host it on the SPI, since I like to have the "Reference documentation" and articles/tutorials combined in one service, and as SPI offers that amazing, super simple approach to hosting it. I wanted to ask whether, as soon as we can fix the compatibility matrix problem, we can apply the same solution to the documentation generator? I don't know whether that is a good approach, but Homebrew is very fast with updating to the newest versions of libadwaita (I also won't update this package faster than Homebrew). Maybe we can install via Homebrew?
@finestructure does it have to be Ubuntu? With e.g. Fedora 40 it's very simple (the Swift version is 5.8.1):
The doc generation runs as an additional phase right after building, so once builds work, doc gen is pretty much automatic.
We don't currently support installing dependencies with Homebrew but we may have that in place in a few weeks, if things go as planned.
The route with a linux base image is currently probably our best shot to get this working (and we support doc gen on Linux as well).
That would work in principle, yes, though it'd be a bit more complicated to set up than just extending our existing Linux base images.
Are there other Swift versions available on Fedora? As you can see from the linked repo we try to create base images for all supported Swift versions (5.7, 5.8, 5.9, 5.10), so it'd be good if that was possible.
@finestructure The downloads on the Swift website are probably the easiest way for using a specific version:
Ok, great, this seems to work. I've set up a new base image and will re-trigger builds once it's done generating the images.
Well, actually it'll require a
.spi.ymlchange, PR open.Builds retriggered and passing now:
BTW, note that the documentation link is broken. I believe it's because the ref in
.spi.ymlisn't a proper https link:(This should be fixed if you switch over the doc hosting as discussed.)
Nice! It would be cool if you could inform me when installing dependencies from Homebrew is possible to make the macOS build work as well (that's why I reopened this issue).
About the docs: Should the link be
https://aparokshaui.github.io/adwaita-swift/documentation/adwaita/work? I'm happy with the GitHub actions approach I'm using now.I think it should, see https://swiftpackageindex.com/swiftpackageindex/spimanifest/1.4.1/documentation/spimanifest/commonusecases#Configure-a-documentation-URL-for-existing-documentation for details!