osx
28 views
Skip to first unread message
Jasper Blues
Dec 22, 2012, 12:50:56 AM12/22/12
to Cedar Discuss
Hi Folks,
I'm running Cedar on OSX. . . Whenever I modify a Spec I get:
file '...-80daa93c/Build/Products/Debug/Cedar.framework/Headers/SpecHelper.h' has been modified since the precompiled header was built
Any idea how to work around this? Is there a way to tell Xcode to clean my target before building? (without using two keyboard strokes)
Adam Milligan
Dec 26, 2012, 9:21:27 AM12/26/12
to cedar-...@googlegroups.com
Hm. I honestly don't know; I haven't had this problem in the past. We regularly use Cedar for OSX builds, so it should work fine. How exactly are you including the file in the PCH? Are you using <Cedar/SpecHelper.h>? Do you have any header search paths set? It seems strange to me that the error message you references the location of the header file from the build products directory, rather than your project directory, since this appears to be a compile warning rather than a link or runtime warning. If the compiler is finding the header file in the build directory then it may be upset because the header gets overwritten on build. That's my best guess.
Jasper Blues
Dec 26, 2012, 9:31:02 AM12/26/12
to cedar-...@googlegroups.com
Yes, I've used Cedar successfully myself on other OSX projects. The only difference I can think of is that this particular project is a cmd-line tool (at the moment, but will soon turn into a framework). I used the Cedar Spec Suite template for OSX. This created the pch, example spec, etc for me.
Anyway, for unrelated reasons I ended up using just OCUnit on this one:
a) I want it to build without dependencies.
b) I'm waiting for better Cedar support in AppCode . .
If it happens again on the next project I'll let you know.
Happy holidays!
Reply all
Reply to author
Forward
0 new messages