Building from sources

[gsal]

Do I need to build from sources?

Oh, I should mentioned right away that I don't know how to use cmake.

It looks like my OS is a bit old and, after simply doing pip install dearpygui and attempting to run the program, it complains about not finding some version of GLIBC.

So, I thought I would build from sources; but, that immediately comes back with the following error:

mkdir build
cd build
cmake ..
.
.
.
CMake Error at Dependencies/CMakeLists.txt:13 (add_subdirectory):
  The source directory
    /<myhome>/Downloads/DearPyGui-1.3.1/Dependencies/glfw
  does not contain a CMakeLists.txt file.

Any idea what should be there? I tried put some simple file in there, but then I run into another error.

[hoffstadt]

Hi! This occurs if the submodules are not pulled in. Make sure you used git clone --recursive https://github.com/hoffstadt/DearPyGui. Let me know what other errors arise!

[gsal]

I see. All I had done before was use the green Code button to download the zip file. Actually cloning with recursive certainly populated the sub-directories; thank you for that.

...here is the next error message :-(

[  7%] Building C object Dependencies/glfw/src/CMakeFiles/glfw.dir/linux_joystick.c.o
[  8%] Linking C static library libglfw3.a
[  8%] Built target glfw
[  9%] Building CXX object ImguiTesting/CMakeFiles/PureImgui.dir/main.cpp.o
In file included from /home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp:8:0:
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/src/mvLinuxWindow.h:10:22: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
     bool m_running = true;
                      ^
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/src/mvLinuxWindow.h:24:57: warning: non-static data member initializers only available with -std=c++11 or -std=gnu++11 [enabled by default]
     float m_clear_color[4] = {0.45f, 0.55f, 0.60f, 1.00f};
                                                         ^
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/src/mvLinuxWindow.h:24:57: warning: extended initializer lists only available with -std=c++11 or -std=gnu++11 [enabled by default]
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp: In function ‘int main()’:
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp:18:5: warning: ‘auto’ changes meaning in C++11; please remove it [-Wc++0x-compat]
     auto window = new mvWindowClass();
     ^
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp:18:10: error: ‘window’ does not name a type
     auto window = new mvWindowClass();
          ^
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp:37:5: error: ‘window’ was not declared in this scope
     window->show();
     ^
gmake[2]: *** [ImguiTesting/CMakeFiles/PureImgui.dir/main.cpp.o] Error 1
gmake[1]: *** [ImguiTesting/CMakeFiles/PureImgui.dir/all] Error 2
gmake: *** [all] Error 2

[gsal]

Switched from system GCC 4.8.5, to my GCC 10.3.0 ....error above went away, a new one came up:

[ 14%] Building CXX object ImguiTesting/CMakeFiles/PureImgui.dir/__/Dependencies/imgui/backends/imgui_impl_glfw.cpp.o
[ 14%] Building CXX object ImguiTesting/CMakeFiles/PureImgui.dir/__/Dependencies/imgui/backends/imgui_impl_opengl3.cpp.o
[ 15%] Building C object ImguiTesting/CMakeFiles/PureImgui.dir/__/Dependencies/imgui/examples/libs/gl3w/GL/gl3w.c.o
[ 15%] Linking CXX executable PureImgui
/usw/spgtools/binutils/2.36.1/centos7/bin/ld: CMakeFiles/PureImgui.dir/main.cpp.o: in function `main':
/home/salazag/Downloads/DearPyGui/DearPyGui/ImguiTesting/main.cpp:18: undefined reference to `operator delete(void*, unsigned long)'
collect2: error: ld returned 1 exit status
make[2]: *** [ImguiTesting/PureImgui] Error 1
make[1]: *** [ImguiTesting/CMakeFiles/PureImgui.dir/all] Error 2
make: *** [all] Error 2

[gsal]

Anybody?

[hoffstadt]

Try again! We removed PureImGui.

[gsal]

Trying...

[ 12%] Building C object Dependencies/glfw/src/CMakeFiles/glfw.dir/linux_joystick.c.o
[ 13%] Linking C static library libglfw3.a
[ 13%] Built target glfw
[ 14%] Building CXX object DearPyGui/CMakeFiles/coreemb.dir/src/core/mvContext.cpp.o
In file included from /home/salazag/Downloads/DearPyGui/DearPyGui/src/core/mvContext.h:19:0,
                 from /home/salazag/Downloads/DearPyGui/DearPyGui/src/core/mvContext.cpp:1:
/home/salazag/Downloads/DearPyGui/DearPyGui/../Dependencies/cpython/Include/Python.h:8:22: fatal error: pyconfig.h: No such file or directory
 #include "pyconfig.h"
                      ^
compilation terminated.
make[2]: *** [DearPyGui/CMakeFiles/coreemb.dir/src/core/mvContext.cpp.o] Error 1
make[1]: *** [DearPyGui/CMakeFiles/coreemb.dir/all] Error 2
make: *** [all] Error 2
$ [[master]]  /home/salazag/Downloads/DearPyGui/build
..
$ [[master]]  /home/salazag/Downloads/DearPyGui
find . -name pyconfig.h -type f 
./Dependencies/cpython/PC/pyconfig.h

[hoffstadt]

Sorry for the late response. Is it essentially running completely headless without a monitor?

[gsal]

Hi...again.

I kind of gave up on DearPyGui given my current Linux environment and the above difficulties; I may pick it back up when possible.

I gained access to a development Linux box running on Rocky 8 and everything works fine, there; but, IT is busy and we are not getting Rocky 8 until next year.

Regarding your questions, I don't quite get what you mean; I mean, sure, the server is probably headless and the rendering is done on the monitors of the DCV clients. Other than that, I don't know/remember deeper technical details on whether the DCV client uses GPUs or alternatives like Mesa for graphics rendering; I know this much....we use DCV clients for a bunch of things including working with software that does 3D modeling, etc and everything seems to work just fine.

[gsal]

Oh, so, one more thing.

Don't know what DearPyQGui software/hardware requirements are, but now with clouds (AWS, Azure) in place, I am wondering and would like to know if DearPyGui is going to be able to work in a cloud-based manner or not:
do you know this now?
have you considered it?

[hoffstadt]

We have a few ideas but we think they will need to wait until DPG 2.0 (which we started on already).

[gsal]

Nice, looking forward to that.

[abellgithub]

Why are we building our own cpython? So confused.