| 27 Sep 2025 |
 K900 | But you can remove it and it'll probably blow up | 20:52:34 |
 outfoxxed | alright
I havent tried building any kde packages yet because they all pull in qtwebengine somehow | 20:52:54 |
| K900 | And then you can see how it blows up | 20:53:01 |
| K900 | I assume the secrets are in the dev output, at least | 20:53:02 |
| K900 | Something something unprefixed pkg-config something | 20:53:11 |
| K900 | You can break that chain at PySide | 20:53:20 |
| K900 | For many things at least | 20:53:40 |
| outfoxxed | ah does pyside pull in literally everything | 20:53:42 |
| K900 | OK seriously bedge | 20:53:45 |
| K900 | Today is a day | 20:53:48 |
| K900 | Was a day | 20:53:51 |
| K900 | Not literally everything but most things yes | 20:54:00 |
| outfoxxed | thanks | 20:54:07 |
| K900 | And technically most KDE things don't need webengine | 20:54:38 |
| K900 | But we can't give them a custom PySide either because python flat names pace | 20:54:38 |
| outfoxxed | could we have a pysideWithModules or something | 20:55:00 |
| outfoxxed | assuming pyside itself doesnt take forever to compile for each one | 20:55:12 |
| K900 | No because it's defined at build time | 20:55:16 |
| K900 | Anyway | 20:55:19 |
| outfoxxed | later yeah | 20:55:24 |
| K900 | I really need sleep | 20:55:38 |
| K900 | Sorry I'm cutting myself off | 20:55:38 |
| outfoxxed | It seems like the host prefixes environment variable doesn't actually do what it says it does and unlinke QT_HOST_PATH doesn't add itself to the tool scanning list. I think the best solution here is just to add a patch to their cmake files when cross compiling, so we don't break anything new in a normal build, and cross doesn't work anyway so anything is an improvement | 23:21:49 |
| outfoxxed | list(PREPEND CMAKE_PREFIX_PATH "${_qt_additional_host_packages_prefix_paths}")
was it really so hard
| 23:21:58 |
| outfoxxed | * list(PREPEND CMAKE_PREFIX_PATH "${_qt_additional_host_packages_prefix_paths}")
was it really so hard
| 23:22:04 |
| outfoxxed | I personally prefer this to injecting _DIR variables into every package when cross compiling | 23:23:00 |
| 28 Sep 2025 |
| outfoxxed | 
Download image.png | 00:16:20 |
| outfoxxed | and we're green with all the _DIRs removed | 00:16:25 |
 rosssmyth | How are deps calculated w.r.t. splicing (i.e. what pkgset are they pulled from) when they are used strings? So for example if you write buildPhase = "echo '${lib.getExe foo}' >> buz.sh" or whatever, how is | 02:25:33 |
| rosssmyth | * How are deps calculated w.r.t. splicing (i.e. what pkgset are they pulled from) when they are used strings? So for example if you write buildPhase = "echo '${lib.getExe foo}' >> buz.sh" or whatever, how is the package set calculated? Or is it? Or is it just always nataiveBuildInputs or something? | 02:28:08 |
