![]() ![]() You can probably do it later as a dual boot, but W10 has to go on first (due to driver issues). forget trying to install W7, it just wont have it. if youre going with the latest generation of mobo and processor. ![]() its ready to log in before the monitor has had a chance to warm up properly.lol. I went with DDR4 2600, GTX 1060 and a Samsung Evo M.2 SSD (ridiculously fast). "its good, very good!" the only downside being that you have to upgrade every other component of the system to remove any bottlenecks. If anyone is thinking about upgrading to a Ryzen based system, my message to you is. This should work on anyīit puzzled as to why it doesnt work in default mode though, as so far this new system has made total mincemeat out of everything I've thrown at it. Stellarium (MESA mode) Uses software rendering via MESA library. Stellarium (ANGLE mode) Uses Direct3D translation of the OpenGL rendering via ANGLE Im not usually one for reading instructions though.lol: It is recommended to use ``make makepatch'' when you need to generate a patch to ensure proper patch format.Just found the explanation of both modes. WARN: /usr/ports/x11-toolkits/qt5-gui/files/patch-src_plugins_platforms_xcb_qxcbconnection_xi2.cpp: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to generate a patch to ensure proper patch format. WARN: /usr/ports/x11-toolkits/qt5-gui/files/patch-src_platformsupport_input_evdevtouch_qevdevtouchhandler.cpp: patch was not generated using ``make makepatch''. WARN: Makefile: Makefile: extra item "BUILD_DEPENDS_armv6" placed in the LICENSE section.įATAL: Makefile: extra item "BUILD_DEPENDS_armv7" placed in the LICENSE section.įATAL: Makefile: extra item "LIB_DEPENDS" placed in the LICENSE section.įATAL: Makefile: extra item "RUN_DEPENDS" placed in the LICENSE section. To fix this casually, as a part of other commit? I am just not sure it is worse opening new bug for this or I can ask Makefiles in other qt5-* and also qt6-* ports? I also do not see any problems with dropping mesa-dri as runtimeīTW does anybody aware that 'portlint' is quite unhappy about qt5-gui/Makefile, libEGL prints warnings about missing swrast_dri.so but those are not critical (can be ignored). However, I couldn't reproduce bug 241485 - calibre works fine without mesa-dri. What could be the reason why Mesa does not respect the environment > variable anymore > (The Stellarium developer suggested it is a. > want to use pdf-to-something or something-to-pdf conversion applications on a headless systems or run GUI application remotely.ĭeskutils/calibre calls OpenGL directly (see USE_GL=egl gl), so it wouldn't be qt5-gui fault if mesa-dri is required. $ QT_QPA_PLATFORM=offscreen qterminal # works fine $ QT_QPA_PLATFORM=offscreen falkon # fails in qt5-webengine ![]() $ QT_QPA_PLATFORM=vnc qterminal # works fine Probably we just go to the unelegant way of setting the env var in the CLI parser, instead of forwarding some setting and then throw in the initialisation flag when we feel its the right place. $ QT_QPA_PLATFORM=vnc falkon # works fine I expect the Mesa CL switch will be ignored for the very same reason, and should likewise start when the env var is set accordingly. $ cage -d env -u DISPLAY qterminal # Wayland: works fine $ cage -d env -u DISPLAY falkon # Wayland: works fine $ cage -d env -u WAYLAND_DISPLAY qterminal # X11: works fine $ cage -d env -u WAYLAND_DISPLAY falkon # X11: works fine $ pkg install cage falkon-qtonly qterminal qt5-wayland X11, Wayland, remote (VNC), headless (offscreen) work fine without mesa-dri. > It was added because some users want to use qt5-gui in a scenario without Xorg stack: (In reply to Denis Polygalov from comment #4) ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |