https://linen.dev logo
Join DiscordCommunities
Powered by
# lime
  • g
    it only does it when i build it manually with the command line using this command
  • g
    since its been a while, this is about using hxScout while building through VS Code
  • r
    did you try 
    <define/>
    ?
  • g
    and i can't seem to find out how vscode handles the hxml files
  • g
    i might have?
  • g
    let me try it
  • b
    or 
    <haxedef name="telemetry" />
    ?
  • r
    as far as I know, vscode ignores hxml files when using Lime/OpenFL
  • g
    yeh thats the one i'd tried in the original question id asked earlier
  • g
    (referring to semmi's response)
  • b
    ah ... sorry was forgot or over-readit
  • g
    is alright
  • g
    hmm. do you think another problem would be the network port vscode uses?
  • b
    mhm, thats curious ... i mean that lime not correctly generating the hxml then
  • g
    hmm
  • g
    i fufill the conditions stated here (because the version requirements are very old)
  • g
    and ive got this
  • g
    maybe the location of the define is important?
  • g
    in the XML?
  • b
    not sure this works .. but remember i did some times long ago something like this: 
    <haxeflag name="-D" value="telemetry" />
    (not for "telemetry" but roughtly remember for something)
  • g
    yeah thats what I did when i tried haxeflag
  • g
    its weird it didnt work
  • b
    yep ... not sure what it was into the past here by me and with openfl at that time
  • g
    it creates a xml when it exports
  • g
    and i can see it there
  • b
    mhm, then it works by lime->project.xml
  • b
    but why not later into build-chain ?
  • g
    hmm something i noticed compared to building it manually with command line
  • g
    the resulting hxml doesnt have some of hte stuff thats supposed to be automatically set up
  • g
    lemme put those things in myself and see if it corrects it
1...676869...138Latest