Shouldn't a change of warning level initiate a re-compilation?

[Wolfgang]

Hi,

if I change Build Options / Configuration Options / Compiler Warnings / Warning level say from Common to Extended I would have expected that the source code is recompiled, but it is not. I have to edit my file to force recompilation. Is this by design? I thought to remember that some earlier versions of CVI behaved differently (observed using CVI2015).

Thanks!

[Johannes_T]

Hello Wolfgang!

The intended behaviour in LabWindows/CVI 2015 is indeed to recompile your source files in your project after you change the warning level from the Build Options dialog. Let's say you create a project from template, you compile the project, change the warning level from the Build Options dialog and then do a build of the program. Your sources should be recompiled.

Is your source file that you isn't recompiled added in the current active project Project Tree?

Is the date/time setting in your Operating System set correctly? I'm asking this, in the case it isn't and you've copied some source files from a different computer, thus having a different timestamp. This could explain why after you modified the files, the source files are recompiled.

Best regards!

- Johannes

[Wolfgang]

Thanks Johannes!

Indeed it works as expected on my office computer - I will have to check why it appeared to be different at home...