Annotation of gpl/axl/README.win32, revision 1.1.1.1
1.1 misho 1:
2: -= Compiling LibAxl under Microsoft Windows =-
3:
4: 1. Intro
5: ~~~~~~~~
6:
7: There are two know ways to compile LibAxl under windows: using gcc
8: tools, provided by the mingw project [1] or using one of the Microsoft
9: C compilers.
10:
11: In any case, you must take into consideration these basic steps for
12: both:
13:
14: 1) You must create an axl_config.h file, using the
15: axl_config_win32.h file provided. Just rename it.
16:
17: 2) If you are using Microsoft C compilers, you must ensure you can
18: have access to the _vscprintf function or not. If you can, which
19: is the recomended, you must define a preprocessor as follows:
20:
21: HAVE_VSCPRINTF
22:
23: See axl_stream_vprintf_len function inside the axl_stream.c
24: module to get a more accurate idea.
25:
26: If you can't get access to such function (which is relatively
27: recent), just do nothing. This will make Axl Library to use
28: default implementation for the axl_stream_strdup* family of
29: functions to be limited to 8192 bytes.
30:
31: In many cases this isn't a problem, but you are adviced.
32:
33: 2. GCC and Mingw
34: ~~~~~~~~~~~~~~~~
35:
36: This is default platform we are using to get LibAxl working under
37: windows. It is showed to get really good results and good performance,
38: however there is a problem. Gcc tools do not produce a debug
39: information format that could be used by Microsoft tools.
40:
41: Obviously, if this is not a problem for you, then you don't have any
42: problem, and, under this situation we recomend to use gcc as default
43: compilation tool.
44:
45: You can use files provided inside the src, ns and test directory to
46: compile Axl: Makefile.win
47:
48: 3. Microsoft compilers
49:
50: Axl library is tested to compile and run properly using Visual C 6.0,
51: Visual Studio 2005 and its express edition.
52:
53: With the source code are provided visual studio project files to
54: make it easy to compile LibAxl. See libaxl.sln under the top source
55: directory.
56:
57: 4. Testing build done
58:
59: Whatever you compiler is, you must execute the test_01 regression
60: test, found inside the test directory to ensure your build will
61: provide a proper function. All tests must be passed.
62:
63: 5. Futher information and resources
64:
65: Remember you can get more information at [1], [2], [3] and [4].
66:
67: If you want commercial support, contact us directly at: info@aspl.es
68: (either Spanish or English).
69:
70: A limited community support, according to the colaboration received,
71: is also provided at the mailing list [4].
72:
73: 6. Resources
74:
75: [1] [Mingw project] http://www.mingw.org
76: [2] [Axl library project] http://xml.aspl.es
77: [3] [ASPL homwpage] http://www.aspl.es
78: [3] [ASPL mailing list] http://lists.aspl.es
79:
80: --
81: Francis Brosnan Blázquez
82: francis@aspl.es
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>