Skip to content

nob_win64_mingw.c executable name variance. #119

Description

@nezvers

As my first experience with nob I tried building with Mingw64. I'm using the same version that came with Raylib installable setup.
I noticed that building stopped at compiling Raylib's *.os into an *.a and gave this error.

[INFO] CMD: x86_64-w64-mingw32-ar -crs ./build/raylib/win64-mingw/libraylib.a ./build/raylib/win64-mingw/rcore.o ./build/raylib/win64-mingw/raudio.o ./build/raylib/win64-mingw/rglfw.o ./build/raylib/win64-mingw/rmodels.o ./build/raylib/win64-mingw/rshapes.o ./build/raylib/win64-mingw/rtext.o ./build/raylib/win64-mingw/rtextures.o ./build/raylib/win64-mingw/utils.o
[ERROR] Could not create child process: 2

After checking content of my Mingw, I saw only x86_64-w64-mingw32-gcc-ar being the closest name.
Replaced here:

nob_cmd_append(&cmd, "x86_64-w64-mingw32-ar", "-crs", libraylib_path);

After that everything worked.
Dunno, maybe there's a way to check it's name?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions