Sfoglia il codice sorgente

Small Documentation Addition: Corelibs vs Optlibs

MeFisto94 8 anni fa
parent
commit
8ad5f1e884
1 ha cambiato i file con 3 aggiunte e 0 eliminazioni
  1. 3 0
      docs/libraries.md

+ 3 - 0
docs/libraries.md

@@ -43,3 +43,6 @@ Apart from the automatic generation failing sometimes we have another flaw which
 Many libraries depend on eachother like nearly all libraries depend on core.
 Now to not have 10 versions of `jme3-core` inside the libraries which might even cause the build to fail, we simply discard those inner-jme dependencies and force the user to manage them appropriately.  
 The Question here is if that is the right approach? For `jme3_xbuf` it lead to problems because things like `jme3_xbuf_loader` and `jme3_xbuf_physics_loader` aren't seperate artifacts and will be bundled into one library. Thats why there is a workaround for Xbuf.  
+
+## Corelibs vs Optlibs
+It seems that when the sdk itself depends on something, it has to be in corelibs, optlibs only seems to be for the user of the sdk.