Linux i686 and x86-64

namtabmai · 2009-02-08T14:06:17

Hi, I'm trying to get Angelscript running on Linux, both on 32bit and 64bit, but without much luck at the moment. I'm currently running the latest SVN version as of yesterday, but I've tried before with the stable version with unsuccessful results. There are some issues with compiling on both platforms, firstly the in atomic.cpp. Looks like you've used a kernel header for your asCAtomic class which is a bit of a no-no according to the kernel developers, these functions/headers are only really meant to be used inside the kernel. I've changed it to use gcc built in atomic functions which seems to work o.k. for the few tests that do pass at the moment. See below for the changes. #include <asm/atomic.h> BEGIN_AS_NAMESPACE asDWORD asCAtomic::atomicInc() { return atomic_inc_and_test(value); } asDWORD asCAtomic::atomicDec() { return atomic_dec_and_test(value); } #include <asm/atomic.h> asDWORD asCAtomic::atomicInc() { return __sync_fetch_and_add(&value, 1); } asDWORD asCAtomic::atomicDec() { return __sync_fetch_and_sub(&value, 1); } I'm using test_feature to check Angelscript performs as expected, but I've had to change a few of the tests in order to get it to compile. The vector3 tests require scriptmath3d, but scriptmath3d needs new.h which I'm guessing is part of the MS CRT library? So for the moment I've just #ifndef __LINUX__ these tests out, perhaps once the rest of the code is working I'll look at trying to get this built as well. On 64bit I've also had to #ifdef out a few of the tests in test_registertype due to them using asCALL_CDECL. Anyway my current fail on 64bit is in test_stringscript testing script3, this seems to stem from the fact in asCContext::CallGeneric currentObject is NULL, so further on in scriptstring.cpp CScriptString::operator= is getting passed NULL for other. I'll do some more digging and see if I can work out the exact cause of this, but perhaps you might be able to point me in the right direction?

AngelCode Affiliates

Started by namtabmai January 23, 2009 06:37 AM

24 comments, last by WitchLord 15 years, 9 months ago

gargltk

125

February 08, 2009 10:35 AM

The only modification I made to the makefile is that I've added 'as_callfunc_x64_gcc.cpp' to the list of sources - the flag didn't exist in the first place. Anyway, adding '-fPIC' would have been my suggestion as well - I've seen this before with other libraries as well, and it's always been the way I fixed it.

jal_

122

February 08, 2009 10:37 AM

Ye, Vic, -fPIC was added by hangy on our local copy.

WitchLord

4,860

February 08, 2009 12:55 PM

Should I add -fPIC to the CXXFLAGS?

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

_Vicious_

330

February 08, 2009 01:01 PM

It wouldn't hurt for sure.

gargltk

125

February 08, 2009 01:03 PM

Yes, I think you should, will probably keep more duplicate bug reports from pouring in in the future :)

WitchLord

4,860

February 08, 2009 02:06 PM

Done. Thanks!

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Linux i686 and x86-64

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Linux i686 and x86-64

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines