Introduction and first question :-)

mlm

Hello,

I am Michael and have a background in macOS/iOS/Swift (you probably can see a pattern here) development. That's probably also why I stumbled across the Aparoksha blog post on the swift.org site.

Currently I am exploring alternatives outside of the more traditional (I suppose) development environments - for various reasons - and Aparoksha/Adwaita appealed to me, because I still could use Swift (which I like) to explore a world which is entirely new to me.

The issue I am currently struggling the most with (and here we come to my first question), is that the build in Builder sometimes just fails without showing an apparent error in the log (see the log at the bottom for an example). Sometimes just building again makes it succeed. Sometimes doing an rm -rf ./build will do the trick. Sometimes it is entirely unclear what would solve the issue or, at least, show what the error is.

So I guess my question is, if there's a more reliable environment than Builder? Or maybe what's the best way to learn the underpinnings so I could track down the issues more easily? Or what would be the most bare bones way of development, so I could see what's actually happening? Just running swift build won´t work, because it's missing some of the environment that the build from Builder is setting, I suppose... Guess that are now actually three first questions ;-)

Despite of my issues with build/Builder I am impressed what's possible with Aparoksha and how I was able to apply my Swift/SwiftUI knowledge. So anything that helps me to continue that path is highly appreciated. It's been a fun journey so far, so let me conclude by saying thank you for the effort you put into Aparoksha and the surrounding infrastructure. I hope that some day I can give back by contributing to it somehow.

Cheers, Michael

warning: 'csqlite': ignoring declared target(s) 'CSQLite' in the system package warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: prohibited flag(s): -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -mfpmath=sse, -msse, -msse2, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread Building for debugging... [40/40] Linking Generation-tool Build of product 'Generation' complete! (2.22s) warning: 'sqlite.swift': found 1 file(s) which are unhandled; explicitly declare them as resources or exclude from the target /home/ml/Development/SecondAparoksha/.build/checkouts/SQLite.swift/Sources/SQLite/PrivacyInfo.xcprivacy warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: harfbuzz -> freetype2 -> harfbuzz warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: circular dependency detected while parsing libadwaita-1: freetype2 -> harfbuzz -> freetype2 warning: prohibited flag(s): -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -mfpmath=sse, -msse, -msse2, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread, -pthread Building for debugging... [4/119] Write swift-version--36E70F4A7E8509C9.txt

david-swift

Hello Michael,

Thank you for your interest!

mlm The issue I am currently struggling the most with (and here we come to my first question), is that the build in Builder sometimes just fails without showing an apparent error in the log (see the log at the bottom for an example). Sometimes just building again makes it succeed. Sometimes doing an rm -rf ./build will do the trick. Sometimes it is entirely unclear what would solve the issue or, at least, show what the error is.

I've never experienced this problem. I'm personally not on the stable, but the GNOME Nightly version of GNOME Builder, as autocompletion support for Swift 6 (and Swift file icons 🙂) are not yet available in the latest stable version. Don't think this is relevant though.

mlm So I guess my question is, if there's a more reliable environment than Builder?

The alternative is VS Code using the Flatpak extension (and Swift for language support). Don't think this helps as both use Flatpak Builder under the hood AFAIK.

mlm Or what would be the most bare bones way of development, so I could see what's actually happening?

Directly running Flatpak Builder.

mlm Just running swift build won´t work, because it's missing some of the environment that the build from Builder is setting, I suppose... Guess that are now actually three first questions ;-)

You could install libadwaita-devel (or something similar based on your distro) and then, swift build should work. However, this will only work if your distro offers the latest libadwaita version, which is why Flatpak is much more comfortable. Unfortunately, it is the only solution I could think of.

mlm Despite of my issues with build/Builder I am impressed what's possible with Aparoksha

Thank you so much for the kind words! Note that I would recommend accessing Adwaita for Swift directly right now (not through the Aparoksha package), as the latter is in a very early stage of development.

Maybe some information about your setup could help? Is your project based on the Adwaita template, and, if so, on the latest version? Is this problem also occurring with a minimal Swift executable?

I'm happy to help (if I can)!

Cheers,
David

mlm

Hello David,

thanks for the reply... and sorry for my late response ;-). It took me some time to get back to investigate.

So far it seems I am probably dealing with two problems:
#1 At one point the build fails without showing a proper error message in the log within Builder.
#2 There is no obvious way to recover from this situation, since even reverting to an older revision of the project (which build and ran fine) now does not compile anymore.

To me I think addressing issue #2 first is the reasonable way to start, since, if I am able to recover from the build problem by reverting back to the previous working version I should be able to figure our what changes are causing the build problem in the first place more easily.
So far deleting the .build folder and deleting the whole ~/Projects seem to be not enough - there must be something else where some "state" from previous builds is being kept. Do you know if there's something else I could "nuke" to get a clean slate? Since I saw the .dockerfile within the project, is there maybe a docker image wich has some "state"? (This probably shows how little I know about the actual Flatpak(?) build process ;-)

About your questions (I hope I do not miss any):

Starting point of my explorations are always based on the Adwaita Template.
I am using the TuxedoOS distro, but switched to the Gnome desktop environment. Bought a laptop from tuxedocomputers as a starting point for my Linux endeavors, since I wanted good hardware support right from the start.
Starting over from scratch (with the template) works, but only if I use a different directory name. That's also one of the reasons I think there must be some "leftover" from previous builds.

So, that's basically where I am currently at in my journey to Gnome/Adwaita programming with Swift :-)

Cheers, Michael

david-swift

Thanks for further investigating this!

mlm So how is this a step further? I now can compile straight from the command line (swift build, swift run, etc.). Which is great. So now I am using Sublime as an editor plus the command line. Works fine for now.

I will always update Adwaita for Swift soon after a new release of libadwaita (not before Homebrew offers the latest version), therefore, the latest version of GNOME is required to use it outside of a Flatpak (this is one of the reasons I prefer Flatpak).

mlm Strange enough, using Builder is not working at all: It just stops right at the start, without showing an error in the log. Compiling the same project from the command line, works just fine.

So it seems we could boil it down to a problem somehow related to Flatpak 🙂

mlm Since I saw the .dockerfile within the project, is there maybe a docker image wich has some "state"? (This probably shows how little I know about the actual Flatpak(?) build process ;-)

No, Flatpak doesn't use Docker. Docker is available as an alternative to Flatpak or natively running the app. There should not be state stored outside of the build folder, however, I've seen some strange files appearing in the directory where the Swift package manifest is sometimes (something with swiftdeps or names related to actual Swift files, in case I remember correctly - I can't reproduce this at the moment).

Cheers, David

mlm

Short update:
... I think I am on step further, not sure about the direction, though ;-):
I saw that I had an "older" version of Gnome (46) and figured that I try the latest release 47.4, to see it that makes any difference. So instead of fiddling around with my distro, I search for another one with a mostly plain Gnome 47. I settled for Manjaro.

So how is this a step further? I now can compile straight from the command line (swift build, swift run, etc.). Which is great. So now I am using Sublime as an editor plus the command line. Works fine for now.

Strange enough, using Builder is not working at all: It just stops right at the start, without showing an error in the log. Compiling the same project from the command line, works just fine.

Cheers, Michael