FROM : Herb Petschauer
DATE : Sun Nov 18 21:21:59 2007
On 18/11/2007, Shawn Erickson <<email_removed>> wrote:
>
> On Nov 18, 2007, at 11:50 AM, Charles Hamel wrote:
>
> > The definition is exactly the same, I copied/pasted it just to be
> > sure.
> >
> > No namespaces involved.
> >
> > I understand the nature of the error, it really looks like somehow
> > the linker doesn't see the analyze method implementation in
> > Vision.mm, even if it is included in the target.
> >
> > What I don't get is that AppController.mm compiles fine, it even
> > highlights the vision->analyze(...) statement, so it knows it is a
> > valid symbol right ?
> >
> > I have read the Apple doc many time now and I don't get what's
> > missing, is there a way to force the linker with some kind of extern
> > statement in my case ?
>
> You see the Vision.mm file get compiled in the build log? You sure
> some ifdef isn't preventing it from being compiled in?
>
> -Shawn
Sorry to interject (Sunday afternoon and all...)
Have you tried added an #error directive to Vision.mm (that proves
whether it is being compiled or not).
Then add the #error directive just before calling your C++ code. And
add the #error directive into your C++ code to see if it is getting
compiled.
#error WTF?
Back to Sunday afternoon...
Cheers,
-H.
DATE : Sun Nov 18 21:21:59 2007
On 18/11/2007, Shawn Erickson <<email_removed>> wrote:
>
> On Nov 18, 2007, at 11:50 AM, Charles Hamel wrote:
>
> > The definition is exactly the same, I copied/pasted it just to be
> > sure.
> >
> > No namespaces involved.
> >
> > I understand the nature of the error, it really looks like somehow
> > the linker doesn't see the analyze method implementation in
> > Vision.mm, even if it is included in the target.
> >
> > What I don't get is that AppController.mm compiles fine, it even
> > highlights the vision->analyze(...) statement, so it knows it is a
> > valid symbol right ?
> >
> > I have read the Apple doc many time now and I don't get what's
> > missing, is there a way to force the linker with some kind of extern
> > statement in my case ?
>
> You see the Vision.mm file get compiled in the build log? You sure
> some ifdef isn't preventing it from being compiled in?
>
> -Shawn
Sorry to interject (Sunday afternoon and all...)
Have you tried added an #error directive to Vision.mm (that proves
whether it is being compiled or not).
Then add the #error directive just before calling your C++ code. And
add the #error directive into your C++ code to see if it is getting
compiled.
#error WTF?
Back to Sunday afternoon...
Cheers,
-H.
| Related mails | Author | Date |
|---|---|---|
| Charles Hamel | Nov 18, 18:21 | |
| Charles Hamel | Nov 18, 18:22 | |
| Scott Ribe | Nov 18, 18:24 | |
| Charles Hamel | Nov 18, 18:27 | |
| stephen joseph but… | Nov 18, 19:11 | |
| Charles Hamel | Nov 18, 19:31 | |
| stephen joseph but… | Nov 18, 19:43 | |
| Charles Hamel | Nov 18, 20:50 | |
| Shawn Erickson | Nov 18, 21:11 | |
| Herb Petschauer | Nov 18, 21:21 | |
| stephen joseph but… | Nov 18, 21:26 | |
| Jonathan Prescptt | Nov 20, 02:21 |






Cocoa mail archive

