some kind of error

[ROCK201888]

Haxe 4.3.1
Haxelib 3.3.0
openfl 9.2.1
lime 7.8.0

windows x64

[player-03]

I don't think Lime 7.8.0 is compatible with OpenFL 9+. Try updating Lime?

Also, since C++ code is involved, what version of hxcpp do you have?

[ROCK201888]

lol i fix it myself by using lime test neko instead of lime test windows

[player-03]

Yeah, Neko is nice for testing.

Just be warned that Neko isn't great for distribution. If you want to publish your game as HTML5, it's probably fine. But if and when you want to distribute a downloadable game, you'll want to get lime test windows working.

[ROCK201888]

then why lime test neko builded the game in the export

[player-03]

That's the default folder name.

To be fair, if someone has Neko installed, they can play your Neko game. But most people don't have Neko.

[ROCK201888]

so can i let them download the game with neko packaged in

[player-03]

That should work. Won't give as good performance as HL or C++, but if it's a lightweight game maybe that's fine.

[ROCK201888]

so 1 last question, how do i package it in (i make friday night funkin' i don't know how to control source that much)

[player-03]

Not sure, but I seem to recall that Lime does that automatically for HashLink apps. Might be worth a shot.

[ROCK201888]

bruh i just wanan know how to fix this lime test windows issue

[player-03]

I don't think Lime 7.8.0 is compatible with OpenFL 9+. Try updating Lime?

Also, since C++ code is involved, what version of hxcpp do you have?

[ROCK201888]

hxcpp 4.3.2
Haxe 4.3.1
Haxelib 3.3.0
openfl 9.2.1
lime 8.0.1
flixel 5.3.1

[player-03]

Does the same error happen when you run a Flixel demo?

[ROCK201888]

let me try

[ROCK201888]

it's the same

[player-03]

Hmm. I don't think you're rebuilding tools, but if you were, you'd need Visual Studio C++. Might be worth grabbing regardless.

Also, try lime setup windows and see if it has any suggestions.

[ROCK201888]

mmm i have vs c++ already

[ROCK201888]

so how to fix

[player-03]

It really should work if you have the right version installed. Maybe uninstall and reinstall from the C++ page.

[ROCK201888]

nothing changed

[player-03]

FNF still claims to need Haxe 4.1.5. (Would be nice if they'd fix that. Haxe 4.3 offers some excellent features.)

I don't see how the Haxe version could be the source of this issue, but at this point I don't know what else to try.

Edit: they also have some Windows-specific instructions.

For Windows, you need to install Visual Studio Community 2019. While installing VSC, don't click on any of the options to install workloads. Instead, go to the individual components tab and choose the following:

MSVC v142 - VS 2019 C++ x64/x86 build tools
Windows SDK (10.0.17763.0)

[Apprentice-Alchemist]

The easy fix would be to compile with -D lime_disable_gpu_hint.
The proper fix would be to figure out why your C++ compiler doesn't support _declspec.
One thing to try is to replace _declspec with __declspec here:

lime/src/lime/system/System.hx

Lines 39 to 40 in deecd6c

	_declspec(dllexport) unsigned long NvOptimusEnablement = 0x00000001;
	_declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1;

Although if you're using MSVC it should support _declspec unless something is passing /Za to the C compiler...

[ROCK201888]

now it give me this error

[Apprentice-Alchemist]

...are you using Mingw or something?
That error can only happen if you're using GCC/Clang instead of MSVC.

[ROCK201888]

let me retry...

[ROCK201888]

now this happens

[player-03]

Not sure why we never responded to that last one, but for the record, you can set environment variables from the system settings (just search the computer for "environment variable"). You'd make a new variable named MINGW_ROOT with the MinGW folder as the value.

But this is a year late and you probably either figured that out or moved on, so it's time to close this.