GlueGen proper size / alignment of primitive and compound types usage [2/2] - Fin

MachineDesction == MD

MD.StaticConfig:
  - enum for all supported static configs (ID -> MD)
  - verified at runtime: test runtime queried-MD versus static-MD,
    hard fail if not compatible (size/alignment)

SizeThunk primitive sizes:
  - Add notion of fixed native size (eg. int64_t) and otherwise (eg. long)

java struct 'wrappers' code generation:
  - single class using size/offset arrays of all MachineDescription configurations
  - at runtime the array idx is queried in static block
  - type aligment for not fixed-native-size types (SizeThunk, undef long/int) via StructAccessor

junit test:
  - add float test
  - fix native code
  - add java (create, write)  -> native (verify) test

works (tested) on: linux 32/64 and windows 32/64

1 files changed, 0 insertions, 20 deletions

diff --git a/src/java/com/jogamp/gluegen/GlueEmitter.java b/src/java/com/jogamp/gluegen/GlueEmitter.java
index ac1065b..99bf31d 100644
--- a/src/java/com/jogamp/gluegen/GlueEmitter.java
+++ b/src/java/com/jogamp/gluegen/GlueEmitter.java
@@ -54,26 +54,6 @@ public interface GlueEmitter {
 
   public void readConfigurationFile(String filename) throws Exception;
 
-  /** Sets the description of the underlying hardware. "md32"
-      specifies the description of a 32-bit version of the underlying
-      CPU architecture. "md64" specifies the description of a 64-bit
-      version of the underlying CPU architecture. At least one must be
-      specified. When both are specified, the bulk of the glue code is
-      generated using the 32-bit machine description, but structs are
-      laid out twice and the base class delegates between the 32-bit
-      and 64-bit implementation at run time. This allows Java code
-      which can access both 32-bit and 64-bit versions of the data
-      structures to be included in the same jar file. <P>
-
-      It is up to the end user to provide the appropriate opaque
-      definitions to ensure that types of varying size (longs and
-      pointers in particular) are exposed to Java in such a way that
-      changing the machine description does not cause different shared
-      glue code to be generated for the 32- and 64-bit ports.
-  */
-  public void setMachineDescription(MachineDescription md32,
-                                    MachineDescription md64);
-
   /**
    * Begin the emission of glue code. This might include opening files,
    * emitting class headers, etc.