USER FORUM
(you are viewing a thread; or go back to list of threads)
QT version on Linux (available to build from source) (by Paul)
For those wanting a QT version of Solvespace on Linux, we have merged the code into the main repository. The build instructions have been updated to include this new option.
Aside from the look, this version allows docking the text window inside the main graphical window. That's a huge bonus for users on Wayland because most the DEs currently do a poor job of placing the 2 windows relative to each other.
Aside from the look, this version allows docking the text window inside the main graphical window. That's a huge bonus for users on Wayland because most the DEs currently do a poor job of placing the 2 windows relative to each other.
Build for Ubuntu (by S Groesz)
I'm not clear on the build instructions for building for debuntu. The line added to the readme in the update identifies gtkmm30-devel, which is only listed for RedHat. The equivalent for Debuntu would be libgtkmm-3.0-dev, I would assume. I will try it out on my own to resolve this. I will need to try without any changes first and see if the -qt gets built properly or not, then try a few other changes to get it to work. I would also have thought that maybe it's not compatible or ready for debuntu yet, but I see someone has created a .deb with the qt build so, I at least know it's possible. Also will need to see if the -DUSE_QT_GUI=ON works for building on debuntu, which I assume it will.
I am knowledgeable with compiling from source on Linux (been doing it for years, including customizing the Kernel in some cases) but I am by no means an expert. My expertise lies mostly in mashing the keyboard until I achieve my desired results :p
You will need the usual build tools, CMake, zlib, libpng, cairo, freetype. To
build the GUI, you will need fontconfig, gtkmm 3.0 (version 3.16 or later),
pangomm 1.4, OpenGL and OpenGL GLU, and optionally, the Space Navigator client
library. On a Debian derivative (e.g. Ubuntu) these can be installed with:
```sh
sudo apt install git build-essential cmake zlib1g-dev libpng-dev \
libcairo2-dev libfreetype6-dev libjson-c-dev \
libfontconfig1-dev libgtkmm-3.0-dev libpangomm-1.4-dev \
libgl-dev libglu-dev libspnav-dev
```
On a RedHat derivative (e.g. Fedora) the dependencies can be installed with:
```sh
sudo dnf install git gcc-c++ cmake zlib-devel libpng-devel \
cairo-devel freetype-devel json-c-devel \
fontconfig-devel gtkmm30-devel pangomm-devel \
mesa-libGL-devel mesa-libGLU-devel libspnav-devel
```
To build the QT version replace `gtkmm30-devel` with `qt6-qtbase-devel` and add `-DUSE_QT_GUI=ON` to the cmake step below
Before building, [check out the project and the necessary submodules](#via-source-code).
After that, build SolveSpace as following:
```sh
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -DENABLE_OPENMP=ON
make
I am knowledgeable with compiling from source on Linux (been doing it for years, including customizing the Kernel in some cases) but I am by no means an expert. My expertise lies mostly in mashing the keyboard until I achieve my desired results :p
You will need the usual build tools, CMake, zlib, libpng, cairo, freetype. To
build the GUI, you will need fontconfig, gtkmm 3.0 (version 3.16 or later),
pangomm 1.4, OpenGL and OpenGL GLU, and optionally, the Space Navigator client
library. On a Debian derivative (e.g. Ubuntu) these can be installed with:
```sh
sudo apt install git build-essential cmake zlib1g-dev libpng-dev \
libcairo2-dev libfreetype6-dev libjson-c-dev \
libfontconfig1-dev libgtkmm-3.0-dev libpangomm-1.4-dev \
libgl-dev libglu-dev libspnav-dev
```
On a RedHat derivative (e.g. Fedora) the dependencies can be installed with:
```sh
sudo dnf install git gcc-c++ cmake zlib-devel libpng-devel \
cairo-devel freetype-devel json-c-devel \
fontconfig-devel gtkmm30-devel pangomm-devel \
mesa-libGL-devel mesa-libGLU-devel libspnav-devel
```
To build the QT version replace `gtkmm30-devel` with `qt6-qtbase-devel` and add `-DUSE_QT_GUI=ON` to the cmake step below
Before building, [check out the project and the necessary submodules](#via-source-code).
After that, build SolveSpace as following:
```sh
mkdir build
cd build
cmake .. -DCMAKE_BUILD_TYPE=Release -DENABLE_OPENMP=ON
make
(no subject) (by Paul)
Someone has submitted a PR to clarify those build instructions. The bottom line is that you need to have the correct QT package installed and you have to pass another flag to cmake. The updated instructions are more clear on the details.
(no subject) (by S Groesz)
That was me. Thanks for accepting my proposed changes.
(no subject) (by Jason)
Nice! Just compiled it and trying it out, works well, but I am noticing some ghosting when I zoom in or out.
(no subject) (by Paul)
Ghosting? Sounds like a monitor issue. There are no visual effects in Solvespace. The only thing I can think of that might be confused for a visual artifact is the default contour fill for 2d sketches. Under "Configuration" this is enabled by the "check sketch for closed contours" checkbox. You'll need to move something for it to update the display.
The default fill color is very faint on some monitors. The fill color can be changed in "line styles" as s009-def-contour-fill. I'm thinking about changing the default to 0.1, 0.0, 0.3 for the next release.
The default fill color is very faint on some monitors. The fill color can be changed in "line styles" as s009-def-contour-fill. I'm thinking about changing the default to 0.1, 0.0, 0.3 for the next release.
Ghosting (by Jason)
Hi, I take your point, this was on an iMac 2013 running Debian 13 KDE. So I tried it on an MS Surface 7 Pro, also running Debian 13 but Gnome and it is also present there. Please see a screenshot attached from the iMac after zooming in, should I start a bug report or is this a Wayland problem? Thx
Ghosting (by Jason)
It does seem to be a Wayland issue, I just logged in under X and the ghosting was not there
(no subject) (by ruevs)
Jason, What do you mean by "ghosting"? Your screen shot looks perfectly fine to me.
(no subject) (by Jason)
Hi, the red arrow is pointing from the current zoom level to the previous zoom level which is still visible, is that not called ghosting?
(no subject) (by Paul)
It depends on what screen you view the file. The ghost is faint and not visible on my phone. But it is visible on my desktop monitor. Since we are viewing a screenshot we know its real and not OPs monitor.
Once the ghost is visible try pressing the space bar and see if it goes away.
Once the ghost is visible try pressing the space bar and see if it goes away.
(no subject) (by ruevs)
Aha! I see it - had to turn the brightness up... Interesting...
Post a reply to this comment: