The build process of one of the following components aborts:
The following error message is displayed:
Build with RTI:
…
<modelname>.h:<XX>:<XX>: fatal error: brtenv.h: No such file or directory
#include <brtenv.h>
^
compilation terminated.
gmake: *** [<modelname>.obj] Error 1
Build with ConfigurationDesk:
…
DSMAKE: mdladapter_mdlfunctions.cpp:<XX>:<XX>: error: <modelname>_dsrtmdlfcn.h: No such file or directory
…
DSMAKE: Compilation was not successful. (1)
The make phase failed for the following application process: <application process name>.
==== Build process aborted ==================================
Build with VEOS:
…
COMPILING "…\SicAppFrm_FunMod_generated.c"
In file included from …/SicAppFrm_Cfg.h:<XX>:<XX>,
from …\SicAppFrm_FunMod_generated.c:<XX>:
…/SicAppFrm_Cfg_generated.h:<XX>:<XX>: fatal error: <modelname>_dsmpbap.h: No such file or directory
#include "<modelname>_dsmpbap.h"
^
compilation terminated.
COMPILING FAILED. See …\SicAppFrm_FunMod_generated.err for details
MAKE PROCESS ABORTED
Similar error messages might be displayed with different file names.
Why does the compiler report this error message although the mentioned files exist in the file system?
Date | 2016-09-01 |
Software Type | Implementation Software |
Product | ConfigurationDesk, RTI (Real-Time Interface) |
Information Type | Frequently Asked Questions |
Information Category | Troubleshooting |
dSPACE Release | 2023-A, 2022-B, 2022-A, 2021-B, 2021-A, 2020-B, 2020-A, 2019-B, 2019-A, 2018-B, 2018-A, 2017-B , 2017-A, 2016-B, 2016-A, 2015-B, 2015-A, 2014-B, 2014-A, 2013-B, 2013-A, Prior to 2013-A |
Keywords | MEX compiler, MinGW64, MinGW, Windows SDK 7.1, MATLAB R2015b, brtenv.h |
Drive innovation forward. Always on the pulse of technology development.
Subscribe to our expert knowledge. Learn from our successful project examples. Keep up to date on simulation and validation. Subscribe to/manage dSPACE direct and aerospace & defense now.