Closed ciros88 closed 1 week ago
oopss.. sorry
you can use:
$ nss-config --version 3.104.0
@raedrizqie ure not getting the point: makensis is broken, it is not about printing the version itself
i think you need to run it under cmd
or powershell
?
i run it in msys2/mingw32/mingw64 shell (as it should be)
yes.. you can run cmd/powershell inside mintty
this is not the point, the issue is that makensis doesn't work in msys2 shell (where is supposed to, and also where i personally need it)
this is not the point, the issue is that makensis doesn't work in msys2 shell (where is supposed to, and also where i personally need it)
You can see this: https://www.msys2.org/docs/filesystem-paths/
Automatic Unix ⟶ Windows Path Conversion
is enabled by default.
@ArchGuyWu can you give me a proper context? exactly what is your suggested solution? have you tried it? thanks
@ArchGuyWu can you give me a proper context? exactly what is your suggested solution? have you tried it? thanks
Don't use "/" for arguments in unix shell.
"/" is used for path in unix system.
ok now makes sense, and:
makensis -version
v3.10
makensis -license
Copyright (C) 1999-2023 Nullsoft and Contributors ...
gives the right output, thanks
Description / Steps to reproduce the issue
mingw-w64-i686-nsis
ormingw-w64-x86_64-nsis
makensis /version
ormakensis /license
Expected behavior
display nsis version or license
Actual behavior
$ makensis /version
\Processing config: C:\msys64\mingw32\etc\nsisconf.nsh
\Can't open script "C:/msys64/version"
$ makensis /license
\Processing config: C:\msys64\mingw32\etc\nsisconf.nsh
\Can't open script "C:/msys64/license"
Verification
Windows Version
MINGW32_NT-10.0-22621
MINGW environments affected
Are you willing to submit a PR?
No response