In the scope of #39, Goa became capable of looking up version information from other Goa projects below the current working directory. This way dependent Goa projects can be hosted in a common subdirectory and Goa detects their versions. However, it requires to invoke Goa from the common subdirectory using the -C switch.
In order to simplify this, we should add a --search-dir argument and the corresponding search_dir variable to explicitly set the location from which Goa starts looking for projects to something other than the working directory. For my system_info project, for instance, I can then add a goarc file that sets the search_dir to the path where all the lvgl library projects are located. With this I become able to simply call goa run in the system_info directory without Goa complaining about missing lvgl version information.
In the scope of #39, Goa became capable of looking up version information from other Goa projects below the current working directory. This way dependent Goa projects can be hosted in a common subdirectory and Goa detects their versions. However, it requires to invoke Goa from the common subdirectory using the
-Cswitch.In order to simplify this, we should add a
--search-dirargument and the correspondingsearch_dirvariable to explicitly set the location from which Goa starts looking for projects to something other than the working directory. For my system_info project, for instance, I can then add a goarc file that sets thesearch_dirto the path where all the lvgl library projects are located. With this I become able to simply callgoa runin the system_info directory without Goa complaining about missing lvgl version information.