Compliation error

  • CATSSMAC
    4th November Member 0 Permalink

    what caused this error? ANd also how to fix it, I didnt see this in the compilation wiki, which really should include more on troubleshooting.

    MYREALNAME@MYPC UCRT64 ~/The-Powder-Toy
    $ meson compile -C build-debug
    INFO: autodetecting backend as ninja
    INFO: calculating backend command to run: C:\msys64\ucrt64\bin/ninja.exe -C "C:/msys64/home/MYREALNAME/The-Powder-Toy/build-debug"
    ninja: Entering directory `C:/msys64/home/MYREALNAME/The-Powder-Toy/build-debug'
    [1/18] Linking static target libsimulation.a
    FAILED: [code=1] libsimulation.a
    "gcc-ar" "csrDT" libsimulation.a @libsimulation.a.rsp
    C:/msys64/ucrt64/bin/../lib/gcc/x86_64-w64-mingw32/16.2.0/../../../../x86_64-w64-mingw32/bin/ar.exe: libsimulation.a: No such file or directory
    [14/18] Compiling C++ object powder.exe.p/src_lua_LuaInterface.cpp.obj
    ninja: build stopped: subcommand failed.

     

    Im using MingW UCRT64 :P

  • jacob1
    4th November Developer 0 Permalink
    Is this all the logs, or only selected parts of it? If it's not all, try pasting the whole thing (with redacted username)

    Is this the new compiler you just installed from the guide, or an older compiler you had sitting around?

    The error is kind of weird, it looks like a compiler glitch or some kind of filesystem issue. It really shouldn't be saying "no such file or directory", that's not a code issue ...
  • CATSSMAC
    4th November Member 0 Permalink

    jacob1:

    Is this all the logs, or only selected parts of it? If it's not all, try pasting the whole thing (with redacted username)

    Is this the new compiler you just installed from the guide, or an older compiler you had sitting around?

    The error is kind of weird, it looks like a compiler glitch or some kind of filesystem issue. It really shouldn't be saying "no such file or directory", that's not a code issue ...

     
    this is just what the terminal gave after doing the meson compile command...  though Im not sure if theres some other logs behind this 

    EDIT- I managed to fix it, by removing libsimulation.a inside build-debug, so it regenerated it after recompilation :D I never removed some files, so I am guessing it was in some sort of broken state.

    Edited 2 times by CATSSMAC. Last: 4th November