you can set versions for haxelib dependencies in haxelib.json but typically a lime project isn't a haxelib

i am like 90% sure it is, i've already done it

ah here!

xml
<haxelib name="actuate" version="1.0.0" />

thank you!

got this error while trying to compile lime with mingw

that's funky, isn't mingw just like gcc but for windows

coming from here

this line more specifically

cpp
_declspec(dllexport) int AmdPowerXpressRequestHighPerformance = 1;

lime compiled fine for me using gcc on linux

but again maybe that's because it was an older lime version

trying to compile for release to see if that happens

yep, it happened on release too

i'll try maybe deleting the hxcpp cache, even if lime is not there

idk

nope, same error.

i'll try to downgrade a version to see if its an issue with the newest release

i hope this is reasonable thing to ask but I've got a few things about lime I'm curious of. just trying to learn more about the tools I'm using. 1. is there any way (when compiling through VS Code's "Start Debugging") to ask it to use additional command line arguments? I've been wanting to use hxScout, though that requires adding

-D telemetry

and due to my lack of experience I'm having trouble finding where to put it 2. is there any good documentation or guides for Haxe's implementation of OpenAL? I've been interested in using the audio effects but I'm having trouble finding anything that tells me what I need to know. I do have openAL's general documentation and it does give some things but it's very long and it's hard to find information relevant to what I'm looking to do

-D telemetry

goes in the hxml

but since its lime, its in the project.xml

how do i put it in the XML? I remember trying that but I might have used the wrong tag or something

lemme check what i used

i did it this way

well test it ig

hm?

I've been studying openAL all day...

openal works good inside of lime (also mojo)

mojo?