VisualDSP++

Hi,

We have some general guidelines to reducing the build time for projects where the build is particularly time-consuming:

- If you have C++ files in your project you could try using the "-no-implicit-inclusion" switch to the Compiler. (Some customers have seen a significant improvement in compile times when using this switch. )
- Don't use a networked license.
- Don't use mounted/networked source/include directories.
- Clean out your temporary directory occasionally. A lot of files can slow down the system in general.
- Identify files which take a long time to compile and consider breaking them down into smaller files, perhaps on a per-function bases. If any files are taking an unacceptable length of time to compile, report them to tools support.
- Disable pre-processing in generated assembly, if you don't need it (with "-flags-asm -sp").
- Keep files local (so that network traffic isn't required).
- Keep PATHs short and local (ditto)
- Reduce amount of rebuilds needed because of dependencies (i.e. don't have an auto-generated .h file that's included by everything, if you can avoid it) -ipa takes much longer than -O.
- Re-configure virus scanner (so that it's not re-scanning all of the tool-chain every time you re-build.
- Add more memory.
- Don't have large arrays of constants, either in C or in assembler (because the compiler and assembler aren't great at parsing very long sequences of initialiser tokens) -Oa and #pragma always_inline can make functions very large, and those can take very long times to compile or optimise.

- Use the 'Build' rather than 'Rebuild' when appropriate.

Regards,

Craig.

This question has been assumed as answered either offline via email or with a multi-part answer. This question has now been closed out. If you have an inquiry related to this topic please post a new question in the applicable product forum.

Thank you,
EZ Admin