Support for Linux library .so/.o variant to replace Windows library .dll?

[ribbybbir]

I'm not going to use the Japanese language for this topic. The context deals with programming and programming is usually done in English, or at least what I know of.

I recalled that ghost/shell modification requires a library file called .dll, dynamic-link library. That's fine and dandy and all, but it derives from Windows OS support. I would like .so/.o library file support instead, after all, this was ninix-aya, a ukagaka baseware for Linux. It is logical for this program to support Linux instances. Besides, I read that .dll could be susceptible to hijacking, forcing people to scan for malicious scripts within the deemed file. https://en.wikipedia.org/wiki/Dynamic-link_library#DLL_hijacking

How would one know if the .dll might be infected with malware? I would check with virustotal.com's malware scan services. For most ukagaka mods, the .dll is the primary culprit. The safest .dll for ukagaka mods would be misaka.dll. Any ghost mod that uses misaka.dll will do. Of course, the misaka base template ghost will also do.

---

Speaking of libraries, I recently found out that .dll files are like encrypted files so any text editor cannot read its contents. .dll files require de-compilation, which is not so different from .acs compilation to .o for doom mod scripts. We need a specific program for the job. I admit that this part of compilation/de-compilation is a bit of a hassle to me. I gotten too used to DECORATE scripts, which can be read with any text editor. But I suppose advanced scripts require its own encryption for its own specific purposes. The context is about modding than proprietary rights such as copyrights and trademarks.

I eventually found information about de-compiling .dll files. What I disapprove about the ukagaka modding community is the silence over this modding aspect. .dll knowledge gets left in the dark. All I got was an advice to copy another .dll with the preferred behavior. Then I wonder if those modders ever get exact know-how about libraries? I highly doubt it. Anyways, I just touched the surface on de-compiling .dll files, let alone knowing the .dll script layout for ukagaka ghost/shell mods. I might not be near my ukagaka modding goal.
https://john.fremlin.de/linux/howto/win32-disassembly.html
|
After some times, my continued research conclude that Visual Studio Code (with interpreter extension) can open the ukagaka .dll files. That's good to know, but the contents gibber the library code syntax, which will hinder efforts for a custom ghost library. I tried English ghosts, which contain .dll files with the same gibberish and Japanese language. Makes me think if those English speaking ukagaka modders are actually Japanese/bi-lingual speaking ukagaka modders?

By the way, do you know if the original ninix-aya baseware developers will support .so/.o libraries? If that could happen, I can just use any text editor to write up the ghost library code, and use ACS script compiler to convert the source into .so/.o.

[ribbybbir]

In addition to replace .dll library files. I suggest to revamp the ninix(-kagari)'s programming language from Ruby to non-proprietary C code. I would like Hyperbola Linux-libre compatibility, but the standard is quite stringent. Access to installation by source package or repository can be discussed later. Testing with multiple Hyperbola Linux-libre users would be a good recommendation.