rasc_iccarm file for include and preprocessor settings

Question

Moving from RACS v5.2 to v5.7 the iar ipcf-project description file now adds a rasc_iccarm file (using the -f option) to store include paths and preprocessor define settings. This gives us some problems in our build chain. 
 Is there a way to switch off the generation of the -f rasc_xxxx files into the ipcf file?

IK_Renesas · Answer

Hello MIR, 
 After discussing with our tools team, please let me inform you that: 
 The reason new RASC versions generate XCL files is because the data-driven toolchain options can add/modify toolchain options that are not available in the build_info.ipcf. Based on the selected FSP components and properties, advanced toolchain options can be modified according to the FSP data. 
 It is ok to disable RASC in pre-build command once the configuration.xml is stable but managing this will be in user responsibility. 
 RASC invocation in Post-build command is for generating smart-bundle file. This is required if some other projects depend on this project. (e.g. non-secure projects requires the smart bundle of secure projects). If no other projects is referencing it, it is also fine to disable it, but it does not update the project source content and toolchain flags, so IMO it should be fine to leave it. 
 Lastly, we have tried using multiple XCL files, and it also works fine. So, maybe you can amend the toolchain options without removing/editing the xcl files generated by RASC. We have attached the snapshot of this example. This probably easier to implement and manage by the user, if it works for you. 
 
 We don&rsquo;t know what kind of toolchain options you need. If you need to add new options, having multiple xcl files should be fine. If you need to remove some options that RASC add, it depends on the specific options for the toolchain, for example a macro symbol added by -D can be removed by -U. 
 Thanks and Regards, 
 IK