Valentin

@TheAssassin Related to this topic I have the particular case of Python C extension modules. Those are basically shared libraries that are dynamically loaded by Python on an `import statement`....

Just thinking, would it be OK if: - When linuxdeploy finds a shared library in AppDir, but not located in `/usr/lib` then - It sets its runpath to "$ORIGIN;$ORIGIN/relative/path/to/usr/lib" Would...

@TheAssassin : Switching to a C++ plugin seems to be the most flexible indeed. Concerning the implementation, should each plugin package its own version of `liblinuxdeploy`? Or is it shared...

That would be great. Currently I'm using a 2 calls process as: ``` linuxdeploy --appdir AppDir \ --plugin python linuxdeploy --appdir AppDir \ -i python.png -d python.desktop \ -e exe...

In my case `exe` is built by the plugin. If I pack it in a single call it says: `exe` not found. Also the dependencies of extension modules (#77), built...

I got the same problem. I changed the naming of my functions which with rather OK in my case. The second suggestion, i.e. provide exceptions for group names in the...

Hello, yes, I would expect this do work. Actually, I could distribute the relocated Pythons as zip files as well. AppImage is relevant only when running live without extracting. But...

Hey @anki-code . I was just curious if you had any success on this? I could make use of it as well for OSX :) But maybe this was not...

OK, I see. Patchelf needs a replacement on OSX. It is used to make binaries look for shared libs under a relative path (hence in the AppImage as well) instead...

Hey @anki-code . Interesting :) Does it work fine for xxh on OSX? It looks like everything is built from scratch, isn'it? Python-appimage instead relies on an existing install. It...