Hello Maciek,
First of all sorry about the mcd_kvxx vs mctbx_kvxx issue - i got it from the development path name (not the installation path name).
Secondly, I put the entire folder for gcc so that you can drag&drop it into the specified path; there was no gcc support for MCLib for this toolbox in the past (that's the reason why there was no gcc folder).
About the compiler, the GCC_ARM_TOOL system environment variable should point to gcc-arm-none-eabi-4_9; if you have S32K Toolbox you can use the same path as for GCC_S32K_TOOL:
It should be something similar to C:\MBDToolbox\mbdtbx_S32K\tools\gcc-arm-none-eabi-4_9 (as stated in step #3 in the hotfix provided here).
Finally, in regard with CM4_MMCLIB_GCC.a, this file should be copied in the *_rtw folder that is created when you build a model - this is done by the mcd_kv3xf_copy_required_files.p file.
To address your concern, it is safe for you to keep it there, but that is not how it's intended to work - if the mcd_kv3xf_copy_required_files.p copies it into the *_rtw folder, it should work as is, leaving it in the gcc folder.
So can you check (having GCC_ARM_TOOL environment variable set the same to GCC_S32K_TOOL) if you have any errors? And if the errors persist, can you tell me if the CM4_MMCLIB_GCC.a file is in the respective *_rtw folder ?
Thanks!
Razvan.
Edited after initial post : I installed a fresh copy of kinetis tbx from www.nxp.com, added the initial hotfix for gcc, then added this hotfix for MCLib (having GCC_ARM_TOOL set as I stated above) and it works. Please let me know if you encounter any problems after setting the GCC_ARM_TOOL env variable.