-
TheCharlatanI've spent quite some time on the repro builds again and I'm pretty much stuck still in qt configuration hell. It's horrible.
-
dsc_TheCharlatan: ./configure of qt?
-
dsc_what version?
-
dsc_And which platform?
-
selstaQt 5.12 would be ok
-
dsc_5.12 is EOL in 1 year
-
dsc_anyway, I have a ./configure for 5.15
-
selstawe need Ubuntu 16.04 and macOS 10.12 support
-
selstaI also would like 5.15 with automatic high dpi scaling
-
TheCharlatanI'm going for 5.15
-
TheCharlatandsc_ can you share what you have somewhere?
-
TheCharlatanselsta what is prohibiting a 5.15 qt build running on 16.04?
-
selstaqt
-
selstaapparently? it is not included in supported platforms
-
TheCharlatanshould still run though, right?
-
selstaI don’t know.
-
TheCharlatanI'll guess I find out then.
-
dsc_TheCharlatan: sure!
-
dsc_(And yes, 5.15 is ubuntu 18.04 and up)
-
dsc_TheCharlatan: paste.centos.org/view/raw/13f9445a <== This requires 2 external files: kitware.asc (CMake authors, so we can `apt install` latest cmake (3.18.*) and `Qt5.15_LinuxPatch.json` which can be found here: paste.centos.org/view/raw/c1847671 (the qtbase git patch is paste.centos.org/view/raw/d6f367f2)
-
dsc_Please note however that it's doing `-no-opengl`, as my Qt application doesn't need it
-
dsc_And because you're using a fairly recent CMake you can do `find_package(Qt5 REQUIRED COMPONENTS Core Widgets Gui Network Svg Xml WebSockets)` inside CMakeLists.txt
-
dsc_in `target_link_libraries` you'd do `Qt5::Core Qt5::Widgets Qt5::Gui` etc. Also `target_compile_definitions` and `target_include_directories`.
-
dsc_for static builds you may additionally need to link against `Qt5::FontDatabaseSupport Qt5::QSvgIconPlugin Qt5::QSvgPlugin`
-
dsc_IIRC Qt devs commit straight into CMake - so the reason we have complicated cmake stuff regarding Qt is because for old version support (correct me if I'm wrong)
-
dsc_Latest Qt 5.15 + CMake 3.18 comes with cmake recipes that are useful
-
dsc_Actually, I think those cmake files can be found in `qtbase` anyway .. -DCMAKE_PREFIX_PATH will find them.
-
TheCharlatanthanks a lot. I'll see if one of those -skip 's might be helpful. AFAICT the problem I'm having is in a module we don't actually need.
-
dsc_Which one, and what is the error?
-
selsta.merges
-
xmr-pr3000 3029 3030 3032 3042 3043 3047 3052 3053 3054 3055 3056 3058 3059 3061 3062 3064