Customizing Home Capacity.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • krazyhades
    replied
    This thread makes me long for Pyrel.

    Leave a comment:


  • Nick
    replied
    Originally posted by Zappa
    Would this help anyone tell me what I'm doing wrong?
    My best guess is that it's some 32- vs 64-bit issue, but I'm not sure what. Here is a similar problem someone had recently with NPPAngband. Sorry to be of so little help.

    Leave a comment:


  • Zappa
    replied
    Would this help anyone tell me what I'm doing wrong?

    [spoiler]
    Code:
    gcc -DWINDOWS -static -Iwin/include -Lwin/lib -Wall -Wextra -Wno-unused-paramete
    r -Wno-missing-field-initializers -std=c99 -Wdeclaration-after-statement -O2 -I.
     -c -o z-file.o z-file.c
    In file included from z-file.c:24:0:
    c:\mingw\include\io.h:301:1: error: unknown type name 'off64_t'
     __CRT_INLINE off64_t lseek64 (int, off64_t, int);
     ^
    c:\mingw\include\io.h:301:36: error: unknown type name 'off64_t'
     __CRT_INLINE off64_t lseek64 (int, off64_t, int);
                                        ^
    c:\mingw\include\io.h:302:1: error: unknown type name 'off64_t'
     __CRT_INLINE off64_t lseek64 (int fd, off64_t offset, int whence) {
     ^
    c:\mingw\include\io.h:302:39: error: unknown type name 'off64_t'
     __CRT_INLINE off64_t lseek64 (int fd, off64_t offset, int whence) {
                                           ^
    z-file.c: In function 'file_exists':
    z-file.c:309:14: error: storage size of 'st' isn't known
      struct stat st;
                  ^
    z-file.c:310:2: warning: implicit declaration of function 'stat' [-Wimplicit-fun
    ction-declaration]
      return (stat(fname, &st) == 0);
      ^
    z-file.c:309:14: warning: unused variable 'st' [-Wunused-variable]
      struct stat st;
                  ^
    z-file.c: In function 'file_newer':
    z-file.c:348:14: error: storage size of 'stat1' isn't known
      struct stat stat1, stat2;
                  ^
    z-file.c:348:21: error: storage size of 'stat2' isn't known
      struct stat stat1, stat2;
                         ^
    z-file.c:348:21: warning: unused variable 'stat2' [-Wunused-variable]
    z-file.c:348:14: warning: unused variable 'stat1' [-Wunused-variable]
      struct stat stat1, stat2;
                  ^
    z-file.c: In function 'dir_exists':
    z-file.c:676:14: error: storage size of 'buf' isn't known
      struct stat buf;
                  ^
    z-file.c:676:14: warning: unused variable 'buf' [-Wunused-variable]
    z-file.c: In function 'file_exists':
    z-file.c:311:1: warning: control reaches end of non-void function [-Wreturn-type
    ]
     }
     ^
    z-file.c: In function 'file_newer':
    z-file.c:361:1: warning: control reaches end of non-void function [-Wreturn-type
    ]
     }
     ^
    z-file.c: In function 'dir_exists':
    z-file.c:686:1: warning: control reaches end of non-void function [-Wreturn-type
    ]
     }
     ^
    make: *** [z-file.o] Error 1
    [/spoiler]

    Leave a comment:


  • Zappa
    replied
    thanks for your help anyway. this might be beyond my abilities.

    Leave a comment:


  • Timo Pietilä
    replied
    Originally posted by Zappa
    Oh wow it looks like that works. Thank you so much for your help.

    EDIT: Well it looked like it was working but now I have far too many error messages to post here.
    Sounds exactly like my first try with mingw. I got it to work somehow but that's so long ago that I don't remember what was the problem and how I solved it. Something to do with path lengths IIRC.

    I use cygwin now. Or at least I used to, I don't have it in my new computer. Anyway, I did find cygwin much easier to use than mingw.

    [EDIT] Thangorodrim compile instructions can be useful to you:



    [EDIT EDIT]

    Reading those...not so useful after all. makefile.cyg doesn't even exist anymore. Makefile.win might work though (I haven't compiled my own version for ages now).
    Last edited by Timo Pietilä; October 17, 2013, 10:19.

    Leave a comment:


  • Zappa
    replied
    Originally posted by Timo Pietilä
    mingw32-make instead of make?
    Oh wow it looks like that works. Thank you so much for your help.

    EDIT: Well it looked like it was working but now I have far too many error messages to post here.

    Leave a comment:


  • Timo Pietilä
    replied
    Originally posted by Zappa
    Yeah, but then I'm told 'make' isn't recognized. Cygwin does the same thing.
    mingw32-make instead of make?

    Leave a comment:


  • Zappa
    replied
    Originally posted by takkaria
    If you are using mingw and not cygwin, use make -f Makefile.win MINGW=true.
    Yeah, but then I'm told 'make' isn't recognized. Cygwin does the same thing.

    Leave a comment:


  • takkaria
    replied
    Originally posted by Zappa
    So I'm trying this again and here's where I'm at:

    C:\angband-master\src>mingw32-make -f Makefile.win
    gcc -DWINDOWS -static -Iwin/include -Lwin/lib -Wall -Wextra -Wno-unused-paramete
    r -Wno-missing-field-initializers -std=c99 -Wdeclaration-after-statement -O2 -I.
    -mno-cygwin -c -o attack.o attack.c
    gcc: error: unrecognized command line option '-mno-cygwin'
    Makefile.win:125: recipe for target 'attack.o' failed
    mingw32-make: *** [attack.o] Error 1

    I have no idea what I'm doing wrong.
    If you are using mingw and not cygwin, use make -f Makefile.win MINGW=true.

    Leave a comment:


  • Zappa
    replied
    So I'm trying this again and here's where I'm at:

    C:\angband-master\src>mingw32-make -f Makefile.win
    gcc -DWINDOWS -static -Iwin/include -Lwin/lib -Wall -Wextra -Wno-unused-paramete
    r -Wno-missing-field-initializers -std=c99 -Wdeclaration-after-statement -O2 -I.
    -mno-cygwin -c -o attack.o attack.c
    gcc: error: unrecognized command line option '-mno-cygwin'
    Makefile.win:125: recipe for target 'attack.o' failed
    mingw32-make: *** [attack.o] Error 1

    I have no idea what I'm doing wrong.

    Leave a comment:


  • DaviddesJ
    replied
    I tend to think the max of all stores should be bigger. What purpose does the store limit serve? If you want some items to sometimes be available and sometimes not available, you can certainly do that, but it doesn't need to be a side effect of a limit. The biggest question is how to have a uniform, clean interface that allows any number (or, at least, a larger number) of items.

    Leave a comment:


  • jrodman
    replied
    It seems simple to split out the home max seperately from the store max. The store max is only used when generating item stocks and initializing the store struct. In fact it seems like the item stocks should just be converted to use the store struct's stored max.

    Then we can just use a different max when initializing the home.

    At this point we're not changing the behavior of other stores, which is a plus.

    As said before, reworking the display and selection for a longer list probably would require pagination or a rippling chang out to item-selection menu code, since the existing picker ui is based around being able to single-letter all the choices. :-( More than I care to do right now.

    Oh, also load.c / rd_stores has to be changed not truncate the home, if they're of differing sizes.
    Last edited by jrodman; August 15, 2013, 10:45.

    Leave a comment:


  • Zappa
    replied
    I ended up restarting the computer and that worked. I think the problem started when I tried to compile 3.3.2 with the changes and I copied the .dll's from another unmodified version of 3.3.2.

    At least, that was the last thing I did before it all got goofy.

    Leave a comment:


  • Mikko Lehtinen
    replied
    Maybe the game lost font information for some reason? Try changing fonts after starting the game.

    Leave a comment:


  • Zappa
    replied
    Now I seem to be getting a blank screen after I compile any version. AS in, game starts up but everything is black. I can see the cursor move around during birth. I am sure this is a problem of my making, but if anyone has seen this before I could use a hint.

    Leave a comment:

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