Reference Guide

10 Chapter 1: Library and Header File Changes
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
Header File Changes
All of the Crypto-C ME 4.1.4 public headers have been namespaced into a bsafe
directory to avoid conflicts with other libraries. When migrating an application from
Crypto-C ME 3.x to 4.1.4, you must either:
• Update the
#include directives and prefix each header file name with bsafe.
RSA recommends this option.
• Add the
bsafe sub-directory as an additional include path to the compiler.
The following tables show both of these options:
Table 2 Update the #include Directives
Crypto-C ME 3.x Crypto-C ME 4.1.4
#include "r_prod.h" #include "bsafe/r_prod.h"
Table 3 Additional Include Path to the Compiler
Crypto-C ME 3.x Crypto-C ME 4.1.4
-I<incdir> -I<incdir> -I<incdir>/bsafe