User Tools

Site Tools


user-guide:export-as-lib

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
user-guide:export-as-lib [2025/04/02 16:31] – [Package name] gaetanuser-guide:export-as-lib [2025/04/03 12:09] (current) gaetan
Line 1: Line 1:
-====== Project as Library ======+====== Project as a Module Library ======
  
 Project can be exported as a library usable from other projects. The exported library makes all types (classes, modules, ...) and resources (images, shaders, ...) available for import. Project can be exported as a library usable from other projects. The exported library makes all types (classes, modules, ...) and resources (images, shaders, ...) available for import.
Line 30: Line 30:
 ==== Reference wrapper ==== ==== Reference wrapper ====
  
 +GroIMP implicitly wrap all references call in the project to be exported as module library to make them use the resources form the library. 
 +
 +Indeed, if a project contains a resource with the name "shaderleaf". When exported, the module that use ''setShader(shader("shaderleaf"))'', needs to point as the resource from the module lib. And not a possible "shaderleaf" in a newly opened project. 
 +
 +The wrappers force the references to point at ''plg:pkg.Plugin:"shaderleaf"''
user-guide/export-as-lib.1743604291.txt.gz · Last modified: 2025/04/02 16:31 by gaetan