Getting Unangband/Angband from SVN and Compiling on Windows

[zaimoni]

That option doesn't appear when I right-click, and I can't figure out what to do from here. I'll attach a pic to show what appears on mine. Did I download the wrong thing? I hope not - that one took me 14 hours on dialup. Yoy. Any help will be greatly appreciated.

You are browsing the remote repository. Looking at the screenshot, I see that the right-click menu has a Checkout entry.

That is, you're ready for step 11.

[Anne]

Hmm... things didn't appear for me as Andrew explained them after step #6. It got fairly confusing at one point, and I may very well have clicked on the wrong thing along the way. I'll redo that and see what happens.

[Anne]

Okay, I redid everything after emptying out my Workspace folder.

In order to get to this point:
At step #9, I didn't get an option to fill in a custom label field. I clicked 'Next' anyway.
At step #10, I selected "trunk", then clicked 'Finish' and it immediately started downloading, showing "SVN Checkout - Checking out trunk" before I had a chance to do steps 11-13. It seemed like it was skipping straight to #14. Now, this step took an hour and a half or so, the same amount of time it takes me to download the precompiled game zip. Afterward, downloaded folders appeared in the Workspace folder on my hard drive.

And I'm back to where I posted that image. When I right-click and choose "Checkout" it tells me the files are already in my Workspace folder and asks if I want to replace them. So apparently I'm ready for the next step. Right-clicking the 'src' folder gives me the same choices as before, nothing resemling "Make Targets or Build".

Left-click the 'src' folder, choose File/New/ there are a couple of choices, "Project" and "Project..."
If I click "Project" it brings up a box called "New Project - create a new project resource, allows mw to specify a project name and 'Use default location' (the Workspace folder) is checked.
If I click "Project..." it brings up a box called "New Project - create a new project by checking out an existing project from a SVN repository."
I can't find anything like "Make targets" anywhere.

Up on top, if I click on Project, there are some "build" type things in there, but still nothing like "make targets".

There are command line (DOS-window) versions of SVN that are a lot more straightforward, especially if you are not planning to do development yourself.

Maybe I need to do this that way, then. Or some other way. I must have some other version of the Eclipse program than Andrew used for this tutorial. I have absolutely no programming knowledge to draw from. My goal is just to be able to compile the newest versions instead of waiting for precompiled versions for Windows, and maybe try a little sourcediving if I can make heads or tails of what I see in there. Definitely not development - I'd be utterly lost. lol. I don't suppose there are other tutorials or something out there that might show me how to do it another way, are there?

[Anne]

Images of what I'm seeing - forgot to attach these to the above post.

[zaimoni]

If I click "Project" it brings up a box called "New Project - create a new project resource, allows mw to specify a project name and 'Use default location' (the Workspace folder) is checked.
If I click "Project..." it brings up a box called "New Project - create a new project by checking out an existing project from a SVN repository."
I can't find anything like "Make targets" anywhere.

You have completed step #16 in a slightly unscripted way.

I'm guessing here (as I have a highly unintegrated development environment), but I think at this point you want to click "Project". However, I'd use the src subdirectory as the location. I'm not sure how you do steps 17 and 18 from where you are.

You get back on track at Step 19, when you instruct Eclipse how to make Unangband.

Clicking on "Project..." sounds like the new-style way to do step 11, but as you've completed step 16 you don't have to do that.

[zaimoni]

I must have some other version of the Eclipse program than Andrew used for this tutorial.

Absolutely. The original download link didn't work, after all; you had to locate the recommended current version of Eclipse to download.

[Anne]

Thanks, zaimoni, that sounds right. It seems like I'm needing to do things somewhat out of order, but maybe I can still get this thing working. I'll give it another shot tonight, and I'll be sure to cross my fingers.

[Pete Mack]

If you have MINGW installed, and you have set up a proper workspace, you can compile UnAngband directly from a DOS (cmd.exe) window.

1. Make sure that MINGW bin is in your path:

