Cross platform C++ plugins by supplying source code
#14
(10-26-2014, 06:24 AM)worktycho Wrote: cPlugin would still need to be thunked to the C coding convention for calls to MCServer if plugins are compiled client side. Otherwise we have to ship a compiler to ensure the layouts, calling convention, and name mangling are the same.
Yes, in the first post I suggested shipping a compiler with MCServer... did you read it?
As for Linux, different versions of gcc should be compatible right? Otherwise how can commercial libraries supply their binaries to Linux if programs can only be compiled with the exact same compiler these libraries were compiled with?

(10-26-2014, 06:24 AM)worktycho Wrote: Also what is to stop people using methods that arn't part of the API? For lua and squirrel we handled this by not doing binding code for those methods. For C++ we either need wrapper classes for every class or to expose every virtual method and every field.
Why would you want to stop people from accessing parts that aren't part of the API? This is actually a good thing in my opinion.
Reply
Thanks given by:


Messages In This Thread
RE: Cross platform C++ plugins by supplying source code - by FakeTruth - 10-26-2014, 08:52 PM



Users browsing this thread: 4 Guest(s)