Jump to content

  • Log In with Google      Sign In   
  • Create Account

#Actualandrew1b

Posted 10 December 2012 - 02:19 PM

I just ran the testbed on mac os x and here is what I found:

-Everything passes without AS_MAX_PORTABILITY, but not when it is defined (I tested on 32-bit only)
-The AS_IPHONE option keeps being defined even on the project I created from scratch (asGetLibraryOptions returns AS_IPHONE AS_X86!)

When I build my project without AS_MAX_PORTABILITY, it won't crash at the spot I mentioned above, but it crashes when I try to use some of the operators in my vector2 object. The crash this time would happen in the as_callfunc_x86.cpp, which I would guess has something to do with the definition of AS_IPHONE.

Edit: there's a great chance the iphone macro confusion is xcode's fault. I'm still looking into the issue.

#1andrew1b

Posted 10 December 2012 - 01:48 PM

I just ran the testbed on mac os x and here is what I found:

-Everything passes without AS_MAX_PORTABILITY, but not when it is defined (I tested on 32-bit only)
-The AS_IPHONE option keeps being defined even on the project I created from scratch (asGetLibraryOptions returns AS_IPHONE AS_X86!)

When I build my project without AS_MAX_PORTABILITY, it won't crash at the spot I mentioned above, but it crashes when I try to use some of the operators in my vector2 object. The crash this time would happen in the as_callfunc_x86.cpp, which I would guess has something to do with the definition of AS_IPHONE.

PARTNERS