search

Ultimaker / cura-build-environment

CMake project to build dependencies for Cura
GNU Affero General Public License v3.0
24 stars 55 forks source link

[WIN 10] Build Error python.exe not recognized as an internal or external command #67

Closed white-ghost3886 closed 4 years ago

white-ghost3886 commented 5 years ago

While Trying to build cura on window the following error occurred . error 2

errors My f:/max/dep/bin seems to be empty !

Ghostkeeper commented 5 years ago

Which generator have you been using in CMake? Could you try with nmake?

Also I'm not sure if CPython supports building with VS2019.

white-ghost3886 commented 5 years ago

uninstalled vs2019 and Now using vs2017 can't figure it out why python.exe and its dll are not copying to CMAKE_INSTALL_PREFIX dir .

white-ghost3886 commented 5 years ago

Which generator have you been using in CMake? Could you try with nmake?

Also I'm not sure if CPython supports building with VS2019.

using cmake as makefile generator and build with nmake !

Ghostkeeper commented 5 years ago

Yeah the nmake generator should be fine.

Do you know what that E:\Microsoft.Cpp.Default.props file should be? It's very strange to me that CMake would do anything in the root folder of your E drive.

nubnubbud commented 5 years ago

I'm getting the same issue. I'm on windows 10, and I have both VS 2019 and 2017 installed (as well as the 14.0 build tools, seeing as 2015 is no longer easily available otherwise). I have python 2.7 and 3.6 installed, and everything seems so be responding and in path.

I also used cmake as the makefile generator, and built with nmake, just as it instructs on the repo, however, where it's looking for my python.exe seems to vary from yours, as we have slightly different places to put them. Still, I don't think it's related to drives, and I get it repeatedly, despite restarts, adjusting system variables, and redownloading python, visual studio, and mingw

c1 c2

I'm no expert at building source code, so I probably can't help much, but I hope this is useful information.

JithuPG commented 5 years ago

I'm getting the same issue. I'm on windows 10, and I have both VS 2019 and 2017 installed (as well as the 14.0 build tools, seeing as 2015 is no longer easily available otherwise). I have python 2.7 and 3.6 installed, and everything seems so be responding and in path.

I also used cmake as the makefile generator, and built with nmake, just as it instructs on the repo, however, where it's looking for my python.exe seems to vary from yours, as we have slightly different places to put them. Still, I don't think it's related to drives, and I get it repeatedly, despite restarts, adjusting system variables, and redownloading python, visual studio, and mingw

c1 c2

I'm no expert at building source code, so I probably can't help much, but I hope this is useful information.

Hai @nubnubbud Can you see python.exe ,python3.dll,python35.dll in your %build-location% / Python-prefix\src\Python\PCbuild\amd64/

LipuFei commented 5 years ago

The current master branch uses Python 3.5 which can be built with VS 2015 but may not work with VS 2017 and later. AFAIK, VS2015 doesn't seem to work for Python 3.6, but VS2017 works. If you are using the master branch, a safe bet is to use VS2015.

See https://wiki.python.org/moin/WindowsCompilers for some extra info.

LipuFei commented 4 years ago

Closing this issue due to inactivity.