Building for macOS? about x11basic HOT 4 OPEN

Hi gingerbredman,
Well, as far as I know, this has worked out before, but not completely.

Fist: I am wondering, because the apple branch is not there anymore.
So you should just do (starting from scratch)
git clone https://gitlab.com/kollo/X11Basic.git
cd X11Basic/src
./configure

And maybe you only want to try the make static, wich is the simplest build.

But first, after the configure, lets have a look at config.h which has been created by configure.

Especially look at the lines with:

#define HAVE_X11 1

from x11basic.

Looking at the other error: raw_keybord.c probably need to be modified.

try to make somethin like:

#ifndef __APPLE__
#include <linux/input.h>
#endif

or for convinience, delete the line #include <linux/input.h>
but other errors my show up. (for the moment, you can ignore warnings)

from x11basic.

Part of the issues I've run into is assuming that the linker is GNU ld/ELF: Apple's linker is not GNU ld, and it uses an executable format known as Mach.
For me, getting it to see headers and libraries in locations not in /usr/local is a pain, as the makefile doesn't seem to use LDFLAGS nor store CPPFLAGS.

For forkpty (without the forward declaration, it is an error on Apple Silicon), including util.h will fix the warning/error.

For the libxbasic shared library, there are a few areas that makes it a no-go on Darwin/macOS:

• linker flags -Wl,-Bsymbolic-functions and -Wl,-soname,libx11basic.so.1.28 don't translate to Mach flags (the second can be done with -install_name /usr/local/lib/libx11basic.1.28.dylib, more on this later).
• Shared libraries must end in ".dylib" for the linker to find them.
• Versioning must be done before the file extension.
• All symbols must be present at link time. prglen, ifilename, program, programbuffer, programbufferlen, and verbose need to be available, otherwise the library won't link. You can use -undefined dynamic_lookup, but I would not recommend it (You'd need the symbols to be external on the executables as well).
• For shared libraries installed in system locations, it is a good idea to set the install name to the prefix you installed it into.
• You can set -compatibility_version and -current_version on the library to make sure the applications fail early if the ABI changes significantly. More information about them can be found here.

from x11basic.

Seems this will not compile for Mac but is it possible to cross-compile the basic code for Mac using the Windows compiler as you can cross-compile on Windows for TomTom?

from x11basic.