!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

217 Members
59 Servers

Load older messages


SenderMessageTime
5 Sep 2024
@outfoxxed:outfoxxed.meoutfoxxedalso consider08:02:36
@outfoxxed:outfoxxed.meoutfoxxedwait08:02:42
@outfoxxed:outfoxxed.meoutfoxxedi think ive got it08:02:45
@outfoxxed:outfoxxed.meoutfoxxedjust the presence of bare qml doesn't necessarily signify that there isn't any aot08:03:08
@outfoxxed:outfoxxed.meoutfoxxedwhen exporting qml modules it includes the bare qml in addition08:03:18
@outfoxxed:outfoxxed.meoutfoxxedyou'll have to actually check the build scripts to see how its included08:03:31
@k900:0upti.meK900Hm08:03:40
@k900:0upti.meK900Yeah I think that might be it08:03:48
@k900:0upti.meK900But then I wonder when we'd end up using those08:03:56
@outfoxxed:outfoxxed.meoutfoxxedwhen everything else somehow fails i think08:04:07
@outfoxxed:outfoxxed.meoutfoxxedlemme find the docs08:04:11
@outfoxxed:outfoxxed.meoutfoxxedhttps://doc.qt.io/qt-6/qt-add-qml-module.html#caching-compiled-qml-sources08:05:32
@outfoxxed:outfoxxed.meoutfoxxed

All .qml, .js, and .mjs files added to the module via the QML_FILES argument will be compiled to bytecode and cached directly in the backing target. This improves load-time performance of the module. The original uncompiled files are also stored in the backing target's resources, as these may still be needed in certain situations by the QML engine.

08:05:42
@outfoxxed:outfoxxed.meoutfoxxed *

All .qml, .js, and .mjs files added to the module via the QML_FILES argument will be compiled to bytecode and cached directly in the backing target. This improves load-time performance of the module. The original uncompiled files are also stored in the backing target's resources, as these may still be needed in certain situations by the QML engine.

08:05:48
@outfoxxed:outfoxxed.meoutfoxxedthis might be whats happening08:06:05
@k900:0upti.meK900Certain situations my ass08:06:11
@k900:0upti.meK900Very helpful08:06:15
@outfoxxed:outfoxxed.meoutfoxxedit sounds like the resource path only, but when I compiled a module from my own application it copied the source as well08:06:35
@outfoxxed:outfoxxed.meoutfoxxed * it sounds like the resource path only, but when I compiled a module from my own application it copied the source to the module dir as well08:06:43
@k900:0upti.meK900Here's a crazy idea08:07:27
@k900:0upti.meK900Just make it log very loudly when it's trying to cache bare QML08:07:41
@k900:0upti.meK900Along with the file path08:07:44
@k900:0upti.meK900And run that for a bit08:07:50
@k900:0upti.meK900And see when it actually gets hit, if ever08:07:57
@outfoxxed:outfoxxed.meoutfoxxeddoesn't even need to be loudly08:07:58
@outfoxxed:outfoxxed.meoutfoxxedjust needs a category08:08:01
@k900:0upti.meK900Well very loudly is helpful for finding it in the journal later08:08:09
@k900:0upti.meK900But otherwise yes08:08:14
@outfoxxed:outfoxxed.meoutfoxxedI don't run many qml applications or plasma so I can't really test that08:08:23
@outfoxxed:outfoxxed.meoutfoxxedsomeone with plasma would be the best choice08:08:29

Show newer messages


Back to Room ListRoom Version: 9