[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[certi-cvs] certi CMakeLists.txt doc/certi_user_doc.tree do...
|
From: |
certi-cvs |
|
Subject: |
[certi-cvs] certi CMakeLists.txt doc/certi_user_doc.tree do... |
|
Date: |
Sat, 11 Oct 2008 23:03:18 +0000 |
CVSROOT: /sources/certi
Module name: certi
Changes by: Eric NOULARD <erk> 08/10/11 23:03:18
Modified files:
. : CMakeLists.txt
doc : certi_user_doc.tree index.html CMakeLists.txt
certi_user.cnf.in DoxyTools.cmake
certi_user.dox
Added files:
doc : certi_user_header.html doc_install.in
Log message:
On step more for a better doc.
Now make install will install "Install" and "User"
doc in share/doc/certi
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/certi/CMakeLists.txt?cvsroot=certi&r1=1.60&r2=1.61
http://cvs.savannah.gnu.org/viewcvs/certi/doc/certi_user_doc.tree?cvsroot=certi&r1=3.1&r2=3.2
http://cvs.savannah.gnu.org/viewcvs/certi/doc/index.html?cvsroot=certi&r1=3.4&r2=3.5
http://cvs.savannah.gnu.org/viewcvs/certi/doc/CMakeLists.txt?cvsroot=certi&r1=1.7&r2=1.8
http://cvs.savannah.gnu.org/viewcvs/certi/doc/certi_user.cnf.in?cvsroot=certi&r1=3.2&r2=3.3
http://cvs.savannah.gnu.org/viewcvs/certi/doc/DoxyTools.cmake?cvsroot=certi&r1=3.2&r2=3.3
http://cvs.savannah.gnu.org/viewcvs/certi/doc/certi_user.dox?cvsroot=certi&r1=3.1&r2=3.2
http://cvs.savannah.gnu.org/viewcvs/certi/doc/certi_user_header.html?cvsroot=certi&rev=3.1
http://cvs.savannah.gnu.org/viewcvs/certi/doc/doc_install.in?cvsroot=certi&rev=3.1
Patches:
Index: CMakeLists.txt
===================================================================
RCS file: /sources/certi/certi/CMakeLists.txt,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- CMakeLists.txt 10 Oct 2008 07:34:53 -0000 1.60
+++ CMakeLists.txt 11 Oct 2008 23:03:16 -0000 1.61
@@ -316,7 +316,7 @@
ADD_SUBDIRECTORY( RTIA )
ADD_SUBDIRECTORY( libRTI )
ADD_SUBDIRECTORY( test )
-ADD_SUBDIRECTORY( doc EXCLUDE_FROM_ALL )
+ADD_SUBDIRECTORY( doc )
SET(CPACK_PACKAGE_DESCRIPTION_SUMMARY "CERTI An efficient Open Source HLA
RunTime Infrastructure")
SET(CPACK_PACKAGE_VENDOR "ONERA/DTIM")
Index: doc/certi_user_doc.tree
===================================================================
RCS file: /sources/certi/certi/doc/certi_user_doc.tree,v
retrieving revision 3.1
retrieving revision 3.2
diff -u -b -r3.1 -r3.2
--- doc/certi_user_doc.tree 9 Oct 2008 23:39:55 -0000 3.1
+++ doc/certi_user_doc.tree 11 Oct 2008 23:03:17 -0000 3.2
@@ -22,137 +22,17 @@
// ----------------------------------------------------------------------------
*/
-/**
- * @mainpage
- * \section intro_sec Introduction
+ /**
+ * \page index
*
- * This is the CERTI documentation.
- * CERTI is an Open Source HLA compliant
- * <a href="http://en.wikipedia.org/wiki/Run-Time_Infrastructure_(simulation)">
- * RunTime Infrastructure (RTI)</a>.
- * You'll find hereafter the documentation for the main modules
- * of the CERTI project.
- * CERTI is primarily developed and maintained by the Toulouse research center
of ONERA [http://www.onera.fr], the French Aerospace Labs.
- * The primary goal of CERTI is to be used in research activities but CERTI
has a growing
- * number of users and contributors among the CERTI Open Source community.
+ * <h1> CERTI User Documentation </h1>
+ * \n
+ * This is the CERTI installation documentation.
+ * The installation documentation is divided into several part:
*
- * People interested in CERTI may join the CERTI Open Source
- * community at <a href="https://savannah.nongnu.org/projects/certi";>
- * https://savannah.nongnu.org/projects/certi </a> and/or
- * by using the mailing list
- * <a href="http://lists.nongnu.org/mailman/listinfo/certi-devel";>
- * http://lists.nongnu.org/mailman/listinfo/certi-devel </a>
- * for discussion regarding CERTI usage.
- *
- * \section certi_modules Main CERTI Modules
- * The main CERTI modules are:
- * <ul>
- * <li> \ref libCERTI </li>
- * <li> \ref libRTI </li>
- * <li> \ref Billard_Application </li>
- * </ul>
- * There are some RTI-agnostic libraries or applications which
- * are bundled with the CERTI distribution:
- * <ul>
- * <li> \ref libHLA </li>
- * </ul>
- *
- * \section certi_sdk Installing and using CERTI SDK
- *
- * CERTI SDK comes as either as an installer (binary) or compressed tar source
archives.
- * The primary distribution format is gzip compressed tar source archive
(.tar.gz)
- * or ZIP archive (.zip) and may be found on Savannah CERTI download area: <a
href="http://download.savannah.nongnu.org/releases/certi/";>
http://download.savannah.nongnu.org/releases/certi/ </a>.
- *
- * CERTI build system uses <a href="http://www.cmake.org/";>CMake,
http://www.cmake.org/ </a>
- * which is a cross-platform build system generator. CMake should be used to
- * compile CERTI SDK on a variety of platform/compiler combination like:
* <ul>
- * <li> Linux x86 / gcc </li>
- * <li> Linux x86_64 / gcc </li>
- * <li> Solaris Sparc / Sun Studio </li>
- * <li> Windows / Visual Studio </li>
- * <li> Windows / Code::Blocks+MinGW </li>
- * <li> ... </li>
+ * <li>Section \ref intro</li>
+ * <li>Section \ref user</li>
* </ul>
*
- * You may follow generic CMake usage instruction for building CERTI
- * on various platforms: <a
href="http://www.cmake.org/cmake/help/runningcmake.html";>Running CMake,
http://www.cmake.org/cmake/help/runningcmake.html://www.cmake.org/ </a>
- * or you may try to follow the below CERTI CMake usage.
- *
- * \subsection certi_sdk_TARGZ Tarball based SDK
- *
- * If you get a tarball source CERTI distribution such as you may found in the
download
- * section of the Savannah project
- * <a>http://download.savannah.nongnu.org/releases/certi/</a>,
- * you should follow these steps:
- * <ol>
- * <li>untar the archive: tar zxvf certi-\<version\>-Source.tar.gz
- * this should create a certi-\<version\>-Source directory
- * </li>
- * \verbatim
- tar zxvf certi-3.2.4-Source.tar.gz
- ... wait for tar ending ... \endverbatim
- * <li>Prepare separate build directory and run CMake
- * </li>
- * \verbatim
- mkdir build_certi
- cd build_certi
- cmake -DCMAKE_INSTALL_PREFIX=/path/to/install
/path/to/certi-\<version\>-Source
- ... wait for cmake run ending ... \endverbatim
- * <li>compile your certi</li>
- * \verbatim
- make
- ... wait the compilation end ... \endverbatim
- <li> Then you may either install CERTI or build
- a binary package that will be usable for installation</li>
- <ul>
- * <li>install CERTI</li>
- * \verbatim
- make install
- ... wait for make install end ... \endverbatim
- * <li>build your binary package </li>
- * \verbatim
- make package \endverbatim
- </ul>
- * </ol>
- * After that you will have a compiled and usable CERTI package.
- *
- */
-
-/**
- * @defgroup certi CERT Run Time Infrastructure (CERTI)
- * The CERTI is an Open Source HLA Run Time Infrastructure (RTI)
- * primarily developed by the Toulouse Center of ONERA
- * (http://www.onera.fr)
- * The CERTI itself consists in a set of libraries and tests applications.
- * @see HLA_Libraries the (normative) HLA Run Time Libraries
- * @see HLA_Helpers_Libraries some RTI-agnostic HLA Helper Libraries
- * @see CERTI_Libraries the private CERTI library.
- * @see CERTI_Applications Some applications bundled with CERTI.
- * More informations on
- * <A
HREF="http://savannah.nongnu.org/projects/certi";>http://savannah.nongnu.org/projects/certi</A>.
- */
-
-/**
- * @defgroup HLA_Libraries Normatives HLA libraries
- * This group of libraries contains the HLA/IEEE-1516 compliant normative
libraries.
- */
-
-/**
- * @defgroup CERTI_Libraries The CERTI libraries
- * The CERTI programming libraries.
- * @ingroup certi
- */
-
-/**
- * @defgroup HLA_Helper_Libraries NON-normative HLA helper libraries
- * This group of libraries contains helper libraries which are non normative
- * and may be used to ease the development of an HLA federate.
- * Those libraries are RTI agnostic, they may be used with other RTI than
CERTI.
- * @ingroup certi
- */
-
-/**
- * @defgroup CERTI_Applications Applications bundled with CERTI.
- * @ingroup certi
*/
Index: doc/index.html
===================================================================
RCS file: /sources/certi/certi/doc/index.html,v
retrieving revision 3.4
retrieving revision 3.5
diff -u -b -r3.4 -r3.5
--- doc/index.html 9 Oct 2008 23:39:55 -0000 3.4
+++ doc/index.html 11 Oct 2008 23:03:17 -0000 3.5
@@ -1,7 +1,8 @@
-<h1>CERTI Available documentation</h1>
+<h1>CERTI Available documentation set</h1>
+<p> Note that you may have only a part of this set installed </p>
<ul>
-<li><a href="install/html/index.html">CERTI installation documentation</a></li>
-<li><a href="user/html/index.html">CERTI user documentation</a></li>
-<li><a href="developer/html/index.html">CERTI developer documentation</a></li>
+<li><a href="Install/html/index.html">CERTI Installation documentation</a></li>
+<li><a href="User/html/index.html">CERTI User documentation</a></li>
+<li><a href="Developer/html/index.html">CERTI Developer documentation</a></li>
</ul>
Index: doc/CMakeLists.txt
===================================================================
RCS file: /sources/certi/certi/doc/CMakeLists.txt,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- doc/CMakeLists.txt 11 Oct 2008 21:40:16 -0000 1.7
+++ doc/CMakeLists.txt 11 Oct 2008 23:03:17 -0000 1.8
@@ -29,7 +29,7 @@
CONFIG_FILE certi_install.cnf
INPUT_FILES certi_install_header.html
certi_footer.html
DOC_TYPE "html;pdf"
- OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/install
+ OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/Install
COMMENTS "CERTI installation documentation"
VERBOSE)
ENDIF (BUILD_DOC_INSTALL)
@@ -40,7 +40,7 @@
CONFIG_FILE certi_user.cnf
INPUT_FILES certi_header.html certi_footer.html
DOC_TYPE "html;pdf"
- OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/user
+ OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/User
COMMENTS "CERTI user documentation"
)
ENDIF (BUILD_DOC_USER)
@@ -51,7 +51,7 @@
CONFIG_FILE certi_developer.cnf
INPUT_FILES certi_header.html certi_footer.html
DOC_TYPE "html"
- OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/developer
+ OUTPUT_DIR ${CMAKE_BINARY_DIR}/doc/Developer
COMMENTS "CERTI developer documentation"
)
ENDIF (BUILD_DOC_DEVELOPER)
Index: doc/certi_user.cnf.in
===================================================================
RCS file: /sources/certi/certi/doc/certi_user.cnf.in,v
retrieving revision 3.2
retrieving revision 3.3
diff -u -b -r3.2 -r3.3
--- doc/certi_user.cnf.in 11 Oct 2008 21:40:16 -0000 3.2
+++ doc/certi_user.cnf.in 11 Oct 2008 23:03:17 -0000 3.3
@@ -53,29 +53,19 @@
OUTPUT_LANGUAGE = English
-# This tag can be used to specify the encoding used in the generated output.
-# The encoding is not always determined by the language that is chosen,
-# but also whether or not the output is meant for Windows or non-Windows
users.
-# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
-# forces the Windows encoding (this is the default for the Windows binary),
-# whereas setting the tag to NO uses a Unix-style encoding (the default for
-# all platforms other than Windows).
-
-USE_WINDOWS_ENCODING = NO
-
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
# include brief member descriptions after the members that are listed in
# the file and class documentation (similar to JavaDoc).
# Set to NO to disable this.
-BRIEF_MEMBER_DESC = YES
+BRIEF_MEMBER_DESC = NO
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
# the brief description of a member or function before the detailed
description.
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
# brief descriptions will be completely suppressed.
-REPEAT_BRIEF = YES
+REPEAT_BRIEF = NO
# This tag implements a quasi-intelligent brief description abbreviator
# that is used to form the text in various listings. Each string
@@ -159,7 +149,7 @@
# member inherits the documentation from any documented member that it
# re-implements.
-INHERIT_DOCS = YES
+INHERIT_DOCS = NO
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
# tag is set to YES, then doxygen will reuse the documentation of the first
@@ -213,23 +203,23 @@
# Private class members and static file members will be hidden unless
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
-EXTRACT_ALL = YES
+EXTRACT_ALL = NO
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
# will be included in the documentation.
-EXTRACT_PRIVATE = YES
+EXTRACT_PRIVATE = NO
# If the EXTRACT_STATIC tag is set to YES all static members of a file
# will be included in the documentation.
-EXTRACT_STATIC = YES
+EXTRACT_STATIC = NO
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
# defined locally in source files will be included in the documentation.
# If set to NO only classes defined in header files are included.
-EXTRACT_LOCAL_CLASSES = YES
+EXTRACT_LOCAL_CLASSES = NO
# This flag is only useful for Objective-C code. When set to YES local
# methods, which are defined in the implementation section but not in
@@ -272,7 +262,7 @@
# to NO (the default) then the documentation will be excluded.
# Set it to YES to include the internal documentation.
-INTERNAL_DOCS = YES
+INTERNAL_DOCS = NO
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
# file names in lower-case letters. If set to YES upper-case letters are also
@@ -292,19 +282,19 @@
# will put a list of the files that are included by a file in the
documentation
# of that file.
-SHOW_INCLUDE_FILES = YES
+SHOW_INCLUDE_FILES = NO
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
# is inserted in the documentation for inline members.
-INLINE_INFO = YES
+INLINE_INFO = NO
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
# will sort the (detailed) documentation of file and class members
# alphabetically by member name. If set to NO the members will appear in
# declaration order.
-SORT_MEMBER_DOCS = YES
+SORT_MEMBER_DOCS = NO
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
# brief documentation of file, namespace and class members alphabetically
@@ -327,30 +317,30 @@
# disable (NO) the todo list. This list is created by putting \todo
# commands in the documentation.
-GENERATE_TODOLIST = YES
+GENERATE_TODOLIST = NO
# The GENERATE_TESTLIST tag can be used to enable (YES) or
# disable (NO) the test list. This list is created by putting \test
# commands in the documentation.
-GENERATE_TESTLIST = YES
+GENERATE_TESTLIST = NO
# The GENERATE_BUGLIST tag can be used to enable (YES) or
# disable (NO) the bug list. This list is created by putting \bug
# commands in the documentation.
-GENERATE_BUGLIST = YES
+GENERATE_BUGLIST = NO
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
# disable (NO) the deprecated list. This list is created by putting
# \deprecated commands in the documentation.
-GENERATE_DEPRECATEDLIST= YES
+GENERATE_DEPRECATEDLIST= NO
# The ENABLED_SECTIONS tag can be used to enable conditional
# documentation sections, marked by \if sectionname ... \endif.
-ENABLED_SECTIONS =
+ENABLED_SECTIONS = YES
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
# the initial value of a variable or define consists of for it to appear in
@@ -366,13 +356,13 @@
# at the bottom of the documentation of classes and structs. If set to YES the
# list will mention the files that were used to generate the documentation.
-SHOW_USED_FILES = YES
+SHOW_USED_FILES = NO
# If the sources in your project are distributed over multiple directories
# then setting the SHOW_DIRECTORIES tag to YES will show the directory
hierarchy
# in the documentation.
-SHOW_DIRECTORIES = YES
+SHOW_DIRECTORIES = NO
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
# doxygen should invoke to get the current version for each file (typically
from the
@@ -462,14 +452,13 @@
# should be searched for input files as well. Possible values are YES and NO.
# If left blank NO is used.
-RECURSIVE = YES
+RECURSIVE = NO
# The EXCLUDE tag can be used to specify files and/or directories that should
# excluded from the INPUT source files. This way you can easily exclude a
# subdirectory from a directory tree whose root is specified with the INPUT
tag.
-EXCLUDE = CVS \
- test/libgraphc
+EXCLUDE = CVS
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
# directories that are symbolic links (a Unix filesystem feature) are excluded
@@ -543,7 +532,7 @@
# Note: To get rid of all source code in the generated output, make sure also
# VERBATIM_HEADERS is set to NO.
-SOURCE_BROWSER = YES
+SOURCE_BROWSER = NO
# Setting the INLINE_SOURCES tag to YES will include the body
# of functions and classes directly in the documentation.
@@ -560,13 +549,13 @@
# then for each documented function all documented
# functions referencing it will be listed.
-REFERENCED_BY_RELATION = YES
+REFERENCED_BY_RELATION = NO
# If the REFERENCES_RELATION tag is set to YES (the default)
# then for each documented function all documented entities
# called/used by that function will be listed.
-REFERENCES_RELATION = YES
+REFERENCES_RELATION = NO
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
# will generate a verbatim copy of the header file for each class for
@@ -622,7 +611,7 @@
# each generated HTML page. If it is left blank doxygen will generate a
# standard header.
-HTML_HEADER = certi_header.html
+HTML_HEADER = certi_user_header.html
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
# each generated HTML page. If it is left blank doxygen will generate a
@@ -687,7 +676,7 @@
# top of each HTML page. The value NO (the default) enables the index and
# the value YES disables it.
-DISABLE_INDEX = NO
+DISABLE_INDEX = YES
# This tag can be used to set the number of enum values (range [1..20])
# that doxygen will group on one line in the generated HTML documentation.
@@ -701,7 +690,7 @@
# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
# probably better off using the HTML help feature.
-GENERATE_TREEVIEW = YES
+GENERATE_TREEVIEW = NO
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
# used to set the initial width (in pixels) of the frame in which the tree
@@ -722,7 +711,7 @@
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `latex' will be used as the default path.
-LATEX_OUTPUT = latex
+LATEX_OUTPUT = pdflatex
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
# invoked. If left blank `latex' will be used as the default command name.
@@ -1151,22 +1140,6 @@
DOTFILE_DIRS =
-# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_WIDTH = 1024
-
-# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
-# (in pixels) of the graphs generated by dot. If a graph becomes larger than
-# this value, doxygen will try to truncate the graph, so that it fits within
-# the specified constraint. Beware that most browsers cannot cope with very
-# large images.
-
-MAX_DOT_GRAPH_HEIGHT = 1024
-
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
# graphs generated by dot. A depth value of 3 means that only nodes reachable
# from the root by following a path via at most 3 edges will be shown. Nodes
Index: doc/DoxyTools.cmake
===================================================================
RCS file: /sources/certi/certi/doc/DoxyTools.cmake,v
retrieving revision 3.2
retrieving revision 3.3
diff -u -b -r3.2 -r3.3
--- doc/DoxyTools.cmake 11 Oct 2008 21:40:17 -0000 3.2
+++ doc/DoxyTools.cmake 11 Oct 2008 23:03:18 -0000 3.3
@@ -107,7 +107,8 @@
IF (genhtml)
MESSAGE(STATUS "Will install ${DoxyTools_OUTPUT_DIR}")
- INSTALL(DIRECTORY ${DoxyTools_OUTPUT_DIR} DESTINATION share/doc/certi)
+ CONFIGURE_FILE(doc_install.in ${DOCSET}_doc_install.cmake)
+ INSTALL(SCRIPT ${CMAKE_BINARY_DIR}/${DOCSET}_doc_install.cmake
COMPONENT DOC)
ENDIF (genhtml)
ENDMACRO(DoxyTools_ADD_DocSet)
\ No newline at end of file
Index: doc/certi_user.dox
===================================================================
RCS file: /sources/certi/certi/doc/certi_user.dox,v
retrieving revision 3.1
retrieving revision 3.2
diff -u -b -r3.1 -r3.2
--- doc/certi_user.dox 11 Oct 2008 21:40:17 -0000 3.1
+++ doc/certi_user.dox 11 Oct 2008 23:03:18 -0000 3.2
@@ -1,63 +1,7 @@
/**
- * \page install Installing CERTI SDK
+ * \page install Using CERTI
*
- * \addindex installation
- * CERTI SDK comes as either as an installer (binary) or compressed tar source
archives.
- * The primary distribution format is gzip compressed tar source archive
(.tar.gz)
- * or ZIP archive (.zip) and may be found on Savannah CERTI download area: <a
href="http://download.savannah.nongnu.org/releases/certi/";>
http://download.savannah.nongnu.org/releases/certi/ </a>.
- *
- * CERTI build system uses <a href="http://www.cmake.org/";>CMake,
http://www.cmake.org/ </a>
- * which is a cross-platform build system generator. CMake should be used to
- * compile CERTI SDK on a variety of platform/compiler combination like:
- * <ul>
- * <li> Linux x86 / gcc </li>
- * <li> Linux x86_64 / gcc </li>
- * <li> Solaris Sparc / Sun Studio </li>
- * <li> Windows / Visual Studio </li>
- * <li> Windows / Code::Blocks+MinGW </li>
- * <li> ... </li>
- * </ul>
- *
- * You may follow generic CMake usage instruction for building CERTI
- * on various platforms: <a
href="http://www.cmake.org/cmake/help/runningcmake.html";>Running CMake,
http://www.cmake.org/cmake/help/runningcmake.html://www.cmake.org/ </a>
- * or you may try to follow the below CERTI CMake usage.
- *
- * \section certi_sdk_TARGZ Tarball based SDK
- *
- * If you get a tarball source CERTI distribution such as you may found in the
download
- * section of the Savannah project
- * <a>http://download.savannah.nongnu.org/releases/certi/</a>,
- * you should follow these steps:
- * <ol>
- * <li>untar the archive: tar zxvf certi-\<version\>-Source.tar.gz
- * this should create a certi-\<version\>-Source directory
- * </li>
- * \verbatim
- tar zxvf certi-3.2.4-Source.tar.gz
- ... wait for tar ending ... \endverbatim
- * <li>Prepare separate build directory and run CMake
- * </li>
- * \verbatim
- mkdir build_certi
- cd build_certi
- cmake -DCMAKE_INSTALL_PREFIX=/path/to/install
/path/to/certi-\<version\>-Source
- ... wait for cmake run ending ... \endverbatim
- * <li>compile your certi</li>
- * \verbatim
- make
- ... wait the compilation end ... \endverbatim
- <li> Then you may either install CERTI or build
- a binary package that will be usable for installation</li>
- <ul>
- * <li>install CERTI</li>
- * \verbatim
- make install
- ... wait for make install end ... \endverbatim
- * <li>build your binary package </li>
- * \verbatim
- make package \endverbatim
- </ul>
- * </ol>
- * After that you will have a compiled and usable CERTI package.
+ * \addindex using
*
+ * Using CERTI blah blah ....
*/
Index: doc/certi_user_header.html
===================================================================
RCS file: doc/certi_user_header.html
diff -N doc/certi_user_header.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ doc/certi_user_header.html 11 Oct 2008 23:03:17 -0000 3.1
@@ -0,0 +1,5 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head><meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+<title>$title</title>
+<link href="$relpath$certi.css" rel="stylesheet" type="text/css">
+</head><body>
Index: doc/doc_install.in
===================================================================
RCS file: doc/doc_install.in
diff -N doc/doc_install.in
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ doc/doc_install.in 11 Oct 2008 23:03:17 -0000 3.1
@@ -0,0 +1,2 @@
+MESSAGE(STATUS "Now installing doc set <@DOCSET@> ...")
+EXECUTE_PROCESS(COMMAND @CMAKE_COMMAND@ -E copy_directory
@DoxyTools_OUTPUT_DIR@ @CMAKE_INSTALL_PREFIX@/share/doc/certi/@DOCSET@)
\ No newline at end of file
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [certi-cvs] certi CMakeLists.txt doc/certi_user_doc.tree do...,
certi-cvs <=