Furyband codebase

[Zop]

I am always surprised to see people still playing Furyband. Perhaps it was more popular than I realized!

Anyway, Fury, the creator, seems to have abondoned the project years ago. I feel a bit of responsibility for the code, since I was working with Fury last. so I started a base at github: link

If there are any bugs or feature requests, I'd like to implement them before my classes begin in September. Or let me know of any thoughts about this.

[krazyhades]

[eight more characters and then some for posting requirements]

[Nick]

Excellent news

[HugoVirtuoso]

How about a Windows / Mac compiled binary for us all to test with?

[nikheizen]

How about a Windows / Mac compiled binary for us all to test with?

Looks like it's right in the repo itself: "CompiledWindows08JULY2016.zip"

[getter77]

Always good to see some life in this!

[Zop]

Hugo, I took a quick look into compiling a Mac binary from Windows, and it looks problematic and barely possible. The main issue is that I won't be able to test what I compile.

The file I uploaded, AllSources.zip, has a makefile for Mac (makefile.osx), but I don't know what one would need to install in order to compile it.

[HugoVirtuoso]

Hugo, I took a quick look into compiling a Mac binary from Windows, and it looks problematic and barely possible. The main issue is that I won't be able to test what I compile.

The file I uploaded, AllSources.zip, has a makefile for Mac (makefile.osx), but I don't know what one would need to install in order to compile it.

Debo would be the right-hand man to test compile a Mac binary.

[Tulip]

I distinctly remember god mechanics being quite wonky, if you could try to touch those up, that would be neat.

Especially that one god that requires sacrifices, it was almost impossible to gain piety with it, I remember.

[debo]

Debo would be the right-hand man to test compile a Mac binary.

The mac client for something this old is almost 100% guaranteed to be based on the old carbon client (or something even older.) Those won't build on any modern mac anymore. Anyone on a mac would be better off building off makefile.std or whatever and using gcu.

[Zop]

Debo: In makefile.osx, "carbon" is mentioned multiple times, so I bet you're correct. I don't suppose I could ask you to test if compiling for mac even works? I doubt it'll be worth the effort if it takes longer than five minutes to get it to work, however.

[Pete Mack]

If you genuinely mean to maintain Furyband, updating to more recent term-xxx.c files and makefiles would be near the top of the list. Updating the UI would follow.

[Nick]

Debo: In makefile.osx, "carbon" is mentioned multiple times, so I bet you're correct. I don't suppose I could ask you to test if compiling for mac even works? I doubt it'll be worth the effort if it takes longer than five minutes to get it to work, however.

A few years ago I added the V build system, SDL port and cocoa port to Poschengband without too much trouble (11 commits over the course of a week, apparently). Someone could probably copy that quite well for Furyband, although I'd have to say that person is unlikely to be me.

[Pete Mack]

Yeah, I think it took me a few days to do a bit of that for UnAngband some years back. It really, really helps to have that stuff unified. (For what it's worth, I wrote the original makefile.inc thing largely to make it easier to do the UnAngband OSX port.)

[Zop]

Pete, Furyband uses z-term.c as an abstraction layer, so there's no term-xxx.c file... unless you mean main-xxx.c?