In the previous articles, we used freestanding applications and relied on a global Zephyr installation. In this article, we’ll see how we can use West to resolve global dependencies by using workspace applications. We first explore West without even including Zephyr and then recreate the modified Blinky application from the previous article in a West workspace.
Wouldn’t it be better to also include the PIPFILE into the git repo?
I’d say yes, but it depends on your environment. E.g., by default vscode only picks up a Pipfile if it is in your workspace root, and in a standard T2 application the workspace root is not the Git repository. You can restructure your repository, of course, but then you might make it incompatible to be used as West module in a later step.
See, e.g., the ZMK repository: GitHub - zmkfirmware/zmk: ZMK Firmware Repository. This repository uses a different approach where the Git repository is your entire workspace. But then you need to clone the repo yourself and live with some other restrictions.
Whatever works best for you 