shaba/libxml2
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/libxml2.git synced 2025-03-19 14:50:07 +03:00
Code

cleanup

Browse Source
This commit is contained in:
Igor Zlatkovic 2002-11-14 17:43:55 +00:00
parent bd1a306cab
commit b2f616352a
2 changed files with 11 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
include/win32config.h
View File

@ -80,23 +80,11 @@ static int isnan (double d) {
}
#endif /* _MSC_VER */
#ifdef _MSC_VER
/* We don't use trio when compiling under MSVC. This is not because trio
is bad, but because MSVC has no easy way to conditionally include a .c
file in the project. In order to enable trio usage, we would have to compile
all trio functionality into the executable, even if we don't use it.
Since MS C-runtime has all required functions, trio is not necessary. */
#ifdef WITH_TRIO
#undef WITH_TRIO
#endif /* WITH_TRIO */
#ifndef WITHOUT_TRIO
#define WITHOUT_TRIO
#endif /* WITHOUT_TRIO */
/* Microsoft's C runtime names all non-ANSI functions with a leading
underscore. Since functionality is still the same, they can be used. */
#if defined(_MSC_VER) || defined(__MINGW32__)
#define mkdir(p,m) _mkdir(p)
#define snprintf _snprintf
#define vsnprintf _vsnprintf
#endif /* _MSC_VER */
#define vsnprintf(b,c,f,a) _vsnprintf(b,c,f,a)
#endif
/* Threading API to use should be specified here for compatibility reasons.
This is however best specified on the compiler's command-line. */

10
win32/Readme.txt
View File

@ -95,11 +95,15 @@ configuration.
-------------
After the configuration stage has been completed, you want to build
the software. To do that, type
the software. You will have to use the make tool which comes with
your compiler. If you, for example, configured the source to build
with Microsoft's MSVC compiler, you would use the NMAKE utility. If
ýou configured it to build with GNU C compiler, mingw edition, you
would use the GNU make. Assuming you use MSVC, type
nmake
in the win32 subdirectory.When the building completes, you will find
in the win32 subdirectory. When the building completes, you will find
the executable files in win32\binaries directory.
You can install the software into the directory you specified to the
@ -125,5 +129,5 @@ possible, and there is also a chance that support exists for IDEs
which I have never seen.
March 2002, Igor Zlatkovic <igor@stud.fh-frankfurt.de>
November 2002, Igor Zlatkovic <igor@stud.fh-frankfurt.de>