C:\> path=%path%;C:\mingw\bin

(Or wherever the mingw executables are installed)

2. cd (change directory) to your workspace (repository) directory
C:\> cd C:\Documents and Settings\anne\....\unangband\trunk\unangband\src

3. Build the program:
C:\Doc....\src> make -f Makefile.win

(If you don't have a workspace set up, install svn and follow the instructions for Vanilla, but using the unangband svn web address instead of the angband one. The instructions for Vanilla are at rephial.org.

[Anne]

Thanks, Pete. I'm still having trouble, so I'll give that way a shot.

[Anne]

Alrighty, trying the instructions from Pete, I got as far as #3. In the DOS window, once I was in the src folder, I typed "make -f Makefile.win" and it told me:
"'make' is not recognized as an internal or external command, operable program or batch file."

I had a look inside the folder, and 'Makefile.win' is indeed in there. Maybe I'm not actually using the DOS window? I went in using the Command Prompt window (Programs / Accessories / Command Prompt), which I believe should be the right thing - it certainly looks right for a DOS window. Any idea why it wouldn't be recognizing "make" as a command and what I might try?

[pav]

But do you have make.exe in PATH ?

[zaimoni]

Alrighty, trying the instructions from Pete, I got as far as #3. In the DOS window, once I was in the src folder, I typed "make -f Makefile.win" and it told me:
"'make' is not recognized as an internal or external command, operable program or batch file."

I had a look inside the folder, and 'Makefile.win' is indeed in there. Maybe I'm not actually using the DOS window? I went in using the Command Prompt window (Programs / Accessories / Command Prompt), which I believe should be the right thing - it certainly looks right for a DOS window. Any idea why it wouldn't be recognizing "make" as a command and what I might try?

You are using a command shell. It will pass as the DOS window.

Try typing the command line from step #19 in the command shell. The binary install of MingW32 make installs it under that command name.

If that still doesn't work, look at where the MingW32 binaries are installed; whatever looks like a make is what you want.

EDIT: if using Makefile.win, be sure to use MINGW=yes afterwards.

[Pete Mack]

Alrighty, trying the instructions from Pete, I got as far as #3. In the DOS window, once I was in the src folder, I typed "make -f Makefile.win" and it told me:
"'make' is not recognized as an internal or external command, operable program or batch file."

I had a look inside the folder, and 'Makefile.win' is indeed in there. Maybe I'm not actually using the DOS window? I went in using the Command Prompt window (Programs / Accessories / Command Prompt), which I believe should be the right thing - it certainly looks right for a DOS window. Any idea why it wouldn't be recognizing "make" as a command and what I might try?

That means you got step 1 wrong. cmd.exe still doesn't know where you installed MINGW make and gcc compilers. It needs to be installed in one of the directories in variable %path%.

If you need to check, just enter:
C:\> %path%

at the command prompt, and you will see a semicolon-separated list of the directories it's searching.

[zaimoni]

That means you got step 1 wrong. cmd.exe still doesn't know where you installed MINGW make and gcc compilers. It needs to be installed in one of the directories in variable %path%.

Almost.

It's much simpler to add that directory to the PATH. However, the binary installer does do this (I think); the problem is that the binary installer for MingW32 make has a moronic naming convention (it assumes you actually would *want* to prefer CygWin make to MingW32 make for a primary MingW32 install, so different name).

[Anne]

Okay, I -think- it worked. It certainly did something that caused a lot of lines of text to appear. If it did work correctly, would the old shortcut for the game still run the newly compiled version? Or do I need to find wherever it put the new version and make a new shortcut from that? (Urg, I hope I wasn't supposed to uninstall the old version before doing all this - I didn't.)


When I bring up the game by the old shortcut it says it's Unangband 0.6.2 - I don't know whether that should be a clue or not. The version I had on my computer before compiling this one was the last unreleased beta version. I'm sorry, I really am a newb at this. You're all being so patient with me. I really appreciate all this.