4 Commits (78816ef5f29bb9d404c7bd1dceaa015b7313e72b)

Author	SHA1	Message	Date
Graham	fbf6a5f597	Stop building OS-specific modules on all systems ... They were only built on all systems for the benefit of the site plugin, but I'm not intending to use that any more.	5 years ago
Graham	fc7583c58a	Build all natives on all platforms ... On unsupported platforms we stub out the methods. I'm thinking about using the Maven site plugin to manage the project website, and it is nicer for documentation purposes for all of the modules to be available in the site regardless of the platform it is built on.	5 years ago
Graham	3e2192236f	Add jaggl_dri implementation	5 years ago
Graham	d77de89ea1	Add JNI header files generated from jaggl and jagmisc ... A long-term goal is to write clean room implementations of these libraries, for several reasons: * The original libraries are missing, so we currently have to do a fair amount of awkward bytecode patching in the loader to use JOGL instead. * The original libraries were not compiled for 64-bit Linux. We might also want to compile for new architectures (e.g. ARM or RISC-V) or additional operating systems (e.g. the BSDs). * I'm worried that over time the libraries will bit rot and might eventually stop working with modern JREs - it's already been about 10 years since they were originally compiled! I'm not too concerned about putting this in the main open-source repository: I think it's generally believed that interfaces are not copyrightable, and we're only copying the interface for interoperability purposes. The native code will be original. Furthermore, most of the jaggl interface is just a copy of the OpenGL interface, so it's unlikely that Jagex could claim they hold the copyright on it anyway.	5 years ago