From 197f1edfc13e6b3ce89af4ff9047feee75121455 Mon Sep 17 00:00:00 2001 From: "arseny.kapoulkine" Date: Thu, 15 Jul 2010 17:01:57 +0000 Subject: docs: Fixed TOC links properly, got rid of pointer-based auto-generated ids git-svn-id: http://pugixml.googlecode.com/svn/trunk@604 99668b35-9821-0410-8761-19e4c4f06640 --- docs/quickstart.qbk | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'docs/quickstart.qbk') diff --git a/docs/quickstart.qbk b/docs/quickstart.qbk index bedaa15..512db4a 100644 --- a/docs/quickstart.qbk +++ b/docs/quickstart.qbk @@ -7,11 +7,9 @@ [license Distributed under the MIT License] ] -[template file[name] ''''''[name]''''''] -[template sbr[] ''''''] -[template lbr[] ''''''] [/ for empty lines in lists] -[template sref[name] ''''''] -[template anchor[name] ''''''[^[name]]] +[template file[name]''''''[name]''''''] +[template sref[name]''''''] +[template ftnt[id text]''''''[text]''''''] [section:main pugixml 0.9 quick start guide] @@ -40,7 +38,7 @@ The distribution contains library source, documentation (the guide you're readin The complete pugixml source consists of four files - two source files, [file pugixml.cpp] and [file pugixpath.cpp], and two header files, [file pugixml.hpp] and [file pugiconfig.hpp]. [file pugixml.hpp] is the primary header which you need to include in order to use pugixml classes/functions. The rest of this guide assumes that [file pugixml.hpp] is either in the current directory or in one of include directories of your projects, so that `#include "pugixml.hpp"` can find the header; however you can also use relative path (i.e. `#include "../libs/pugixml/src/pugixml.hpp"`) or include directory-relative path (i.e. `#include `). -The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[footnote All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects. There are other building methods available, including building pugixml as a standalone static/shared library; read the manual for further information. +The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[ftnt trademarks All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects. There are other building methods available, including building pugixml as a standalone static/shared library; read the manual for further information. [endsect] [/install] -- cgit v1.2.3