• Locked Locked
  • Replies 5 replies
  • Subscribers 119 subscribers
  • Views 4070 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Precompiled Header

andredz
Note: This was originally posted on 8th June 2010 at http://forums.arm.com

Problem:
I've been trying to utilize precompiled header option, but with no luck. Even after installing patch 771 for RVCT 4.0.

Here what I'm trying to do.
Assume I have 3 source files and 1 header:

0. /myproject/inc/aaa.h
-----------------------------------
// a bunch of definitions


1. /myproject/src/AAA.c  (created this file to include only the header file and compiled with --create_pch=AAA.pch)
------------------------------
#include "aaa.h"  // this is a very large file
//eof

2. /myproject/src/File1.c (compiled with --use_pch=AAA.pch)
---------------------------------
#include "aaa.h"

// some codes


3. /myproject/differentsrc/File2.c (compiled with --use_pch==AAA.pch)
---------------------------------
#include "aaa.h"

// some codes


So the problem:
File1.c is using AAA.pch and compiled in a snap without any problem.

But File2.c can't use AAA.pch and does a regular compile (long compile). It gives warning:
"no source": Warning:  #629-D: the command line options do not match those used when precompiled header file "AAA.pch" was created

Questions:
- Is this a limitation for the precompiled header option? Files must be in the same directory.
- Are there any other options on how to solve this?

Thank you,
-a
Parents
  • Arm Employee Badge
    Note: This was originally posted on 14th June 2010 at http://forums.arm.com

    [...]
    But File2.c can't use AAA.pch and does a regular compile (long compile). It gives warning:
    "no source": Warning:  #629-D: the command line options do not match those used when precompiled header file "AAA.pch" was created

    Questions:
    - Is this a limitation for the precompiled header option? Files must be in the same directory.
    - Are there any other options on how to solve this?


    It's possible that AAA.pch does actually depend on the current directory or current source file directory.  Does aaa.h contain any #includes?

    Can you show the full command lines for the different compile steps?  Are there any differences besides the pch options and filenames?
Reply
  • Arm Employee Badge
    Note: This was originally posted on 14th June 2010 at http://forums.arm.com

    [...]
    But File2.c can't use AAA.pch and does a regular compile (long compile). It gives warning:
    "no source": Warning:  #629-D: the command line options do not match those used when precompiled header file "AAA.pch" was created

    Questions:
    - Is this a limitation for the precompiled header option? Files must be in the same directory.
    - Are there any other options on how to solve this?


    It's possible that AAA.pch does actually depend on the current directory or current source file directory.  Does aaa.h contain any #includes?

    Can you show the full command lines for the different compile steps?  Are there any differences besides the pch options and filenames?
Children
No data