• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
UltimateWalrus

Marmalade: Angelscript runs fine on x86, crashes on ARM

35 posts in this topic

Great to hear it is finally working.

Do let me know if you encounter other problems.

I'll probably have to include a Marmalade makefile for the AngelScript library, especially since it is not so straightforward to figure out how to configure it.
0

Share this post


Link to post
Share on other sites
Yep, it's working, and I'm finally able to run AngelScript on device using CDECL calling conventions. :]

Thanks a ton for all your help. Attached is a complete Marmalade project that implements "Hello World" by calling a print function from AngelScript, and runs just fine on devices without the asCALL_GENERIC workaround. Should save some time if anyone else needs to get AngelScript/Marmalade working in the future. You're welcome to reference it if you wanna put Marmalade makefiles in the AngelScript library.
1

Share this post


Link to post
Share on other sites
Hi everyone,

I want to say a big thank you to all of you for your hard work in getting AngelScript to work on Marmalade. Unaware of UltimateWalrus's latest posts, I spent some time last week integrating AngelScript into Marmalade, and have put together yet another integration of AngelScript and Marmalade: [url="https://github.com/mstarinc/angelscript-marmalade"][b]angelscript-marmalade[/b] project on GitHub[/url].

It seems to be working well on MSVC/x86, VS/GCC-ARM, XCode/Clang/x86, XCode/GCC/x86, XCode/ARM, and Scons/ARM. I've included portable binaries in the distribution so that it can be used right away. If one does want to [re-]compile it, it should compile easily and run with native calling conventions on Marmalade Windows, Marmalade Mac, or Marmalade ARM. (Although due to the presence of the ".S" files, one line of the MKB must be commented out before it will compile with Visual Studio). I made sure that the AngelScript code is completely unmodified; in fact, if you use the MKB to build the project, it will download the unmodified source upstream code as part of the build process.

I'm just getting started with AngelScript, but everything looks very promising so far. Just wanted share my code and to say thanks [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
0

Share this post


Link to post
Share on other sites
Hi Braden,

thanks for sharing your work and for letting us know that it works on all these different platforms.

There are now quite a few projects using AngelScript with Marmalade. [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]

I see that you use a couple of predefines to determine the target platform, i.e. I3D_ARCH_X86 and I3D_ARCH_ARM. How did you find out about these? It looks like something I can use directly within the as_config.h so it wouldn't be necessary to define anything other than MARMALADE from the project files.

Actually perhaps I can even use the existance of I3D_ARCH_X86 or I3D_ARCH_ARM to identify that the library is being compiled for Marmalade, in which case it wouldn't be necessary to define anything at all from the Marmalde makefile.

Regards,
Andreas Edited by Andreas Jonsson
1

Share this post


Link to post
Share on other sites
That is an excellent idea: You could use (I3D_ARCH_X86 || I3D_ARCH_ARM) as a test for the Marmalade platform. It would be nice to remove the predefines from the MKB makefile if possible. I found out about these defines from the Marmalade forum; they are not in the documentation, although they have been around for a long time. (Unfortunately there are quite a few of these little Marmalade "tricks" that are completely undocumented except for the occasional insightful forum post from Marmalade staff.)

Edit: It's worth mentioning that Marmalade also supports other platforms (although they're not nearly as popular as x86 and ARM); their preprocessor definitions are: I3D_ARCH_AMD64, I3D_ARCH_MIPS, I3D_ARCH_PS3, I3D_ARCH_X360, and I3D_ARCH_PSP. I've never worked with any of those other platforms. The full list of symbols can be seen in the "temp_defines_debug.h" file that Marmalade's makefile_builder creates during the build process.

Edit 2: Upon looking at that file further, I see that you could also detect the Marmalade platform by looking for "IW_SDK", "__S3E__", or any number of other definitions. Check out [url="https://gist.github.com/4211333"]this copy of an example temp_defines_debug.h[/url] file to see. Edited by Braden M
1

Share this post


Link to post
Share on other sites
Great. It looks like __S3E__ is a useful define to look for to identify Marmalade. With this it should no longer be necessary to manually define Marmalade anywhere. I3D_ARCH_ARM and I3D_ARCH_X86 etc will be used to determine for which CPU the library is compiled, and will control the code for the native calling conventions.

I'll make the necessary changes in the as_config.h, and let you know when it's checked in.
0

Share this post


Link to post
Share on other sites
I've checked in the changes in revision 1490.

It should no longer be necessary to make any defines to compile AngelScript for Marmalade. Please give it a try and let me know if there are any problems.

Based on the tests that UltimateWalrus had made, I configured Marmalade to use the same ABI as is used for Android. It's possible that later on you'll find some functions that don't work properly if this assumption is incorrect. If that happens, please tell me and I'll make the necessary changes in the library.
0

Share this post


Link to post
Share on other sites
Thanks Andreas! I really appreciate how responsive you are with fixes to AngelScript. I just tried out r1490 and it works perfectly as far as I can tell. I've put the new MKB in [url="https://github.com/mstarinc/angelscript-marmalade/tree/angelscript2.26"]a separate branch[/url] for now, and I'll update "master" once 2.26 is released. The only "tweak" that I had to leave in was a definition of "fopen_s" that I put in preinclude.h, because Marmalade's standard library doesn't have that function available, even in Visual Studio.

Also, FYI, there are two compiler warnings that come up with Marmalade's ARM GCC4.4 (arm-none-eabi-g++); the first one looks like it could possibly affect bytecode output so I'll mention it in case you weren't aware of it.

[CODE]
angelscript/source/as_bytecode.cpp: In member function 'void asCByteCode::DebugOutput(const char*, asCScriptEngine*, asCScriptFunction*)':
angelscript/source/as_bytecode.cpp:2114: warning: format '%3d' expects type 'int', but argument 3 has type 'long unsigned int'


add_on/scripthelper/scripthelper.cpp: In function 'int WriteConfigToFile(asIScriptEngine*, const char*)':
add_on/scripthelper/scripthelper.cpp:194: warning: format '%X' expects type 'unsigned int', but argument 3 has type 'asDWORD'
[/CODE]
The second warning occurs a total of ten times at different lines in scripthelper.cpp.
0

Share this post


Link to post
Share on other sites
Thanks, these last issues should now be fixed in revision 1493.

You should not need the fopen_s tweak anymore. I had forgotten a few places were I was using fopen_s. These are in either case only used when compiling the library in debug mode.
0

Share this post


Link to post
Share on other sites
Hi Andreas, I just found two more places where fopen_s is still causing that error even with the latest revision (if I omit the preinclude.h file) - both in add_ons:

scriptfile/scriptfile.cpp (line 320)
scripthelper/scripthelper.cpp (line 169)
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0