Compiling help: i don't know why this happens

[Slein9]

[x] Windows
[ ] Linux
[ ] Mac

[moxie-coder]

use Haxe 4.3 instead

[Slein9]

use Haxe 4.3 instead

i tried, but when i'm using haxe 4.3 i'm getting this

[moxie-coder]

did you try running the setup files?

[Slein9]

did you try running the setup files?

what's setup files? like update.bat?

[r6915ee]

Chipping in real quick; that's the source code for v1.0.1, not the development branches. You're free to keep it at Haxe v4.2.5, because v4.3.7 is only used for Codename's development branches at the moment, though I don't entirely remember what happens if you use v4.3.7 on v1.0.1.

That being said, yes, update.bat is one of the setup files. You should run it to get all of Codename's dependencies installed.

[Slein9]

Chipping in real quick; that's the source code for v1.0.1, not the development branches. You're free to keep it at Haxe v4.2.5, because v4.3.7 is only used for Codename's development branches at the moment, though I don't entirely remember what happens if you use v4.3.7 on v1.0.1.

That being said, yes, update.bat is one of the setup files. You should run it to get all of Codename's dependencies installed.

yes, i did run update.bat and did everything that README.md says

[r6915ee]

yes, i did run update.bat and did everything that README.md says

In that case, since you switched Haxe versions, you may want to try first removing the .haxelib directory in the repository and then rerunning the script. That should help clear up some of the cache and hopefully assist with the type errors you're receiving in the log.

[Slein9]

yes, i did run update.bat and did everything that README.md says

In that case, since you switched Haxe versions, you may want to try first removing the .haxelib directory in the repository and then rerunning the script. That should help clear up some of the cache and hopefully assist with the type errors you're receiving in the log.

that didn't help.

[r6915ee]

that didn't help.

Do you have Git accessible in $PATH, in that case? It should be available if you run git in the same session as running the setup scripts.

You may also want to install NekoVM if you haven't already. That is a core dependency for most Haxelibs, particularly runnable Haxelibs.

[Slein9]

that didn't help.

Do you have Git accessible in $PATH, in that case? It should be available if you run git in the same session as running the setup scripts.

You may also want to install NekoVM if you haven't already. That is a core dependency for most Haxelibs, particularly runnable Haxelibs.

yes i have Git accessible in $PATH and neko installed

[r6915ee]

What happens when you run lime build windows instead?

[Slein9]

What happens when you run lime build windows instead?

same thing

[r6915ee]

same thing

In that case, what do you get when you run haxe --version? What is the output of dir .haxelib?

[Slein9]

same thing

In that case, what do you get when you run haxe --version? What is the output of dir .haxelib?

i'm using haxe 4.2.5 because you told me that i can do so

and this is what i get after running dir .haxelib

[r6915ee]

i'm using haxe 4.2.5 because you told me that i can do so

and this is what i get after running dir .haxelib

In that case, did you make any changes to the project.xml? If so, what would be those changes?