third_party/libxml/src/win32/VC10/README.vc10 - Issue 1193533007: Upgrade to libxml 2.9.2 and libxslt 1.1.28

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: third_party/libxml/src/win32/VC10/README.vc10

Issue 1193533007: Upgrade to libxml 2.9.2 and libxslt 1.1.28 (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: no iconv Created 5 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
(Empty)
	1

	2 README file for VC10 project files for libxml2

	3 ----------------------------------------------

	4

	5 to clarify: This is not the readme file for the whole libxml2 project.

	6 Rather, it's a readme for the VC10 project files, attached to the libxml2 proejc t.

	7

	8 Quick Start

	9 -----------

	10

	11 1) To use, load the libxml2.sln solution file into visual studio

	12 2) check and correct paths for dependent "iconv" project which most certaily

	13 are wrong on your environment.

	14 3) Compile all projects

	15

	16

	17 Background Info

	18 ---------------

	19

	20 Running of "configure.sh" won't make sense since VS doesn't support

	21 this kind of build system and the environment is pretty much known already

	22 if you're using Visual Studio. Instead, a preconfigured "config.h" file

	23 is provided in the "win32\VC10" directory and referenced by the project

	24 files already.

	25

	26 The compile process is not completely warning-free: Some warnings will

	27 appear during compile which can be ignored.

OLD	NEW