This is the method i use (above). I have a highly stripped version of Trinity for a lightweight OS. In CMake i open the Cmakelists.txt file and change BUILD_ALL to OFF for the packages i don't need. In autobuilds you can also simply delete the folders of packages you don't want, then run admin/make -f makefile.common and continue with the build.

Jay



On Sun, Feb 19, 2012 at 1:17 AM, Timothy Pearson <kb9vqf@pearsoncomputing.net> wrote:
> Every package has a doc directory containing the documentation files. How
> do I build only that directory as a mini package?
>
> Reason: All Trinity documentation is contained in Docbook files. DocBook
> is a markup language. Quanta Plus and Kate provide no mechanism to view
> the final result because all Docbook files have to be converted to another
> form for viewing.
>
> As I revise the various docbook files, I want to regularly view the
> results in a Trinity desktop. I want to do this quickly without building
> an entire package.
>
> Side note: Basically, this is the beginning of a discussion about creating
> an efficient Docbook editing environment, which I'll post to the wiki. If
> you have any experience or interest in the development side of Docbook
> then please feel welcome to help. You don't have to write or edit, just
> help set up the environment and I'll document the process for everybody
> --- but I need help getting there. :)
>
> Thanks!
>
> Darrell

You could try running ./configure or cmake normally, then change to the
doc/ directory before running make/make install.

Tim


---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting