• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: I hate xcode for such a bugs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: I hate xcode for such a bugs


  • Subject: Re: I hate xcode for such a bugs
  • From: Bill Bumgarner <email@hidden>
  • Date: Fri, 09 Oct 2009 08:59:32 -0700


On Oct 9, 2009, at 5:41 AM, Шкраблюк Павел wrote:

6. comment (or remove) some of A's members in 1.h/cpp and push cmd+b
  and ... you'll get LINKER error! What does it mean? It means that
  it didn't even try to COMPILE main.cpp.

I tried to figure out what happens for about 3 days.
Today I've found solution - set file type of 1.h to 'sourcecode.cpp.h'
(when created automatically it gets 'sourcecode.c.h'); when this is
done everything goes right - I get compiler error.

(If you were to look at the linker errors, it would tell you that the symbols you commented out don't exist. While not as useful as a compiler error, it is still pretty indicative of the real problem. However, I fully agree that the compiler should have failed.)


I don't think that is the problem. I just set up the exact scenario as you described and got a compiler error. Furthermore, I my 1.h file is of type 'sourcecode.cpp.h'.

So, something else is going on in your configuration.

When something like this happens, the first question is whether or not there is anything not straightforward about your filesystems. Namely, are you working on a mounted filesystem? Have you changed your system's clock recently? Is there anything else that might have touched the files -- changed the modification dates -- such that the dependency checker wouldn't have noted the change?

In any case, I would definitely encourage you to file a bug via http://bugreport.apple.com/ . The tools shouldn't behave this way (and they don't, generally -- Xcode is tested extensively prior to release). Even if the problem were to prove to be something odd with your machine, it would be preferable to catch such a problem before you hit the build button.

b.bum



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: I hate xcode for such a bugs
      • From: Sherm Pendley <email@hidden>
References: 
 >I hate xcode for such a bugs (From: Шкраблюк Павел <email@hidden>)

  • Prev by Date: Re: I hate xcode for such a bugs
  • Next by Date: Re: subversion instructions for 3.1.4?
  • Previous by thread: Re: I hate xcode for such a bugs
  • Next by thread: Re: I hate xcode for such a bugs
  • Index(es):
    • Date
    • Thread