openfl / lime

A foundational Haxe framework for cross-platform development
https://lime.openfl.org/
MIT License
759 stars 371 forks source link

some kind of error #1685

Closed ROCK201888 closed 4 months ago

ROCK201888 commented 1 year ago

Haxe 4.3.1 Haxelib 3.3.0 openfl 9.2.1 lime 7.8.0

image

windows x64

player-03 commented 1 year ago

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 commented 1 year ago

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

player-03 commented 1 year ago

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 commented 1 year ago

then why lime test neko builded the game in the export

player-03 commented 1 year ago

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 commented 1 year ago

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

player-03 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

ROCK201888 commented 1 year ago

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

player-03 commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

ROCK201888 commented 1 year ago

let me try

ROCK201888 commented 1 year ago

it's the same

player-03 commented 1 year ago

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 commented 1 year ago

mmm i have vs c++ already

ROCK201888 commented 1 year ago

so how to fix image image

player-03 commented 1 year ago

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

ROCK201888 commented 1 year ago

nothing changed

player-03 commented 1 year ago

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 commented 1 year ago

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: https://github.com/openfl/lime/blob/deecd6c6f872f2855a879d8006dfb97f63134f84/src/lime/system/System.hx#L39-L40 Although if you're using MSVC it should support _declspec unless something is passing /Za to the C compiler...

ROCK201888 commented 1 year ago

now it give me this error image

Apprentice-Alchemist commented 1 year ago

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

ROCK201888 commented 1 year ago

let me retry...

ROCK201888 commented 1 year ago

image now this happens

player-03 commented 4 months ago

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.