FAangband 1.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • SaThaRiel
    replied
    I was able to compile a running version using
    Code:
    ./configure --prefix=/usr --bindir=/usr/bin --with-private-dirs
    . So the lib-Dir will be under /usr/share/faangband. That seems to be somehow hardcoded - maybe relative, as i could also run it when installed into a user directory.
    The Font problem still exists and the CGU variant looks a bit too "colored" which maybe normal. Are there any screenshots of the current version so i can compare? If the competition savefile from FAAngband is still available, i will also try out if this works (i think i had a problem with it).

    Leave a comment:


  • Magnate
    replied
    Originally posted by Nick
    I last took V's build system in July - and at the time I just left the Debian stuff out because that was easier. I may update it all again soon, and it certainly wouldn't be smart to repeat all your good work.
    Ok. The build overhaul was quite extensive, although it defaults to the same outcomes as before - it just adds lots more flexibility for packaging. Unfortunately it means that the previous debian/ dir is now obsolete and needs completely rewriting. I've removed it from trunk, as Debian strongly prefers its maintainers to keep packaging stuff separate from upstream source. It's going to be maintained at git://git.debian.org/git/collab-maint/angband.git when I rewrite it, but it's not there yet. You're welcome to use as much as you can once it's there, and I'm happy to help with packaging. If you want to package it yourself you'll need a sponsor to upload it to Debian for you - happy to put you in touch with mine (I don't know any others).

    Leave a comment:


  • Storch
    replied
    Right now I run a pretty succesful CL 38 mage. I like FAA very much but it is so different from Vanilla that I am often confused.

    Are oangband spoilers applicable? Are they available? I cannot find them - www.oangband.com is down.

    What do the specialties exactly do? Their description is not precise enough to tell what the effect really is. I am interested in heighten magic, enhance magic, beguiling and armor proficiency.

    How does slow and confuse work? Could you please show me the math that happens when CL 50 mage with beguiling specialty tries to slow Morgoth?

    How does armor encumberance work? I have found armour of Nevrast. It is nice but costs me half of my mana. Will it improve with CL or STR (I have 18/130 now) or should I dump it?

    Thanks a lot for any help.

    Leave a comment:


  • Nick
    replied
    Originally posted by buzzkill
    FA 1.0.3

    I brand new to using macros, so bear with me if this sounds stupid. I created two simple macros, F1 and F2, and use them to cast fire bolt and fire my sling. I created them using the macro screen in the options menu. Shouldn't these still be there when I reload my still-living character. They don't seem to be.
    No, they're not kept in the savefile. You need to save them to a .prf file, using the "Append to..." option in the macro menu.

    Leave a comment:


  • buzzkill
    replied
    FA 1.0.3

    I brand new to using macros, so bear with me if this sounds stupid. I created two simple macros, F1 and F2, and use them to cast fire bolt and fire my sling. I created them using the macro screen in the options menu. Shouldn't these still be there when I reload my still-living character. They don't seem to be.

    Leave a comment:


  • Nick
    replied
    Originally posted by Magnate
    I don't know how far FA has diverged from V in terms of its impact on the filesystem, or whether you'd be willing to adopt the changes I've made to V's build system (now takes three paths: confdir for pref/ and edit/, vardir for score/ and save/ and libdir for the rest - and we removed raw files). If you're interested I'm very happy to package it for Debian and help it into Ubuntu that way.
    I last took V's build system in July - and at the time I just left the Debian stuff out because that was easier. I may update it all again soon, and it certainly wouldn't be smart to repeat all your good work.

    @SaThaRiel - I suspect the fonts are the sticking point in FA. I've done some slightly different things with them (although I can't just now recall exactly what...) in order to make extended (accented, etc) characters work and also to try to play nicely with Vista. This has probably broken something.

    Leave a comment:


  • SaThaRiel
    replied
    Originally posted by Magnate
    Want to go via Debian? I packaged V 3.1.1.1626 for Debian, and it magically appeared in Ubuntu a short while later - they have a sync bot that is quite sophisticated at repackaging.

    I don't know how far FA has diverged from V in terms of its impact on the filesystem, or whether you'd be willing to adopt the changes I've made to V's build system (now takes three paths: confdir for pref/ and edit/, vardir for score/ and save/ and libdir for the rest - and we removed raw files). If you're interested I'm very happy to package it for Debian and help it into Ubuntu that way.

    Feel free to PM me if you want to discuss details.
    Actually Ubuntu is just a Debian - somehow a "tested unstable" version. Afaik Ubuntu is packaging nothing themselves expect some themes and the metapackages for the distributions. But if you can handle it to compile FA for Debian im pretty sure that it should work on Arch. Ok, Arch is bleeding edge and a rolling release, but after all both are linux systems. Maybe i am missing some libs or something? But since other variants work i dont think so.
    If you have a working configure i would be glad if you could support me with the infos. Additionally i will try to compile it on another system with maybe ubuntu or debian.

    Leave a comment:


  • Magnate
    replied
    Originally posted by Nick
    I'm out of ideas I'm afraid - thanks for trying to do this, though. At some point I'm going to try and package FA (at least) for Ubuntu - I'll report back on whether I have the same issues.
    Want to go via Debian? I packaged V 3.1.1.1626 for Debian, and it magically appeared in Ubuntu a short while later - they have a sync bot that is quite sophisticated at repackaging.

    I don't know how far FA has diverged from V in terms of its impact on the filesystem, or whether you'd be willing to adopt the changes I've made to V's build system (now takes three paths: confdir for pref/ and edit/, vardir for score/ and save/ and libdir for the rest - and we removed raw files). If you're interested I'm very happy to package it for Debian and help it into Ubuntu that way.

    Feel free to PM me if you want to discuss details.

    Leave a comment:


  • Nick
    replied
    I'm out of ideas I'm afraid - thanks for trying to do this, though. At some point I'm going to try and package FA (at least) for Ubuntu - I'll report back on whether I have the same issues.

    Leave a comment:


  • SaThaRiel
    replied
    No change...it compiles with those warning above. But - as pointed out those arent critical.
    So im a bit stuck here. Tried a strace on the binary, but it doesnt show much useful informations. I tried to leave anything out except ncurses. But it wont start.
    Someone any ideas? Otherwise i will go on and try the package for Unangband - where it looks like i have to patch it to get the pathes that i want for install...

    Leave a comment:


  • SaThaRiel
    replied
    Compiling with
    Code:
      ./configure --disable-sdl --disable-gtk --disable-sdl-mixer --prefix=/usr --bindir=/usr/bin \
              --with-libpath=/usr/lib --datadir=/usr/lib \
              --with-private-dirs
    works. But only in the -mgcu mode (actually the mode i prefer most). I think that i had to disable the SDL during compile time because i havent enabled sound on my system. Will check this.
    Also i will try to find a solution to the font problem. Not sure what to do here.

    Edit: Tested some options but hasnt any luck. Now i compiled it again with the options above and it doesnt work anymore. Really strange
    I removed the complete source and packagebuilddir and extracted the zip again. No change. The errors are the same as above.

    And another edit: Maybe the CFLAGS set for my local machine are a problem. Need to test this too - but later.
    Last edited by SaThaRiel; November 25, 2009, 07:52.

    Leave a comment:


  • Nick
    replied
    Originally posted by zaimoni
    ! has very high priority and has only two output values: 0 and 1. This method of testing the lowest-order bit is more than slightly obscure.
    Thank you - my brain was clearly not working yesterday (or when I wrote that code). Still, as you say, that's not causing the not-running problem.

    Leave a comment:


  • zaimoni
    replied
    Originally posted by SaThaRiel
    Im building some PKGBUILDs for Archlinux atm, so Users can install packages quite easily.
    Doing the one for FAAngband i receive the following warnings when compiling
    Code:
    spells1.c: In function ‘thrust_away’:
    spells1.c:435: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’
    spells1.c:450: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’
    spells1.c:451: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’
    spells1.c:466: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’
    spells1.c: In functon ‘project_t’:
    spells1.c:7288: warning: suggest parentheses around operand of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’
    Is this a problem?

    Edit: Actually it seems to be aproblem. FAAngband doesnt run...must check.
    But not the problem preventing running.

    ! has very high priority and has only two output values: 0 and 1. This method of testing the lowest-order bit is more than slightly obscure.

    The compiler warnings are from the possible typo that converts logical and && to bitwise and &. We may not want FAAngband to join Mariner 9 at the bottom of the Great Ocean

    Leave a comment:


  • Nick
    replied
    Originally posted by SaThaRiel
    Running faangband after the install brings up this error
    Code:
    faangband: Couldn't load the requested font. (8x16x)
    My guess is it's trying to find a system font with size 8x16x, whereas faangband is trying to force the use of the fonts in the lib/xtra/fonts directory.

    Leave a comment:


  • SaThaRiel
    replied
    The normal configure is run via
    Code:
      ./configure --prefix=/usr --bindir=/usr/bin \
              --with-libpath=/usr/lib/faangband/ --datadir=/usr/lib/faangband \
              --with-private-dirs
    then a make and a
    Code:
    DESTDIR=/path/to/builddir/pkg make install
    to prepare it for the packagebuild function.
    Running faangband after the install brings up this error
    Code:
    faangband: Couldn't load the requested font. (8x16x)
    a faangband -mgcu brings this
    Code:
    faangband: Fatal Error.
    To be honest, i havent tried to look deeper into this until now. Hopefully you have an idea.

    Leave a comment:

Working...
😀
😂
🥰
😘
🤢
😎
😞
😡
👍
👎