TheAssassin

GCC 7 seems to support C++17 mostly, there's just one minor feature that'd require GCC 8. See https://gcc.gnu.org/projects/cxx-status.html. Ubuntu 18.04 (bionic) ships with GCC 7.4 by default, so I'd suggest...

Well, none of these platforms have a recent enough libstdc++ to support C++17, have they? Therefore, no, rather unlike.

An option is to use https://github.com/probonopd/uploadtool to auto-deploy built binaries to GitHub releases on every build.

@probonopd I already explained earlier that this software requires Ubuntu bionic, if the system native compiler shall be used.

That won't solve the issue. Then libc wise the ABI issues will be gone, but you'd have to bundle libstdc++ then to make things work on other systems. I disagree...

> If it works on xenial and newer, it can pass the tests... give me a second. Well, it's up to @aardappel whether to merge weird workarounds that are guaranteed...

I see, thanks for the clarification. Using `argv[0]` doesn't cut it then, I guess. The AppImage runtime uses `execv()` to run apps once the initialization is done. In some other...

Built a MWE for testing. ```c #include int main(int argc, char** argv) { printf("%s\n", argv[0]); return 0; } ``` [test-x86_64.AppImage.zip](https://github.com/aardappel/treesheets/files/3581900/test-x86_64.AppImage.zip) Output: ```sh > ./test-x86_64.AppImage /tmp/test-x86_64.AppImage ``` Making apps relocatable can...

Either that, or, as I wrote, you can just read the real path of `/proc/self/exe` to get your own binary's path, e.g., using `realpath()` or `readlink()` (C functions).

Well, @aardappel already explained the software uses C++17 features. Why shouldn't it require a recent enough libstdc++? It needs to be capable of C++17, which, as the name suggests, was...