https://linen.dev logo
Join Discord
Powered by
# lime
  • g
    here
  • b
    hashlink likes only my haxe-spice or what ?
  • b
    Nooosh... pls tell YOU me how to make my haxecode -> pure C again !
  • b
    (throught)
  • g
    it seems the file is there
  • g
    im not sure what its lookin for htough
  • b
    is this your 
    default
    ming-w[shit] color-setting ?
  • g
    not sure what you mean here
  • b
    what you are working on at now
  • b
    For -Wcpp: try changing
    Copy code
    <cppflag value="-std=c++11" if="HXCPP_CPP11" />
<cppflag value="-U__STRICT_ANSI__" />
    to
    Copy code
    <cppflag value="-std=gnu++11" if="HXCPP_CPP11" />
    and make sure HXCPP_NO_CPP11 is not defined (https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=767537a8b027bcb5807bb45b0268c5da98c2c7a0)
  • b
    ah, you and @gray-vase-27987 working on same ComputerProgram ?
  • b
    I'm trying to help him get gdb working so he can find out what the uncaught segfault really is
  • g
    hi where would i make this change
  • b
    Mingw-toolchain.xml
  • g
    ah i see
  • b
    so 3 problems at now ... open AL ... haxedefine (telemetry?) and this on TOP ?
  • g
    the one in the haxelib library?
  • b
    really ?
  • b
    Yeah in hxcpp
  • b
    understanding
  • g
    alright found it
  • b
    (pls tell me your TARGET at first into haxe)
  • b
    (if you only using ONE only)
  • g
    windows. cpp
  • b
    haxe
    == multilanguage 
    GENERATOR
  • g
    vscode calls it "Windows / Debug"
  • g
    one of the configurations
  • b
    vscode -> single
  • g
    i just ran 
    lime build windows -debug -D toolchain=mingw
  • g
    you know what lemme put the haxedef back in the project xml
1...757677...138Latest