Knowledgebase
Preprocessor references to files are parsed when in the scope of #ifdef statements
Posted by - NA - on 02 April 2014 09:41 AM


Symptom 1: The IncrediBuild warning "import directives in the precompiled header should use the no_implementation attribute. See FAQ section in documentation for more details." Is received, relating to code inside a multi-line comment.

Symptom 2: When changing a file referenced by an #include statement that appears in the scope of an #ifdef statement that does not evaluate to TRUE, running an incremental build will result in the referencing file being recompiled.

Description: IncrediBuild currently parses all preprocessor references to files, including conditional (#ifdef) portions of the source. The warning described in symptom #1 can occur in cases where an #import statement appears inside such a portion. Note that if your code includes large portions of #include statements in an #ifdef portion, deleting these lines may slightly improve compilation speed.

Solution/Workaround: To make the warning in symptom #1 disappear, add the "no_implementation" keyword to the #import statement or simply delete that line. In addition, please refer to the following link and search for "I'm getting the following warning: "IncrediBuild: build system warning: #import directives in the precompiled header should use the no_implementation attribute. See FAQ section in documentation for more details.". What's wrong?" :

http://www.incredibuild.com/webhelp/webframe.htm#detailed_reference7.html 

(884 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
Help Desk Software by Kayako xoreax.helpserve.com