librelist archives

« back to archive

mailcore2 not 32bit compatible?

mailcore2 not 32bit compatible?

From:
Joe Keenan
Date:
2013-09-04 @ 20:18
I get a huge number of errors when trying to compile for 32 bit 
architecture, but none for 64 bit.  Is mailcore not 32 bit compatible, or 
do I have some build settings wrong?

Xcode 4.6.3 on OS X 10.8.4, using 10.8 as base SDK with a target of 10.6.

joe

Re: [mailcore] mailcore2 not 32bit compatible?

From:
Hoa V. Dinh
Date:
2013-09-04 @ 20:56
Could you show some of those errors? 

-- 
Hoa V. Dinh


On Wednesday, September 4, 2013 at 1:18 PM, Joe Keenan wrote:

> I get a huge number of errors when trying to compile for 32 bit 
architecture, but none for 64 bit. Is mailcore not 32 bit compatible, or 
do I have some build settings wrong?
> 
> Xcode 4.6.3 on OS X 10.8.4, using 10.8 as base SDK with a target of 10.6.
> 
> joe 

Re: [mailcore] mailcore2 not 32bit compatible?

From:
Joe Keenan
Date:
2013-09-04 @ 22:22
On Sep 4, 2013, at 4:56 PM, "Hoa V. Dinh" <dinh.viet.hoa@gmail.com> wrote:

> Could you show some of those errors?
> 
> -- 
> Hoa V. Dinh

mailcore2/src/objc/utils/MCOObjectWrapper.mm:19:24: Inconsistent number of
instance variables specified

@implementation MCOObjectWrapper {
    mailcore::Object * mObject;
}


mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:21: Use of undeclared 
identifier 'mObject'; did you mean 'cObject'?
mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:5: Comparison between NULL
and non-pointer ('int' and NULL)
mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:5: Member reference type 
'<anonymous enum at 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AERegistry.h:60:1>'
is not a pointer

- (void) dealloc
{
    MC_SAFE_RELEASE(mObject);
    [super dealloc];
}

@implementation MCOIMAPFetchFoldersOperation {
    CompletionType _completionBlock;
}

mailcore2/src/objc/imap/MCOIMAPFetchFoldersOperation.mm:69:9: Use of 
undeclared identifier '_completionBlock'


And so on....

joe

Re: [mailcore] mailcore2 not 32bit compatible?

From:
Hoa V. Dinh
Date:
2013-09-04 @ 23:13
Oh, I see, it's using the old Objective-C runtime, which doesn't allow 
declaration of ivar in implementation. 
It's not compatible with Mac 32bits.
It's only compatible with iOS 32bits.

-- 
Hoa V. Dinh


On Wednesday, September 4, 2013 at 3:22 PM, Joe Keenan wrote:

> 
> On Sep 4, 2013, at 4:56 PM, "Hoa V. Dinh" <dinh.viet.hoa@gmail.com 
(mailto:dinh.viet.hoa@gmail.com)> wrote:
> 
> > Could you show some of those errors?
> > 
> > -- 
> > Hoa V. Dinh
> > 
> 
> 
> mailcore2/src/objc/utils/MCOObjectWrapper.mm:19:24: Inconsistent number 
of instance variables specified
> 
> @implementation MCOObjectWrapper {
> mailcore::Object * mObject;
> }
> 
> 
> mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:21: Use of undeclared 
identifier 'mObject'; did you mean 'cObject'?
> mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:5: Comparison between 
NULL and non-pointer ('int' and NULL)
> mailcore2/src/objc/utils/MCOObjectWrapper.mm:33:5: Member reference type
'<anonymous enum at 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AERegistry.h:60:1>'
is not a pointer
> 
> - (void) dealloc
> {
> MC_SAFE_RELEASE(mObject);
> [super dealloc];
> }
> 
> @implementation MCOIMAPFetchFoldersOperation {
> CompletionType _completionBlock;
> }
> 
> mailcore2/src/objc/imap/MCOIMAPFetchFoldersOperation.mm:69:9: Use of 
undeclared identifier '_completionBlock'
> 
> 
> And so on....
> 
> joe 

Re: [mailcore] mailcore2 not 32bit compatible?

From:
Joe Keenan
Date:
2013-09-05 @ 00:21
On Sep 4, 2013, at 7:13 PM, Hoa V. Dinh <dinh.viet.hoa@gmail.com> wrote:

> Oh, I see, it's using the old Objective-C runtime, which doesn't allow 
declaration of ivar in implementation.
> It's not compatible with Mac 32bits.
> It's only compatible with iOS 32bits.

Well, considering that iOS only runs on 32bit ARM devices, it kinda hasta 
do iOS 32bit.  ;)

I've had other problems with the 32bit compiler not liking the new Obj-C 
syntax, I didn't know it also had problems with C++

Bummer

joe