| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
| |
That is, unless you count the ones in ncurses' headers, which I can't
do anything except suppress.
|
|
|
|
|
|
|
|
|
|
| |
For most header files, this only saves on having to recompile a
small number of source files, but there are also a few headers
where small changes would now take significantly less time.
This is most obvious for the Tiles build for which the dependencies
have been greatly reduced, so that the only additional includes
when compared to console are strictly library or tile related.
|
|
|
|
|
|
|
|
|
|
| |
This is a NIH implementation of a part of autoconf, it is limited as it
would be hard to affect the Makefile from such tests. On the other hand,
even nasty hacks like grepping for sqlite features are not enough here, as
we're looking for something in system headers.
I think all of configuration in the Makefile should be nuked and rewritten,
so it's just a crutch for 0.11.
|
|
|
|
|
|
|
| |
I used this function because some random page misled me into thinking it is
available on Windows (possibly a fault of my poor reading comprehension...).
It looks like that there's no existing function on Windows that's race-free,
so I implemented one from scratch.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
BTW, what's the point of forcing architecture in the build? The compiler
already knows that, trying to do that ourselves just caused build failures.
|
|\
| |
| |
| |
| | |
There are some issues left, like incorrect wrapping in some cases, but
we can fix them later.
|
| |\
| | |
| | |
| | | |
Conflicts galore...
|
| |\ \ |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Only iostreams functions are left; on Windows they don't support Unicode
so a workaround will be needed.
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"File:" is shown in your editor's status bar.
"Written by:" was used only for the first person who changed a file. We got
git for that now, and pre-DCSS history is so woefully inaccurate it doesn't
really matter.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
Without it, starting Crawl twice in the same second produced identical seeds.
It doesn't matter for real games (no DGL on Windows...), but can be
surprising when doing automated tests or playing with layout generators.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's strange that FreeBSD and old MacOS X don't have something that was
mandated in POSIX Issue 5 (1997), but let's cope with that. It's better
to unfairly accuse other systems of noncompliance and suffer a slowdown
than to fail to build at all.
|
| | | |
|
| |/
|/| |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
twice.
This fixes Mantis 2061.
I did not reuse the existing lk_open() because it's non-portable, waits for the
lock to become available and works using FILE* not a descriptor (bad for random
access).
|
|
It's mostly so you can see how much of the file was lost to due to waste.
If everything is working as designed, waste should never exceed the size of
compressed global chunks (chr, you, tc, kil, ...) plus at most two levels
-- that is, the biggest set of chunks rewritten between commits.
If you know a case when the waste explodes in size, tell me!
|