You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the GirTool generate command accepts a list of input repository files to generate code for. Any includes in these files are resolved and added to the list of output repositories by the RepositoriesDependencyResolver class. This is needed for generating code for interacting with dependencies, but sometimes users won't want to generate code for all dependencies but rather use them via package references, such as when using GirCore.GLib-2.0 for example.
I'd like to change the GirTool behaviour so that these includes that aren't from repositories explicitly listed in the input argument don't get code generated. They would still need to be loaded and resolved though.
The text was updated successfully, but these errors were encountered:
Continuing the discussion from #1078 (comment)
Currently the GirTool generate command accepts a list of input repository files to generate code for. Any includes in these files are resolved and added to the list of output repositories by the
RepositoriesDependencyResolver
class. This is needed for generating code for interacting with dependencies, but sometimes users won't want to generate code for all dependencies but rather use them via package references, such as when using GirCore.GLib-2.0 for example.I'd like to change the GirTool behaviour so that these includes that aren't from repositories explicitly listed in the
input
argument don't get code generated. They would still need to be loaded and resolved though.The text was updated successfully, but these errors were encountered: