CVI2013: _TARGET_PRODUCT_VERSION_ and _TARGET_FILE_VERSION_ troubles

[LuisG]

Hello Carlo,

(Sorry for not responding earlier, I was out of the office last week).

Okay, I understand your use case of having to occasionally make small changes in the release configuration. I certainly agree with you that encountering a compilation error in this situation is incorrect. This is clearly a bug and it will be addressed soon.

I can also see how the requirement to rebuild the entire project, especially considering that you are not even using these macros in your program can be frustrating.

I don't agree with you, however, that these macros should not exist at compilation time. Because they can be used in your source code in order to control some logical flow of your program, and not only as properties of the final executable or dll, they do have a compile-time impact.

We cannot make the constants "not exist". They have existed for several versions of CVI up until now, and to remove them would break existing programs that do use them, even if they might be "doing it wrong" . We also cannot exclude the variable part from the constants, since that too would modify the behavior of existing programs.

As mentioned earlier by Alpar, in the short term this bug will have to be fixed by triggering a full-rebuild of your program for release configurations, when auto-increment is enabled. The problem lies in the fact that CVI does not know whether you are using them in your source code or not. Therefore, as a compromise, we'll add an option later on that will allow you to disable the use of the source code macros. That way, if you disable that option, a rebuild will not be triggered.

Luis

[carlox]

Hello Luis,

(delay isn't a problem, we are all busy...)

I agree with you almost on everything.

The simply fact that they can be useful to someone, IMHO, can't justify what I see as weak definition.

Weakness derives from my personal idea of what is a "file version number", or "product version number", may be I'm beginning to be outdated.

I hope my own next version will be compatible with the present one, too  

I will not insist on my point of view, anyway, this isn't my main problem at present  and I will survive to spurious error messages .

Keep up the good work!