Jump to content
  • Advertisement
Sign in to follow this  
rviney

as_callfunc_arm_xcode.s should be .S?

This topic is 2503 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I'm not sure about this, but I think as_callfunc_arm_xcode.s should really be as_callfunc_arm_xcode.S because it uses preprocessor commands and isn't pure assembly.

My build system (SCons) was doing the wrong thing because of the above issue, changing it to .S made it work.

Thanks,
Richard

Share this post


Link to post
Share on other sites
Advertisement
This was changed to small .s because xcode used it that way. When it was .S xcode failed to compile it.

Perhaps you should use as_callfunc_arm_gcc.S with SCons instead?

Share this post


Link to post
Share on other sites
I tried as_callfunc_arm_gcc.S originally but it fails to compile when building for iOS. I definitely need the changes made in the _xcode version, specifically changing .global to .globl, adding ".align 2", and prefixing the symbols with an underscore.

Am I right to guess that as_callfunc_arm_gcc.S is useful when building on Linux or other platforms? Because it doesn't seem to be a good match for iOS at the moment.

I just tested building as_callfunc_arm_xcode.S (with a big S) in Xcode targeting an iOS device and it compiles fine, the upper/lower case S doesn't seem to make any difference to Xcode.

Maybe as_callfunc_arm_xcode.s should be called as_callfunc_arm_mac.S instead? Because it's really the underlying platform/toolchain that's important, not the choice of IDE.


Hope that makes some sense!

Share this post


Link to post
Share on other sites
With Xcode accepting it either way I see no reason why not to change the file name (done in rev 1157). I guess either Apple updated Xcode, or the previous report that it only worked with .s was wrong, but it doesn't really matter now, does it? :)

Thanks,
Andreas

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!