Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make script crashes when compiling Kha project #814

Closed
AndrewBelt opened this issue May 9, 2018 · 5 comments
Closed

Make script crashes when compiling Kha project #814

AndrewBelt opened this issue May 9, 2018 · 5 comments

Comments

@AndrewBelt
Copy link

AndrewBelt commented May 9, 2018

Hello. I am unable to compile an empty Kha project with Arch Linux, Node v10.0.0, and Kha 2765735.

Initializing the Kha project is fine.

~/src/empty ❯ node ../Kha/make --init
Initializing Kha project.

If you want to use the git version of Kha, execute "git init" and "git submodule add https://github.com/ktxsoftware/Kha.git".

But it fails immediately when building.

~/src/empty ❯ node ../Kha/make
node[8059]: ../src/node_contextify.cc:631:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed.
 1: node::Abort() [node]
 2: 0x563647ad29db [node]
 3: node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [node]
 4: v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo*) [node]
 5: 0x563647ce7ba7 [node]
 6: 0x563647ce833c [node]
 7: 0x712dcc0427d
zsh: abort (core dumped)  node ../Kha/make

The Kha v17.1 tag seems to work, however.

@sh-dave
Copy link
Contributor

sh-dave commented May 9, 2018

Can you build the test projects included in Kha?

cd Kha/Tests/Empty
node ../../make

@sh-dave
Copy link
Contributor

sh-dave commented May 9, 2018

Also reading the error you get and this one here it might be a nodejs issue. Can you downgrade to 9.x and try that?

@AndrewBelt
Copy link
Author

Same error for the Empty project (since they're identical files I think) with Node v10.

Confirmed that Node v9.11.1 works fine.

@RobDangerous
Copy link
Member

ok, updating the dependencies fixes that but introduces other problems. I'm on it...

@RobDangerous
Copy link
Member

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants