Packages in corto can be used by applications in potentially multiple languages. Therefore generated APIs for a particular language should not be compiled in with the package, but loaded separately.
In practice this means that the results generated by the corto/gen/c/api generator will no longer be part of a package. Instead the generated API will be available in a package foo/c for a package called foo.
When a corto project is built it will automatically create a subfolder called c that will contain the generated API. Once more language bindings become available, these will also be automatically generated for the package.
Packages in corto can be used by applications in potentially multiple languages. Therefore generated APIs for a particular language should not be compiled in with the package, but loaded separately.
In practice this means that the results generated by the
corto/gen/c/apigenerator will no longer be part of a package. Instead the generated API will be available in a packagefoo/cfor a package calledfoo.When a corto project is built it will automatically create a subfolder called
cthat will contain the generated API. Once more language bindings become available, these will also be automatically generated for the package.