Closed ghost closed 1 year ago
First of all, thanks for your interest in xtd ;-)
You are right that the use of wxWidgets
as a backend is not specified in the README.md of the project, as well as StackWalker
, StackTrace
, Win32 Api
, Cocoa
, Gtk+
, uuid
... which are libraries that xtd relies on.
However, the use of wxWidgets
is mentioned in the Download, install and uninstall page , in the External tools libraries and toolkits page, and many other places in the documentation.
If you look at the xtd roadmap, you will see that for xtd version 2.0.0, the Win32
backend will be added. For version 3.0.0 the Gtk4
backend will be added, etc...
wxWidgets is used as backend for the moment. But in the future other backend could be available, like Win32, Cocoa, Gtk, X11, Fltk, Qt, SDL2, ...
Later, it will be up to the user to choose the backend he wants (generic or not). Knowing that by default xtd will define the best backend depending on the target: Win32
for Windows, Cocoa
for macOS, Gtk
for linux with Gnome, Qt
for linux with KDE, ...
xtd, gives no access to the backend used. You cannot for example decide to use a xtd::forms::form and a wxButton from the wxWidgets
backend. The two controls are not compatible. You must use xtd::forms::button.
See my answer in issue #220.
Regards,
Gammasoft71
Oh this is unexpected. I admit I'm a bit surprised. Should this be stated clearly on README.md?
This is the output of cmake:
Update: yeah, it seems to depend on gnulib too:
fatal error: execinfo.h: No such file or directory