{"id":14151,"date":"2023-04-21T13:15:17","date_gmt":"2023-04-21T17:15:17","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=14151"},"modified":"2023-04-21T13:15:17","modified_gmt":"2023-04-21T17:15:17","slug":"referenced-projects","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2023\/04\/21\/referenced-projects\/","title":{"rendered":"Referenced Projects"},"content":{"rendered":"
Today I want to talk about <\/span>Referenced Projects<\/span><\/a>. They can be very useful to componentize a large project, allowing for modular work, component reuse, unit testing, etc.<\/span><\/div>
Working in technical support and interacting with users from all kinds of industries, I often see MATLAB Projects referencing 20, 50, or even 100 projects. Obviously, not all those are organized the same way.<\/span><\/div>
In this post, I will describe the main types of setups I see. I would like to hear your thoughts in the comments below on your preferred way to organize referenced projects and why. I also created a <\/span>poll<\/span><\/a> that you should see on the left of this post. <\/span><\/div>

Absolute Path<\/span><\/h2>
To add a referenced project to your current project, start by clicking on the References button in the Project toolstrip:<\/span><\/div>
\"\"<\/img><\/div>
This will open the Add Reference dialog and allow you to select the reference type. Let's start with one that I don't see being used very often: Absolute.<\/span><\/div>
\"\"<\/img><\/div>
As the dialog says, you must ensure that the location is available to all users. This can be useful to include a utility project for which all users in the company need to use the same version, stored in a network location available to all users.<\/span><\/div>

Relative<\/span><\/h2>
A more common way of organizing referenced projects is to specify their location <\/span>relative<\/span> to the top project. Among the projects we ship as examples and projects I receive from users, I typically see two types of relative setup:<\/span><\/div>
\"\"<\/img><\/div>
Let's see the implications associated with those two architectures.<\/span><\/div>

Relative - Outside<\/span><\/h2>
If you look at the example <\/span>Work with Referenced Projects<\/span><\/a>, you will notice that it references two projects. If you select either of the two, you will see that they are both in a relative location that begins with \"..\/\", meaning that they are stored in a folder beside the main project top folder:<\/span><\/div>
\"\"<\/img><\/div>
With this setup, you will not see the files from the referenced projects in the \"Files\" view:<\/span><\/div>
\"\"<\/img><\/div>
Instead, you can go to the References view and click the Show\/Hide Files button on the top right to view the files for the selected referenced project:<\/span><\/div>
\"\"<\/img><\/div>
This setup can be useful if multiple referenced projects are themselves referencing a common project. Placing all the projects side by side allows the common referenced project to be referenced using \"..\/\" by multiple projects. Here is a screenshot from the <\/span>Powertrain Blockset<\/span><\/a> example <\/span>Conventional Vehicle Reference Application<\/span><\/a> where the project <\/span>VehicleConfig<\/span> is referenced four times.<\/span><\/div>
\"\"<\/img><\/div>

Relative - Inside<\/span><\/h2>
Another approach is to include referenced projects using a relative path, but inside the main project. This is in fact necessary if you want to <\/span>reference a project as a Git Submodule<\/span><\/a>.<\/span><\/div>
If your project is under <\/span>Git source control<\/span><\/a> and you would like to include a referenced project stored in a separate repository, you can do it using <\/span>submodules<\/span><\/a>. Begin by clicking on the Submodules icon on the toolstrip:<\/span><\/div>
\"\"<\/img><\/div>
In the submodules window, click Add and you will see that the submodule path must be inside the main project:<\/span><\/div>
\"\"<\/img><\/div>
Once the submodule has been added to the project, you can then add it as a referenced project using the same steps as described at the beginning of this post:<\/span><\/div>
\"\"<\/img><\/div>
One thing I like when using a relative path inside the main project is that I can see all the files in the main project window, including the files in the referenced projects. As you can see, the Status and Git columns have icons indicating that those files are in referenced projects and submodules.<\/span><\/div>
\"\"<\/img><\/div>
Another advantage of placing the projects you want to reference inside the main project folder is that we can identify if they have not been configured as referenced projects properly. For that, use the <\/span>runChecks<\/span><\/a> function or click on the <\/span>Check Project<\/span><\/a> <\/span>button in the Tools gallery of the project window. (Tip: I made the Check Project button a favorite, so it shows up at the top of the gallery)<\/span><\/div>
\"\"<\/img><\/div>
If we find projects in sub-folders inside your project that are not marked as referenced projects, we will let you know and offer to fix it in one click:<\/span><\/div>
\"\"<\/img><\/div>

Now it's your turn<\/span><\/h2>
I would really like to hear your opinion on this type of project componentization choices. Are you on team \"Outside\" or team \"Inside\"? Or maybe you found the perfect combination of both?<\/span><\/div>
Take a few seconds to respond to <\/span>the poll<\/span><\/a> on the left of this post and share your thoughts in the comments below.<\/span><\/div>\r\n<\/div>