NPP sdl

[Nick]

For those who want to play the new NPP in linux and love the SDL port, here is what you need. Unzip,

cd src
make -f Makefile.std
cp nppangband ..

[jsv]

For those who want to play the new NPP in linux and love the SDL port, here is what you need. Unzip,

cd src
make -f Makefile.std
cp nppangband ..

Thanks.

By the way, you've packed compiled *.o files together with the source. So better command to run is

cd src
make -f Makefile.std clean nppangband install

[Nick]

By the way, you've packed compiled *.o files together with the source.

Aaarggh! Fixed now - and yes,

make -f Makefile.std install

in the src directory will do the trick.

[Soluzar]

Since I asked about SDL in regards to NPP in another thread, I must also ask here. Will this work to build a Windows/SDL version using Bloodshed Dev C++ at all? I'm able to compile Vanilla 3.1.1 with SDL using that compiler suite.

[nppangband]

Since I asked about SDL in regards to NPP in another thread, I must also ask here. Will this work to build a Windows/SDL version using Bloodshed Dev C++ at all? I'm able to compile Vanilla 3.1.1 with SDL using that compiler suite.

For NPP 0.5.0, I am not sure. But very soon, the answer will be a definite yes.

I have an updated version coming out that updates the core of NPP from Angband 3.0.6 to the current Angband 3.1.2v2 beta. It won't have all of the features yet, but it will have all of the updated makefiles, main-xxx files and all of the core files that make Angband run. That that point, anything that can compile the current Vanilla should compile NPP as well.

My target for releasing a beta is August 1. I am actually almsot done now, but I have a project at work that is going to keep me busy for the next two weeks. I want to hold off the beta release until I actually will have time to fix the problems people discover.

[nppangband]

For those who want to play the new NPP in linux and love the SDL port, here is what you need. Unzip,

cd src
make -f Makefile.std
cp nppangband ..

Thanks, Nick! Is this a version I should post on my site, or are these coding changes I should incorporate into the next release?

[Nick]

Thanks, Nick! Is this a version I should post on my site, or are these coding changes I should incorporate into the next release?

Simple to incorporate the changes, I think. There's a main-sdl.c, and small changes to externs.h, h-system.h, main.h, main.c, Makefile.std and variable.c. I can give more details later if you need them.

[nppangband]

Thanks again, Nick. I also posted a version in the NPP downloads section here:

http://download.nppangband.org/

There is also a version of the pre-alpha NPP 0.5.1. It is still unplayable, and is marked as such. I just wanted to have a backup out there somewhere in case my computer crashes. It is just NPP 050 with the Angband 3.1.2v2beta backbone, but no new gameplay features and plenty of bugs for me to fix before it is worth anybody's time.

[d_m]

There is also a version of the pre-alpha NPP 0.5.1. It is still unplayable, and is marked as such. I just wanted to have a backup out there somewhere in case my computer crashes. It is just NPP 050 with the Angband 3.1.2v2beta backbone, but no new gameplay features and plenty of bugs for me to fix before it is worth anybody's time.

I strongly recommend you create an account on bitbucket.org or github.org (depending on whether you prefer hg or git). It's free and pretty easy to use, particularly if you're the only person doing commits.

I definitely find that my personal development goes a lot smoother when I can commit at regular milestones. That way, when I change something around and totally break it, I can easily diff with the last known version just to see what happened. Often I am messing around and suddenly realize I care about the code--then I create a local hg repo and eventually move it to my bitbucket account if I want to "back it up".

I can give you more detailed instructions on how to do it in Mercurial if you want. It's pretty easy if you've used any other version control system.

[nppangband]

I strongly recommend you create an account on bitbucket.org or github.org (depending on whether you prefer hg or git). It's free and pretty easy to use, particularly if you're the only person doing commits.

I definitely find that my personal development goes a lot smoother when I can commit at regular milestones. That way, when I change something around and totally break it, I can easily diff with the last known version just to see what happened. Often I am messing around and suddenly realize I care about the code--then I create a local hg repo and eventually move it to my bitbucket account if I want to "back it up".

I can give you more detailed instructions on how to do it in Mercurial if you want. It's pretty easy if you've used any other version control system.

Thanks. Good advice. It was just that going frmo Angband 3.0.6 to the current source was such a large job, this was the first natural breakpoint I have had in a long while.

Actually, we do have one, here... http://www.assembla.com/wiki/show/NPPAngband, but Diego (my silent partner) is the one who maintains it. Now that he istaking a break, I will need to learn.

[AnonymousHero]

Ugh. Subversion.

I'd highly recommend using a distributed VCS instead (as in: Git, Hg or Bazaar). Much, much easier to do expirments when branches and merges are local + trivial to do.