https://linen.dev logo
Join DiscordCommunities
Powered by
# lime
  • s
    yes that's the issue, that only disables traces for my own code
  • s
    the haxelibs still trace stuff
  • b
    also by something like "if"="release" or specific target for
  • b
    ah, so its lib-specific ?
  • b
    you can't do that, flags are set universally for all code in a given haxe compilation
  • s
    apparently yes
  • s
    why does my libs still trace then
  • b
  • b
    wait, so you set 
    no-traces
    but it's still tracing?
  • s
    the haxelibs still trace
  • s
    only the traces from my own project are disabled
  • b
    ah, then you have to use no-traces like CRobes sayed or look into documentation of the specific library how to disable it there
  • b
    (
    --no-traces
    )
  • b
    or -> 
    <haxeflag name="--no-traces" unless="debug" />
    inside of project.xml
  • s
    that's what i had
  • b
    or also: 
    <haxeflag name="--no-traces" if="release" />
    ;:)
  • s
    🥹
  • b
    What's that lib what is doing so much traces ;) = ?
  • s
    see, flixel is still tracing stuff
  • b
    aahhh ^^
  • b
    thats an error - msg ... would ask the flixel-team for what this is (asset problem!)
  • s
    i do know its an problem with not finding assets
  • s
    but that's not the issue, the thing is, its still tracing stuff even when i use the no traces define
  • s
    i made that in purpose to test if it would still trace
  • b
    is the file not inside asset folder ? (or named "voices.ogg" instead of "Voices.ogg" or something)
  • s
    .
  • b
    or try 
    exclude="Voices.ogg"
    inside of 
    <assets ..>
    (maybe the path)
  • s
    yes but Voices.ogg is not the problem
  • b
    o k
  • s
    i made that error in purpose to see if flixel would still trace on release mode
1...606162...138Latest