Locking in fprime and fprime-venv version

[LornDMiller]

Sorry if this has been asked before, I'm not having much luck finding it with search. Is there some way (e.g. settings.ini?) to lock in the specific git hash for the fprime (and I'm assuming this will lock in the tools for fprime-venv)? Is this locked in via the git submodules? We have multiple developers and right now they're passing around these two directories to keep everyone in sync and I don't think I need to explain why that's a bad idea.

[thomas-bc]

F´ version

The F´ version is managed by the git submodule in your project. A project (e.g. https://github.com/fprime-community/fprime-workshop-led-blinker) is a git repo that has a pointer to a specific version of F´, in the form of a git submodule.

When you create a project with fprime-bootstrap project, it'll select the latest released version and stick that in your project as the submodule. That manages the F´ version.

fprime-venv

fprime-venv should not be moved or passed around. To clone an existing project, you can use fprime-bootstrap clone https://github.com/my_user/my-fprime-project which will set up a virtual environment on your system. If you're comfortable managing your own python virtual environment, you're welcome to do that, you'll just need to install ./fprime/requirements.txt in it.

The HelloWorld Tutorial should explain these things in the project setup parts. If things could be made clearer, please feel free to open a pull request! :)

[LornDMiller]

Thanks!