Enhancement: NekoVM compatibility

[ThePlank]

Currently when you try to build with neko, it spits out a error about using a cpp function (relating to DiscordRpc) being used on a Neko target. I'm probally going to make a PR relating to this.

This is what happens happens when you try to build with Neko:

[ThePlank]

This also happens when building with Mac, and linux.

[VMGuy23]

Building Linux on Linux machine works fine

[ThePlank]

I think building on windows seems to be the problem.

[nickplj12]

.. I'm probally going to make a PR relating to this.

PLEASE DO, I really don't want to install 4 gigabytes of unwanted space on my PC just to compile on Windows

(you are allowed to react 👎, 😕, or 👀 on this)

[ThePlank]

I tried to make DiscordClient CPP only, but when i try to test it with Neko it just hangs, i know that Main.hx isn't the problem because i was testing another game with the Main from the game and using the Neko build target and it worked fine.

Example (Title bar says Not responding):

Edit: it MAY be a problem with main, i changed the initial state to a Hello world! state but it dosen't work.

[jbmagination]

"You cannot access the cpp package while targeting neko" Will look into the discord_rpc library, then. For reference, this is the source code for the RPC library - https://github.com/Aidan63/linc_discord-rpc

[jbmagination]

https://github.com/Aidan63/linc_discord-rpc/blob/2d83fa863ef0c1eace5f1cf67c3ac315d1a3a8a5/discord_rpc/DiscordRpc.hx#L3-L7

Well, that explains a lot. Will try building this later and seeing if I can get it to work in Neko (which should be relatively easy!)

[jbmagination]

Update: It will not be easy! Haxe docs show a lot of the CPP functions used aren't supported in Neko, so I'll need to recreate them. That's nice.

[nickplj12]

Update: It will not be easy! Haxe docs show a lot of the CPP functions used aren't supported in Neko, so I'll need to recreate them. That's nice.

just make a whole frickin engine on it

[ThePlank]

what

[steviegt6]

what

Someone just referenced this issue on accident when merging a PR from some other repository. GitHub can be finicky wit that,