• Home
  • History
  • Annotate
  • only in /external/chromium_org/third_party/libxml/src/
NameDateSize

..12-Mar-20154 KiB

acconfig.h12-Mar-2015312

acinclude.m412-Mar-2015776

aclocal.m412-Mar-2015310.6 KiB

AUTHORS12-Mar-2015208

c14n.c12-Mar-201569.9 KiB

catalog.c12-Mar-201596.7 KiB

ChangeLog12-Mar-2015731.2 KiB

check-relaxng-test-suite.py12-Mar-20159.8 KiB

check-relaxng-test-suite2.py12-Mar-201510.3 KiB

check-xinclude-test-suite.py12-Mar-20155.2 KiB

check-xml-test-suite.py12-Mar-20159.4 KiB

check-xsddata-test-suite.py12-Mar-201510.4 KiB

chvalid.c12-Mar-201512 KiB

config.guess12-Mar-201543.9 KiB

config.h.in12-Mar-20157.6 KiB

config.sub12-Mar-201533.6 KiB

configure12-Mar-2015462.7 KiB

configure.in12-Mar-201537.1 KiB

Copyright12-Mar-20151.5 KiB

dbgen.pl12-Mar-20151.3 KiB

dbgenattr.pl12-Mar-20151.3 KiB

debugXML.c12-Mar-201594.4 KiB

depcomp12-Mar-201518.2 KiB

dict.c12-Mar-201525.8 KiB

DOCBparser.c12-Mar-20158.6 KiB

elfgcchack.h12-Mar-2015648.5 KiB

encoding.c12-Mar-2015130.1 KiB

entities.c12-Mar-201526.6 KiB

error.c12-Mar-201526.6 KiB

gentest.py12-Mar-201529 KiB

genUnicode.py12-Mar-201512.7 KiB

globals.c12-Mar-201529.3 KiB

hash.c12-Mar-201528.2 KiB

HTMLparser.c12-Mar-2015199.8 KiB

HTMLtree.c12-Mar-201531.6 KiB

include/12-Mar-20154 KiB

INSTALL12-Mar-201515.2 KiB

install-sh12-Mar-201513.3 KiB

legacy.c12-Mar-201537.9 KiB

libxml-2.0-uninstalled.pc.in12-Mar-2015286

libxml-2.0.pc.in12-Mar-2015336

libxml.h12-Mar-20152.2 KiB

libxml.m412-Mar-20157.7 KiB

libxml.spec.in12-Mar-20153.9 KiB

libxml2.spec12-Mar-20153.9 KiB

list.c12-Mar-201516 KiB

ltmain.sh12-Mar-2015237.5 KiB

missing12-Mar-201511.2 KiB

mkinstalldirs12-Mar-20153.5 KiB

nanoftp.c12-Mar-201550.2 KiB

nanohttp.c12-Mar-201546.3 KiB

NEWS12-Mar-201593.6 KiB

parser.c12-Mar-2015404.6 KiB

parserInternals.c12-Mar-201562.3 KiB

pattern.c12-Mar-201562.2 KiB

README12-Mar-20151.2 KiB

README.tests12-Mar-20151.2 KiB

regressions.py12-Mar-201512.1 KiB

regressions.xml12-Mar-20156.2 KiB

relaxng.c12-Mar-2015355.6 KiB

runsuite.c12-Mar-201531.6 KiB

runtest.c12-Mar-2015112.3 KiB

SAX.c12-Mar-20155.4 KiB

SAX2.c12-Mar-201581.3 KiB

schematron.c12-Mar-201547.1 KiB

testapi.c12-Mar-20151.4 MiB

testAutomata.c12-Mar-20157.5 KiB

testC14N.c12-Mar-20159.5 KiB

testdso.c12-Mar-2015166

testHTML.c12-Mar-201520.7 KiB

testModule.c12-Mar-20151.8 KiB

testReader.c12-Mar-20153.2 KiB

testRegexp.c12-Mar-201510.1 KiB

testRelax.c12-Mar-20154.5 KiB

testSAX.c12-Mar-201527 KiB

testSchemas.c12-Mar-20154.2 KiB

testThreads.c12-Mar-20154.8 KiB

testThreadsWin32.c12-Mar-20153.3 KiB

