Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nob_win64_mingw.c executable name variance. #119

Open
nezvers opened this issue Jul 26, 2024 · 1 comment
Open

nob_win64_mingw.c executable name variance. #119

nezvers opened this issue Jul 26, 2024 · 1 comment

Comments

@nezvers
Copy link

nezvers commented Jul 26, 2024

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?

@Markos-Th09
Copy link
Contributor

Markos-Th09 commented Aug 6, 2024

This was my bad and it was fixed in #99 but it wasn't been merged yet. Distribution of mingw for windows don't include all the prefixed binaries for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants