MATLAB: How to use PackNGo without naming dependencies on the current directory

simulink coder

When using the 'Package code & artifacts' feature with code generation, the resulting .ZIP package contains two subfolders. One is named after the current directory, and the other is named after the release of MATLAB. Can this be avoided? I want to write a general (and fixed) makefile that compiles the generated code, but if the folders depend on the current directory then that makefile will have to change every time someone generates the code depending on what their pwd is.

Best Answer

If you do not want to have any sub-folders named after the PWD, you will need to use the 'flat' structure for 'packNGo'. To do this, you can use the command-line API instead of the model's configuration parameters. You will want to add a 'PostCodeGenCommand' with the 'set_param' function. For example:

>> set_param(gcs,'PostCodeGenCommand','packNGo(buildInfo,''packType'',''flat'',''fileName'',''myPackage'')');

For more information about the 'packNGo' command, please refer here:

https://www.mathworks.com/help/releases/R2016b/rtw/ref/packngo.html

For general information about using the command line with 'packNGo', please refer here:

https://www.mathworks.com/help/releases/R2016b/rtw/ug/relocate-code-to-another-development-environment.html#btm64gd-1

Related Solutions

MATLAB: What is the difference between “slbuild” and “rtwbuild”

Several commands are available for building models in Simulink. A comparison of some of these commands is included below.

1) CTRL+B or 'Build' button

These options generate code for the parent model and all referenced models, and obey the model’s Code Generation configuration parameters. If the 'Generate Code Only' checkbox is not enabled, these methods will also build the generated code.

2) "slbuild" command

This function allows more control over the build process.

In its simplest usage – slbuild(‘modelname’) – it is equivalent to using CTRL+B or the 'Build' button.

When used with the 'ModelReferenceCoderTarget' (called ‘ModelReferenceRTWTarget’ in R2018b and earlier) option, "slbuild" builds only model reference blocks within the specified system. As this option’s name implies, the generated code is for the target specified in the Code Generation settings (i.e. GRT, ERT, etc). This option can be helpful to see if model reference blocks will build properly without incurring the extra time of building the parent model as well. A simple way to see how this option works is to create two simple models – a ‘parent’ and ‘child’ model. The child model can be as simple as a gain block connected to an inport and outport. The parent model contains one or more model reference blocks that reference the child model. Calling "slbuild" with this option for the parent model will produce executable for the referenced child model(s).

"slbuild"’s ‘ModelReferenceSimTarget’ option is similar to the above option, but generates code for simulation in Simulink rather than for a target.

Please note that "slbuild" cannot be used for subsystems.

3) "rtwbuild" command

"rtwbuild" is similar to "slbuild", but has fewer capabilities. "slbuild" is more general, and can be used in place of "rtwbuild".

Just like "slbuild", its simplest usage – rtwbuild(‘modelname’) – is equivalent to using CTRL+B or the 'Build' button.

"rtwbuild" and "slbuild" are indeed Simulink Coder functions, but will also work with Embedded Coder. The only difference is whether your model is set up with the grt.tlc (Simulink Coder) or ert.tlc (Embedded Coder) system target file in its configuration parameters.

For more information, please follow the below links:

"slbuild" : https://www.mathworks.com/help/simulink/slref/slbuild.html
"rtwbuild" : https://www.mathworks.com/help/ecoder/ref/rtwbuild.html

Difference between Simulink Coder and Embedded Coder:

https://www.mathworks.com/matlabcentral/answers/232137-difference-between-simulink-coder-and-embedded-coder

MATLAB: How to include the makefile in the ZIP file generated using packNgo

It is a documented limitation that the packNgo feature does not include all files from code generation folder, including makefiles:

https://www.mathworks.com/help/releases/R2019a/rtw/ref/packngo.html#mw_cf56b3af-2472-43a2-ab6f-9726bd9cbe15

packNgo was mainly designed for users who would like to relocate the generated code to another environment or software project. For this use case, packaging the makefile is not necessary.

To work around the issue, disable the 'Package code and artifacts' option and run below script after the code generation has finished:

model = gcs;
bDirInfo = RTW.getBuildDir(model);
makefile  = [model '.mk'];
cd(bDirInfo.BuildDirectory);
load('buildInfo.mat');
addNonBuildFiles(buildInfo, makefile, bDirInfo.BuildDirectory);
% once the makefile is "in" buildInfo, you can run PACKNGO and
% it will automatically include the makefile
% (and any other nonBuildFile you wish to add)
packNGo(buildInfo,{'packType', 'hierarchical','nestedZipFiles',false});

Best Answer

Related Solutions

MATLAB: What is the difference between “slbuild” and “rtwbuild”

MATLAB: How to include the makefile in the ZIP file generated using packNgo

Related Question