@taotieren have you tried running make_x86_64.bat from cmd.exe and not powershell?
1 Like
Cheers!
I reinstalled windows10 and then configured the cmake environment variable.
Click make_x86_64.bat (using the cmd environment) to compile and package normally.
What is the reason for finding that using cmder or powershell compiles properly and cannot be packaged?
What do you need to do if you want to compile and package under cmder or powershell?
I mean, using cmder or powershell can compile normally (generate kicad*.xz) but not package (generate kicad*.exe).
Using cmd, you can compile (generate kicad*.xz) and package (generate kicad*.exe) normally.
Because the powershell and cmder environments do not call copydlls.sh, does the copydlls.sh have the problem of not executing (environment switching failed)
cmder is not even a shell afaik, it’s just a terminal wrapper that launches cmd or powershell underneath. Obviously difference is in the environment, not the shell.
That is not enough information, look into logs or error output to understand why copydlls.sh doesnt work.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.