Alright, I give up, I'm a failer XP I needs help!

[Gatharoth]

Okay, so I've tried doing this a few times, in different ways. But I fail at it.

I'm trying to compile the latest version of minetest.

I'm running Windows 7 Home Premium, 64-bit.

I am using visual Studio 2010 Express.

I have followed the instructions on the readme.txt. But cannot compile minetest.

I seem to get a few errors when I try to build from Visual Studio.


INSTALL:
"Cannot open include file: 'zlib.h': No such file or directory"
"Cannot find C:/.../minetext.exe" (note: I'm censoring the location)
then a bunch of "error MSB3073" at the end.

ALL_BUILD:
"Cannot open include file: 'zlib.h': No such file or directory"
And a few warnings about
"warning C4355: 'this' : used in base member initializer list"

Any ideas on what I should do?

[sfan5]

You forgot to install the zlib Dev-Files

[Gatharoth]

There wasn't anything in the readme.txt about it. How do I install them?

I have downloaded everything in the readme. I have the zip files for the zlib125/dll, the irrlicht-1.7.2 and the minetest.
I also have the unzipped zlib-1.2.5, irrlicht-1.7.2, gettext, minetest. As well as the zlibwapi.dll and zlibwapi.lib

I have the CMake.

Edit: sorry wasn't paying attention, I put zlibwapi.map instead of .lib which is correct one I have.

Edit2: Alright, the ALL_BUILD built fine. its just the INSTALL now.
It is still saying that it can't find
""C:/Users/.../DIR/celeron55-minetest-0e8bd53/bin/Release/minetest.exe"."

[dannydark]

This usually means the all_build didn't go fine as that file is created when all_build is run.

What other errors are given? i.e. stacktrace etc, also in the error message is has "DIR/" <- does this folder actually exist or have you just edited your error?

EDIT: Also try running a rebuild on ALL_BUILD.

[Gatharoth]

The folder actually exists, I edited the error to remove information I'd rather not have public.

There was no errors when creating the all_build.

There is no stack trace errors.

Here's the log.

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

1>------ Rebuild All started: Project: INSTALL, Configuration: Release Win32 ------
1>  Building Custom Rule C:/Users/.../DIR/celeron55-minetest-0e8bd53/CMakeLists.txt
1>  CMake does not need to re-run because C:\Users\...\DIR\celeron55-minetest-0e8bd53-build\CMakeFiles\generate.stamp is up-to-date.
1>  CMake Error at src/cmake_install.cmake:34 (FILE):
1>    file INSTALL cannot find
1>    "C:/Users/.../DIR/celeron55-minetest-0e8bd53/bin/Release/minetest.exe".
1>  Call Stack (most recent call first):
1>    cmake_install.cmake:44 (INCLUDE)
1> 
1> 
1>  -- Install configuration: "Release"
1>  -- Up-to-date: C:/Users/.../DIR/celeron55-minetest-0e8bd53-install/doc/README.txt
1>  -- Up-to-date: C:/Users/.../DIR/celeron55-minetest-0e8bd53-install/doc/changelog.txt
1>  -- Up-to-date: C:/Users/.../DIR/celeron55-minetest-0e8bd53-install/doc/minetest.conf.example
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: The command "setlocal
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: "C:\Program Files (x86)\CMake 2.8\bin\cmake.exe" -DBUILD_TYPE=Release -P cmake_install.cmake
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: if %errorlevel% neq 0 goto :cmEnd
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :cmEnd
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :cmErrorLevel
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: exit /b %1
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :cmDone
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: if %errorlevel% neq 0 goto :VCEnd
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(113,5): error MSB3073: :VCEnd" exited with code 1.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========


Edit: All all_build does is this (rebuild)

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

1>------ Build started: Project: ALL_BUILD, Configuration: Release Win32 ------
1>  Build all projects
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========


[dannydark]

Ah ok that was much more useful ^_^ that error is usually linked with your files not all being either the same bit type i.e. 32bit/64bit (actually that's not entirely true as it can mean many things but this is usually the case).

Could you double check that all your included libs are pointing to the 32bit versions (as your compiling a 32bit version of minetest) and if not link them with the 32bit versions (in cmake) and that should hopefully fix your problem.

I usually compile a 64bit version of Minetest but that meant compiling all libs like zlib, irrlicht, openal etc for 64bit so you will need to keep that in mind if you do decide to try that.

Another thing you could try is starting up visual studio in administrator mode in case it is a permissions issue on that folder.

Let me know how it goes.

EDIT: Also your all_build log is incomplete well actually no it has the last line but issuing a rebuild should wipe the cache and compile all the files from scratch again so your log should be much longer which is weird :S

EDIT2: One more thing if you still get problems after this you might want to try out the MSVS11 which you can currently download for free and use it until end of April, now its a developer preview version so you may find some bugs but the logging system has had some nice improvements over MSVS2010 and provides much more detailed error messages.

[Gatharoth]

Could you double check that all your included libs are pointing to the 32bit versions (as your compiling a 32bit version of minetest) and if not link them with the 32bit versions (in cmake) and that should hopefully fix your problem.

I usually compile a 64bit version of Minetest but that meant compiling all libs like zlib, irrlicht, openal etc for 64bit so you will need to keep that in mind if you do decide to try that.

There's a 64bit version?? =O I thought there was only a 32bit version. Alright >.< guess I have to sort out whats 32bit and whats 64bit >.< I'd prefer to get the 64bit version.

And yeah, this is my first time compiling minetest.

[dannydark]

Could you double check that all your included libs are pointing to the 32bit versions (as your compiling a 32bit version of minetest) and if not link them with the 32bit versions (in cmake) and that should hopefully fix your problem.

I usually compile a 64bit version of Minetest but that meant compiling all libs like zlib, irrlicht, openal etc for 64bit so you will need to keep that in mind if you do decide to try that.

There's a 64bit version?? =O I thought there was only a 32bit version. Alright >.< guess I have to sort out whats 32bit and whats 64bit >.< I'd prefer to get the 64bit version.

And yeah, this is my first time compiling minetest.

No by default Minetest is 32bit, but you can compile it as 64bit on a 64bit system as long as you compile the libs as 64bit also, there is only a slight difference in speed to see any more noticeable improvements you will have to do a few code edits.

The main reason I compile in 64bit is because VS compiles a lot faster and it seems to play nicer on Win7/8, but as I said above as the code isn't wrote specifically for 64bit systems there isn't much difference without going through and making some edits, which I did....but now If I compile 32bit versions all hell breaks loose ^_^

[Gatharoth]

No by default Minetest is 32bit, but you can compile it as 64bit on a 64bit system as long as you compile the libs as 64bit also, there is only a slight difference in speed to see any more noticeable improvements you will have to do a few code edits.

The main reason I compile in 64bit is because VS compiles a lot faster and it seems to play nicer on Win7/8, but as I said above as the code isn't wrote specifically for 64bit systems there isn't much difference without going through and making some edits, which I did....but now If I compile 32bit versions all hell breaks loose ^_^

Okay >.< Care to help me? I've never compiled anything before. ^^;