Using the kit-app-template (kit ver. 106), I’m trying to add extensions to my kit app. I’m placing my extensions into kit-app-template/source/extensions and when I run the repo build command, the extensions that I generated using the kit-app-template are placed into the _build/.../release/exts folder like I want. but the extensions that were created via other means (like the kit-extension-template) are not being added to the _build despite also being in /source/extensions. is there some way to make sure my extensions are added to the kit app build?
Something else observed is that the extensions that do get added to the build have similar two block naming conventions (like one.two and hello.world) while the ones that aren’t added are named in a three block manner (like omni.hello.world). I believe this is too silly to be the problem though.
Sorry for late reply. There is a necessary premake5.lua file that goes with each extension that lets the build move those extensions. You can find this file by creating an extension using the kit-app-template
For completeness: @austinhwang18 solution is correct. The premake5.lua file (such as the one generated by the Kit App Template when creating extensions) is necessary for the build tooling to include the extension in the build.
The development team is aware of the discrepancies across repositories and will work towards unifying them in the future.