This affects Windows harshly, I think Mac/Linux sort this themselves. This is quite annoying for personal users and rough for distribution. This seems to be about it running the bundled Qt, but QML trying to launch the extension from the system's Qt.
As labs is in a different directory, it need to be called somehow by qml or added to the user's path i guess... maybe literally just something like this in QML.jl to find it. (in the init?)
artifact_bin = joinpath(first(filter(d -> isdir(joinpath(d, "qml", "Qt", "labs", "platform")),
readdir(joinpath(first(Base.DEPOT_PATH), "artifacts"), join=true))), "bin")
sep = Sys.iswindows() ? ";" : ":"
ENV["PATH"] = artifact_bin * sep * ENV["PATH"]
Putting this in the REPL or at the top of the file I wish to run -- before using QML -- adds it to path for that terminal session, and fully fixes it afaik. Not tested on other platforms (dunno if needed)
This affects Windows harshly, I think Mac/Linux sort this themselves. This is quite annoying for personal users and rough for distribution. This seems to be about it running the bundled Qt, but QML trying to launch the extension from the system's Qt.
As labs is in a different directory, it need to be called somehow by qml or added to the user's path i guess... maybe literally just something like this in QML.jl to find it. (in the init?)
Putting this in the REPL or at the top of the file I wish to run -- before
using QML-- adds it to path for that terminal session, and fully fixes it afaik. Not tested on other platforms (dunno if needed)