Page 5 of 10

Re: XL Engine source code release!

Posted: 06 Apr 2018, 10:36
by Zini
That exception is the result of using new[] with a funky array size. Unfortunately there is a lot of macro stuff in there which makes debugging harder, but the Open function has several new statements. I would check which of them is used with an weird size (either via debugger or by couting the value).

Re: XL Engine source code release!

Posted: 07 Apr 2018, 00:37
by psi29a
I think we've made some major progress... :)

Re: XL Engine source code release!

Posted: 07 Apr 2018, 04:11
by Chris
psi29a wrote: 07 Apr 2018, 00:37 I think we've made some major progress... :)
Indeed.
screenshot.png

Re: XL Engine source code release!

Posted: 07 Apr 2018, 05:51
by raevol
Wow nice!!!

Re: XL Engine source code release!

Posted: 07 Apr 2018, 12:38
by drummyfish
OMG it's beautiful.

Re: XL Engine source code release!

Posted: 07 Apr 2018, 15:58
by magamo
I'm unfortunately unable to get this to compile. I installed the libdevil-dev and libdevil1c2 packages into my Ubuntu 16.04 development environment. Is 16.04's version of GCC just not new enough at this point for the current codebase?

EDIT: It would appear so -- If I initialize an ubuntu 18.04 development environment, XLEngine compiles cleanly.

Re: XL Engine source code release!

Posted: 07 Apr 2018, 17:32
by psi29a
What does it complain with?

We are using plain old C++ at this point, even new and delete... no smart pointers. Nothing special.

Re: XL Engine source code release!

Posted: 07 Apr 2018, 19:46
by magamo
stderr stream attached.

Re: XL Engine source code release!

Posted: 07 Apr 2018, 20:03
by psi29a
what's your gcc version?
That's should be available in C++11, maybe we need to set that in cmake?

Re: XL Engine source code release!

Posted: 07 Apr 2018, 20:05
by afritz1
Seems it is already using C++11 features as part of the fixing-up process (std::string::back(), std::string::pop_back(), std::stoi()), so just pass -std=c++11 and it should compile. Alternatively those pieces of code could be replaced with older features, but ultimately I think the project is going to be using C++11 anyway.