Meson stopped working.

  • A_Player
    31st March Member 0 Permalink

    So, i saw the new version that came out for TPT, and when i tried to re-compile the game, on the "meson setup build-debug", meson said: "meson.build:1:0: ERROR: Meson version is 0.63.2 but project requires >=0.64.0"

     

    I tried updating it with pip --upgrade meson ninja, but it is still saying that it's on 0.63.2. Also tried updating pip, still no luck.

    Maybe reinstalling Meson can fix it? (I followed the instructions in How to compile TPT, like i always do when updating the game)

    Edited once by A_Player. Last: 31st March
  • LBPHacker
    31st March Developer 0 Permalink
    pip definitely has a very recent version (1.4.0 or something) so that can't be the problem. When you run the upgrade command, pip tells you what version it upgraded to, check that first, it's most likely 1.4.0. Rather, what I expect the problem to be is that when you run Meson, you don't actually run the one pip manages, but one that your package ecosystem manages. Debian Bullseye is on 0.56.2 (insane), your package ecosystem might be stuck on a version as old as 0.63.2 too.

    The solution here would be to make sure that you have only one Meson in only one ecosystem installed. You can check what gets executed when you type meson by running where meson (on windows) or which meson (on everything sane).
    Edited once by LBPHacker. Last: 31st March
  • A_Player
    31st March Member 0 Permalink

    when i run the upgrade command, pip tells it's on 1.4.0, but when i run meson, it just gets the 0.63.2 version, even when i upgrade pip

     Ok, while i was writing this, i tried to execute the upgrade meson again, and it did something, but it still says that it's on 0.63.2. After executing "where meson" (i tough it was which meson, since the forum didn't say about where meson, but it works now), it found 2 meson's installed.

     

    first one: C:\Program Files\Meson\meson.exe

    second one: C:\Users\(My User)\AppData\Local\Programs\Python\Python312\Scripts\meson.exe

    should i like, delete one of them, or is there a command to make it run only on one?

    Edited once by A_Player. Last: 31st March
  • LBPHacker
    31st March Developer 1 Permalink
    You should definitely have only one; I'd suggest deleting the one in program files, you can probably do it from the add/remove programs page in control panel.
  • A_Player
    31st March Member 0 Permalink

    Thanks, it works fine now, when i uninstalled it, in the "version", it said 0.63.2, so it was the "broken" one.

     

    EDIT: Sadly another error ocurred now, after compiling the game, i tried to place my modded elements from the other version, and ninja said that there was nothing to do, when there was. I tried to re-compile the game, and now it gives an error when compiling the elements.
    EDIT AGAIN: ok, it seems that the code of the game changed, and my materials were using the old code. But i didn't understand some of the things that changed. For example, in AMTR: /src/simulation/elements/AMTR.cpp(55): error C2065: 'BOUNDS_CHECK': identificador não declarado (Undeclared identifier or something like that, my system is in brazillian portuguese). What should i replace it for?

     

    Edited 2 times by A_Player. Last: 1st April