[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] What is it mean by BUILDING DocBook ?
Hi,I'd say, just create a file named docbk.sh at any location you want but remember the full path to it. The content for this are given in step 3 of README.BUILD. There, you need to make sure the 'export' paths are correct. For example, DOCBOOK_SVN should point to your DocBook svn checkout directory.After that, open up ~/.bashrc (by command gedit ~/.bashrc). This file is located at /home/your-account-name/.bashrc. "~/" is an alias. Now, instead of adding ". ~/docbk.sh" to that file as said in the README.BUILD, add the following.. /add/full/path/to/docbk.shDon't worry about this much. It's a simple procedure. I suspect that the error you are getting "svn: warning: '.' is not a working copy" is because DOCBOOK_SVN is not set correctly. Can you run the command `echo $DOCBOOK_SVN` and see whether it outputs the correct directory?Regards,--KasunThank You in Advance !.
regards,Gihan ChanukaOn Thu, Mar 1, 2012 at 10:44 PM, <DeanNelson@aol.com> wrote:Gihan,You are referring to the instructions in the source tree that enumerate the steps required for building a "release" package. This is for the developers who preprocess/build each release that shows up on SourceForge. This is not a normal process for users of DocBook.The normal usage for user would be to download the ZIP file of the release and set up your XSLTPROC (or other tools) to run against that release.The XSLT processors transform the DocBook XML into HTML, PDF, EPUB, etc, via the XSL stylesheets in the release package.I would also suggest that you read the Bob Stayton's book on DocBookhttp://www.sagehill.net/docbookxsl/index.html also available in paper copy.Regards,Dean Nelson