• 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: Build error MasterObjectFile.combine
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build error MasterObjectFile.combine


  • Subject: Re: Build error MasterObjectFile.combine
  • From: mike nidel <email@hidden>
  • Date: Fri, 19 Oct 2001 10:03:47 -0400

> From: email@hidden
> Date: Fri, 19 Oct 2001 00:17:00 EDT
> Subject: Build error MasterObjectFile.combine
> To: email@hidden, email@hidden
>
> When I #import the header file of one of my classes into the main.m file of
> the project, I get a "see build log for details" error and the build log says:
>
> ...failed MasterObjectFile.combine ......./master.o
>
> What is the problem? I have not been able to find any information on this
> problem. Thank you.


I had this exact problem - there might be some additional info in the build
log that tells you more specifically what caused the problem. Try scrolling
up a bit (not easy since project builder doesn't seem to give us scrollbars
- can we request them?).

In any case, that error seems to basically mean your project won't link,
without much explanation as to why - probably you are calling a function or
method for which there is no compiled code, even if the right headers are
imported. I had that problem for two reasons:

1. Referencing a symbol/function call not included in my project. (Either
because I forgot to include the framework, or took the file containing that
function out of the project by unchecking it.)

2. Trying to compile an abstract class for which I didn't give an
implementation. For example:

@interface SomeClass
{
}
- (void)method1;
- (void)method2;
@end

without having the @implementation (even if the methods are empty, which
they were in my case). I never got a message that I had failed to implement
the class, just this link error.

All I can say is, look closer at the build log and see if you can determine
what file(s) won't link.


While I've got the microphone, I just want to say that I think Command-R
should only build the executable if it hasn't already been built
successfully, and Command-Option-R could instead force a rebuild. That's my
two cents.


-mike nidel


  • Prev by Date: Re: private methods?
  • Next by Date: Re: Security Issue ... was[What happens to ...]
  • Previous by thread: Re: Build error MasterObjectFile.combine
  • Next by thread: Pointers to methods (or functions, for that matter)
  • Index(es):
    • Date
    • Thread