Closed liudonghua123 closed 2 years ago
As specified in the workflow, there are a number of dependencies you need to install before running make -j$(nproc) mingw SKIPDEPEND=1 RELEASEBUILD=1
, and you need to use mingw.
See https://github.com/finalburnneo/FBNeo/blob/master/.github/workflows/nightly-release.yml#L83-L88
You might also need to do other steps, like downgrading pthread and the likes.
Yes, I have installed the dependencies via pacman -S msys2-devel base-devel binutils mingw-w64-i686-toolchain mingw-w64-i686-nasm zip wget
, and downgraded pthread
via pacman -U --noconfirm mingw-w64-i686-winpthreads-git-6.0.0.5203.9afaf1c2-1-any.pkg.tar.xz mingw-w64-i686-libwinpthread-git-6.0.0.5203.9afaf1c2-1-any.pkg.tar.xz
.
And I also have vs 2019/2022 community installed.
As i said, you also need to use mingw (as "msystem" in msys)
Thanks, I tried to execute make -j$(nproc) mingw SKIPDEPEND=1 RELEASEBUILD=1
in mingw32 shell. It seemed ok now.
I see the default shell is msys2, not mingw32,
and the build steps do not change the default shell.
I'm not a windows user so i don't know much about msys2. My understanding is that the different msystems (shells ?) will set environment variables in different ways, and if you don't use the mingw one(s), CC
and CXX
will refer to some executables with no access to all the mingw builtin functions.
I'm not a windows user so i don't know much about msys2. My understanding is that the different msystems (shells ?) will set environment variables in different ways, and if you don't use the mingw one(s),
CC
andCXX
will refer to some executables with no access to all the mingw builtin functions.
Thanks, now I get it. 😄
Hi, I tried to build locally according to the steps on https://github.com/finalburnneo/FBNeo/blob/master/.github/workflows/nightly-release.yml. But it failed with some errors like
error: '_tfopen' was not declared in this scope; did you mean ‘fopen’?
Any ideas about this?