testURI.c12-Mar-20152.9 KiB

testXPath.c12-Mar-20155.8 KiB

threads.c12-Mar-201526.2 KiB

TODO12-Mar-201511.1 KiB

TODO_SCHEMAS12-Mar-2015922

tree.c12-Mar-2015248 KiB

trio.c12-Mar-2015155.8 KiB

trio.h12-Mar-20157 KiB

triodef.h12-Mar-20156.6 KiB

trionan.c12-Mar-201522.6 KiB

trionan.h12-Mar-20152 KiB

triop.h12-Mar-20155.6 KiB

triostr.c12-Mar-201541.1 KiB

triostr.h12-Mar-20158 KiB

uri.c12-Mar-201566 KiB

valid.c12-Mar-2015188.2 KiB

win32/12-Mar-20154 KiB

xinclude.c12-Mar-201566.4 KiB

xlink.c12-Mar-20154.5 KiB

xml2-config.112-Mar-20151.2 KiB

xml2-config.in12-Mar-20151.6 KiB

xml2Conf.sh.in12-Mar-2015191

xmlcatalog.c12-Mar-201514.6 KiB

xmlIO.c12-Mar-201599.8 KiB

xmllint.c12-Mar-201594.7 KiB

xmlmemory.c12-Mar-201525.5 KiB

xmlmodule.c12-Mar-20159.8 KiB

xmlreader.c12-Mar-2015158.8 KiB

xmlregexp.c12-Mar-2015214.7 KiB

xmlsave.c12-Mar-201569.9 KiB

xmlschemas.c12-Mar-2015801.2 KiB

xmlschemastypes.c12-Mar-2015172.6 KiB

xmlstring.c12-Mar-201524.5 KiB

xmlunicode.c12-Mar-2015100.5 KiB

xmlwriter.c12-Mar-2015121.8 KiB

xpath.c12-Mar-2015411.2 KiB

xpointer.c12-Mar-201575.4 KiB

README

1
2                  XML toolkit from the GNOME project
3
4Full documentation is available on-line at
5    http://xmlsoft.org/
6
7This code is released under the MIT Licence see the Copyright file.
8
9To build on an Unixised setup:
10   ./configure ; make ; make install
11To build on Windows:
12   see instructions on win32/Readme.txt
13
14To assert build quality:
15   on an Unixised setup:
16      run make tests
17   otherwise:
18       There is 3 standalone tools runtest.c runsuite.c testapi.c, which
19       should compile as part of the build or as any application would.
20       Launch them from this directory to get results, runtest checks 
21       the proper functionning of libxml2 main APIs while testapi does
22       a full coverage check. Report failures to the list.
23
24To report bugs, follow the instructions at: 
25  http://xmlsoft.org/bugs.html
26
27A mailing-list xml@gnome.org is available, to subscribe:
28    http://mail.gnome.org/mailman/listinfo/xml
29
30The list archive is at:
31    http://mail.gnome.org/archives/xml/
32
33All technical answers asked privately will be automatically answered on
34the list and archived for public access unless pricacy is explicitely
35required and justified.
36
37Daniel Veillard
38
39$Id$
40

README.tests

1                       README.tests
2
3   Instructions for standalone test regressions of libxml2
4
5libxml2-tests-$version.tar.gz contains 3 standalone C programs as well
6as a large amount of tests and results coming from libxml2 itself and
7from W3C, NIST, Sun Microsystems, Microsoft and James Clark. Each C
8program has a different testing purpose:
9
10  runtest.c : runs libxml2 basic internal regression tests
11  runsuite.c: runs libxml2 against external regression tests
12  testapi.c : exercises the library public entry points
13  testchar.c: exercise the check of character ranges and UTF-8 validation
14
15The command:
16
17  make -f Makefile.tests check
18
19should be sufficient on an Unix system to build and exercise the tests
20for the version of the library installed on the system. Note however
21that there isn't backward compatibility provided so if the installed
22version is older to the testsuite one, failing to compile or run the tests
23is likely. In any event this won't work with an installed libxml2 older
24than 2.6.20.
25Building on other platfroms should be a matter of compiling the C files
26like any other program using libxml2, running the test should be done
27simply by launching the resulting executables.
28
29Daniel Veillard
30Thu Jul 24 2008
31