Replies: 2 comments
-
|
The correct command is: The script set Note: |
Beta Was this translation helpful? Give feedback.
-
|
There's a lot to respond to here.
You haven't used the same command. It uses
Looks like the
I don't see any hardcoding to
With Visual Studio.
I'm a bit confused by this comment, the only place we really use it is in the CI which shows you exactly how to build it: premake-core/.github/workflows/ci-workflow.yml Lines 82 to 120 in 5c440ef
Glad you found the correct command in the end.
As above, what you have and what PKGBUILD uses weren't the same. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I used the same command as in the PKGBUILD of MSYS2's premake package:
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-premake/PKGBUILD
premake-bootstrap.exe is generated and it attempted to build premake5.exe, but I found it's building for
release_win32and of course it will fail to link needed libraries, because my toolchain is x86_64 and not support multilib, so there is no x86 libraries.The errors are like this:
I inspected the Bootstrap.mk file. I changed the command to be like the suggested in it:
Snippet:
But I found it's still generating for x86:
(extracted from the terminal output)
And
makefailed very quickly becauseMakefile:78: *** "invalid configuration x64_win32". Stop..What's going on? Even the embedded instruction in Bootstrap.mk is invalid.
Update: I found that you are hardcoding it to target x86:
Why? And how can I change this behavior without having to edit Bootstrap.mk? How do you make binary builds for Windows? I found that you are also using MSYS2.
Beta Was this translation helpful? Give feedback.
All reactions