Why is the preprocessor check #if ( UCHAR_MAX != (0xFFU) ) || ( SCHAR_MAX != (0x7F) ) being generated in private.h?
In the generated code for my model, I have noticed that the following code is generated in the "model_private.h" file:
#if ( UCHAR_MAX != (0xFFU) ) || ( SCHAR_MAX != (0x7F) )
#error Code was generated for compiler with different sized uchar/char.
Consider adjusting Test hardware word size settings on the
Hardware Implementation pane to match your compiler word sizes as
defined in limits.h of the compiler. Alternatively, you can
select the Test hardware is the same as production hardware option and
select the Enable portable word sizes option on the Code Generation >
Verification pane for ERT based targets, which will disable the
preprocessor word size checks.
#endif
Why is this code being generated?In the generated code for my model, I have noticed that the following code is generated in the "model_private.h" file:
#if ( UCHAR_MAX != (0xFFU) ) || ( SCHAR_MAX != (0x7F) )
#error Code was generated for compiler with different sized uchar/char.
Consider adjusting Test hardware word size settings on the
Hardware Implementation pane to match your compiler word sizes as
defined in limits.h of the compiler. Alternatively, you can
select the Test hardware is the same as production hardware option and
select the Enable portable word sizes option on the Code Generation >
Verification pane for ERT based targets, which will disable the
preprocessor word size checks.
#endif
Why is this code being generated? In the generated code for my model, I have noticed that the following code is generated in the "model_private.h" file:
#if ( UCHAR_MAX != (0xFFU) ) || ( SCHAR_MAX != (0x7F) )
#error Code was generated for compiler with different sized uchar/char.
Consider adjusting Test hardware word size settings on the
Hardware Implementation pane to match your compiler word sizes as
defined in limits.h of the compiler. Alternatively, you can
select the Test hardware is the same as production hardware option and
select the Enable portable word sizes option on the Code Generation >
Verification pane for ERT based targets, which will disable the
preprocessor word size checks.
#endif
Why is this code being generated? fixedpoint, codegen, header, check, limit MATLAB Answers — New Questions