Can't build 32-bit Cura (Windows 10 32-bit) #22
Comments
|
you need to get protoc3 precompiled binary from HERE and add the exe to your MinGW PATH to fix this, even i have been trying to build, i have gotten a lil further, but still not completed.. but lets see where it goes |
|
One issue I've encountered pretty often is that the Perl environment was defined before the MinGW and Python environment in the |
I got a bit further! Also changed path priority like you said. |
|
http://filehippo.com/download_visualc_2010_express_edition/ Install this to fix this issue, not sure why Mingw can't handle it ! On Wed, Dec 2, 2015, 15:57 mpbomil notifications@github.com wrote:
|
|
I'm working from a clean windows 10 installation and have installed all of the things listed in the original post. After installing vs2010 express the Protobuf-python still fails. Issue 1in Issue 2Immediately after the previous issue when it trys to link, it fails because of a missing library file. The initial makefile was created with |
|
You are creating MinGW makefiles and then proceed to compile with Visual Studio? CMake should have Visual Studio generators. All of Ultimaker's C++ code is designed to be compiled with GCC and MinGW. Protobuf is not Ultimaker's though, and should work with Visual Studio too. Perhaps they can help you out over at the Protobuf repository? Keep in mind that trying to link CuraEngine to Protobuf will probably give linker errors later on, if you try to compile the one with Visual Studio and the other with MinGW. |
|
The build scripts are invoking the visual studio compiler. Specifically the Protobuf-python repository. All I do is mingw32-make from the build directory. From your response I take it that VS compiler should not be used at all during the build process. If VS 2010 is not installed Protobuf-python still fails with the error in mpbomil's second comment. |
|
Well, we never tested it with VS2010. You could try to get it to work, but we simply can't help you there as we don't have any experience with getting Cura to build with any kind of VS compiler. |
|
isnt there any other quick fix to build a distribute exe for those(for now,including me) who are just changing the GUI? |
|
Didn't get it to work on windows, I've installed Ubuntu now and building went smooth as butter, maybe you could do that for now. |
|
Yeah! Ubuntu was sweet for me too! That's actually done.. Hit a dead end On Mon, Dec 7, 2015, 16:31 mpbomil notifications@github.com wrote:
|
|
The GUI is largely dependent on the QML files, which should not be packaged into the executable. If you modify those you can go far with the GUI, without having to compile or package the executable again. |
|
This might be too much to ask, but can anybody who has successfully built the package help us make one if i provide a git with modified code? The need to distribute custom packages is huge for us, even toh currently it's just UI modification.. Obviously we won't stop at that, we've contributed to the marlin firmware and cura is the last option as a host for us to integrate the features, please help |
|
Sorry, I don't have any other build scripts other than these. We use these scripts to create our releases. Could be that @awhiemstra has some tips for you. |
|
I was having the same problem as @mpbomil 19 days ago: I've gotten a little further by adding It's currently working on Qt. Hasn't failed yet! |
|
I'll just dump problems I've encountered here and their solutions. If you get an error that it can't find Qt while it's preparing PyQt, make sure you execute the env_win32.bat script from within the directory you're building in, which is not necessarily the folder where the batch script itself is at. |
|
Numpy mentions that it can only be built using the gfortran compiler from MSVC. I've just resorted to installing numpy and scipy with pip and disabling BUILD_NUMPY and BUILD_SCIPY in CMake. Disabling only Numpy but not Scipy doesn't work, which is probably a mistake in the CMakeLists.txt of cura-build. With that I could finally successfully build. Running the thing though results in python.exe crashing. |
|
Closing this issue due to inactivity. |
What I've installed:
How I try to build:
I get this error after ~10 minutes:
The text was updated successfully, but these errors were encountered: