| Daniel Veillard | 5351695 | 2005-01-27 23:59:14 +0000 | [diff] [blame] | 1 |
|
| 2 | LIBXML2 build system for Win32 README
|
| 3 | -------------------------------------
|
| 4 |
|
| 5 | In this folder are stored all the files required to compile LIBXML2 with win32 compilers.
|
| 6 | Bakefile (http://bakefile.sourceforge.net) is used as makefile generator.
|
| 7 |
|
| 8 | Supported makefiles:
|
| 9 | - makefile.vc for Microsoft NMAKE
|
| 10 | - makefile.bcc for Borland MAKE
|
| 11 | - makefile.wat for OpenWatcom MAKE
|
| 12 | - makefile.gcc for MinGW MINGW32-MAKE
|
| 13 | - all DSP & DSW for Microsoft VisualC++ 6.0 (can be used also with VS.NET AFAIK)
|
| 14 |
|
| 15 | This readme is organized as:
|
| 16 | 1.0 HOWTO compile LIBXML2 using makefiles <-- for users who want to build the library using *command-line*
|
| 17 | 1.1 HOWTO compile LIBXML2 using an IDE <-- for users who want to build the library using an *IDE*
|
| 18 | 1.2 HOWTO regenerate makefiles for LIBXML2 <-- for libxml2 mantainers/developers/advanced users
|
| 19 |
|
| 20 | If you just want to compile the library (and the test programs) you should definitely avoid the
|
| 21 | section 1.1 and focus on the 1.0.
|
| 22 |
|
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
|
| 28 | 1.0 HOWTO compile LIBXML2 using makefiles
|
| 29 | -----------------------------------------
|
| 30 |
|
| 31 | Choose your preferred compiler among those actually supported (see above) and then run
|
| 32 |
|
| 33 | mycompilermake -fmakefile.makefileext [options]
|
| 34 |
|
| 35 | for a full list of the available options you should open with a notepad (or something like that)
|
| 36 | the makefile you want to use; at the beginning you should see a section which starts as:
|
| 37 |
|
| 38 | # -------------------------------------------------------------------------
|
| 39 | # These are configurable options:
|
| 40 | # -------------------------------------------------------------------------
|
| 41 |
|
| 42 | here you can find all the options actually used by that makefile.
|
| 43 | They can be customized when running the makefile writing something like:
|
| 44 |
|
| 45 | nmake -fmakefile.vc BUILD=release
|
| 46 | mingw32-make -fmakefile.gcc BUILD=debug ICONV_DIR=c:\myiconv
|
| 47 |
|
| 48 | or they can be permanently changed modifying the makefile.
|
| 49 | That's all: for any problem/compile-error/suggestion, write to
|
| 50 | frm@users.sourceforge.net with the word "libxml2" in the subject.
|
| 51 |
|
| 52 |
|
| 53 |
|
| 54 |
|
| 55 |
|
| 56 | 1.1 HOWTO compile LIBXML2 using an IDE
|
| 57 | --------------------------------------
|
| 58 |
|
| 59 | Actually only the Microsoft VisualC++ 6.0 project files are generated.
|
| 60 | In future other Integrated Development Environments (IDEs) will be supported as well.
|
| 61 |
|
| 62 | With MSVC++ 6.0, you should open the DSW file and then set as the active project the
|
| 63 | "libxml2" project, if you want to build the library or one of the test projects if you
|
| 64 | want to run them.
|
| 65 | Using the command "Build->Set Active Configuration" you can choose one of the predefined
|
| 66 | configuration.
|
| 67 |
|
| 68 |
|
| 69 |
|
| 70 |
|
| 71 |
|
| 72 | 1.2 HOWTO regenerate makefiles for LIBXML2
|
| 73 | ------------------------------------------
|
| 74 |
|
| 75 | Be sure to have installed Bakefile (http://bakefile.sourceforge.net).
|
| 76 | Just run the "bakefile_gen" command inside the folder containing the "libxml2.bkl" file.
|
| 77 | NOTE: if you want to remove all the makefiles, you can use the "bakefile_gen -c" command.
|
| 78 |
|
| 79 | The template files used to generate all makefiles are only two:
|
| 80 | - libxml2.bkl (the main one)
|
| 81 | - Bakefiles.bkgen
|
| 82 | All the other files can be dinamically regenerated.
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 | If you have problems with the compilation of LIBXML2 under windows (using one of the supported compiler)
|
| 89 | please write to:
|
| 90 |
|
| 91 | Francesco Montorsi <frm@users.sourceforge.net>
|
| 92 |
|