Team of OpenCPI developers - ways of working

Application Development
1

I am working on a small team writing an OpenCPI application. Have been through the OpenCPI tutorials where have to run commands such as:

ocpidev create project my_project --register

and other ocpidev commands to create applications, components and build and run.

But for a team of developers, running on VMs, how is it best to share a project? Should we simply create a single project, get that registered on each VM then just update that project? Or clone a new project and is there a way to register the cloned new files/project?

2

The term project is overloaded in this case. There’s is the Git project and the OpenCPI project. The way we’ve worked in our teams is create a new Git project containing an OpenCPI project.

Then each developer would clone the Git project and then register the OpenCPI project into their environment. We’ve clone them in the opencpi/projects directory but they can also live outside the OpenCPI tree.

Inside your new OpenCPI project , Project.xml, can specify dependencies to other project. For example, ocpi.comp.sdr project to access components and workers from other projects.

3

The scenario is I have run the command:
ocpidev create project awesome_app --register

and then created files etc.

But if another user has the relevant files can they somehow ‘import’ or register this project on their own developer machine? How to do that?

4

Yes, you can move the project directory created with ocpidev create project on to their own machine and then do the following:

cd awesome_app
ocpidev register project

This will register the project.