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/manual.qbk | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs/manual.qbk') diff --git a/docs/manual.qbk b/docs/manual.qbk index b234fee..17f6de1 100644 --- a/docs/manual.qbk +++ b/docs/manual.qbk @@ -12,6 +12,7 @@ [template file[name]''''''[name]''''''] [template sref[name]''''''] [template anchor[name]''''''[^[name]]] +[template ftnt[id text]''''''[text]''''''] [section:overview Overview] @@ -138,7 +139,7 @@ The complete pugixml source consists of four files - two source files, [file pug [section:embed Building pugixml as a part of another static library/executable] -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. +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. If you're using Microsoft Visual Studio and the project has precompiled headers turned on, you'll see the following error messages: -- cgit v1.2.3