TiCS 2025.1.0 Highlights

New TICS Config

TICS Config has gotten a major overhaul and has been moved to the TICS Viewer’s User Settings. Now your personal settings are available wherever you run TICS Client. This also means TICS Config requires a user account from now on. If you don’t have one already, contact your TICS representative to have one created for you. The UI has been made more intuitive, so you can get the most out of TICS Client. The previous TICS Config will no longer work and no updates will be done anymore to this version.

New TICS Wrappers

To accommodate for the new TICS Config, lessen the memory footprint and improve the performance, a significant change was also made to the wrappers. This is a breaking change, meaning the previous wrappers (<= 2.0.0) are not compatible with TICS from 2025.1.0 and up. Vice versa, Wrappers 3.0.0 and up are only compatible with TICS 2025.1.0 and later. Please refer to TICS Client installation options for information about how to update your TICS wrappers.

C++Test Integration

To adhere to new license agreements with vendor Parasoft, the C++Test integration, rule implementations and rule configurations have been updated. From now on, a Parasoft license server needs to be deployed from which TICS will obtain its C++Test license. Updating to TICS 2025.1.0 requires the following:

• Update of the C++Test rule implementations
• Update of the C++Test rule configuration (RULES.txt and IMPL.txt)
• Deployment of a Parasoft License Server
• Parasoft C++Test License

Your current C++Test version remains compatible, though updating is always advised. Please note that the performance will degrade when switching to the new C++Test integration. We are working on this aspect with Parasoft to get this improved.

Include What You Use (IWYU)

With “Include what you use“, for every symbol (type, function, variable, or macro) that you use in a source file (foo.c), either foo.c or foo.h should include a header file that exports the declaration of that symbol. Symbols defined in the source file itself are excluded from this requirement. Include-what-you-use makes heavy use of Clang internals, and heavily depends on the Clang version as it will occasionally break when Clang is updated. The maintainers make sure IWYU is regularly built against Clang mainline to detect and fix such compatibility breaks as soon as possible.

You can find the full release notes, here.