You can subscribe to this list here.
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(51) |
Nov
(8) |
Dec
(13) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2010 |
Jan
(32) |
Feb
(47) |
Mar
(6) |
Apr
(19) |
May
(7) |
Jun
(19) |
Jul
(39) |
Aug
(51) |
Sep
(39) |
Oct
(18) |
Nov
(10) |
Dec
(27) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <den...@us...> - 2010-07-26 14:49:11
|
Revision: 245 http://stdair.svn.sourceforge.net/stdair/?rev=245&view=rev Author: denis_arnaud Date: 2010-07-26 14:49:05 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Doc] Set up the comments in a few classes so that Doxygen better gets them. Modified Paths: -------------- trunk/stdair/stdair/STDAIR_Service.hpp trunk/stdair/stdair/bom/BomContent.hpp trunk/stdair/stdair/bom/BomKey.hpp trunk/stdair/stdair/bom/BomStructure.hpp trunk/stdair/stdair/bom/Inventory.hpp trunk/stdair/stdair/bom/InventoryContent.hpp Modified: trunk/stdair/stdair/STDAIR_Service.hpp =================================================================== --- trunk/stdair/stdair/STDAIR_Service.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/STDAIR_Service.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,13 @@ +/** + * @brief Handle on the StdAir library context + * @author Anh Quan Nguyen <qua...@us...> + * @date 20/01/2010 + * @detail StdAir aims at providing a clean API, and the corresponding + * C++ implementation, for the basis of Airline IT Business Object + * Model (BOM), that is, to be used by several other Open Source + * projects, such as RMOL and OpenTREP<br> + * Install the StdAir library for Airline IT Standard C++ fundaments. + */ #ifndef __STDAIR_SVC_STDAIR_SERVICE_HPP #define __STDAIR_SVC_STDAIR_SERVICE_HPP @@ -12,69 +22,103 @@ namespace stdair { - // Forward declarations + /// Forward declarations class BomRoot; - /** Interface for the STDAIR Services. */ + /** + * @brief Interface for the STDAIR Services + */ class STDAIR_Service { public: // ////////// Constructors and destructors ////////// - /** Constructor. - <br>The init() method is called; see the corresponding documentation - for more details. - <br>Moreover, a reference on an output stream is given, so - that log outputs can be directed onto that stream. - @param const BasLogParams& Parameters for the output log stream. */ + /** + * @brief Constructor. + * <br>The init() method is called; see the corresponding + * documentation for more details. + * <br>Moreover, a reference on an output stream is given, so + * that log outputs can be directed onto that stream. + * @param[in] const BasLogParams& Parameters for the output log stream. + */ STDAIR_Service (const BasLogParams&); - /** Constructor. - <br>The init() method is called; see the corresponding documentation - for more details. - <br>A reference on an output stream is given, so - that log outputs can be directed onto that stream. - <br>Moreover, database connection parameters are given, so - that database requests can use the corresponding access. - @param const BasLogParams& Parameters for the output log stream. - @param const BasDBParams& Parameters for the database session. */ + /** + * @brief Constructor. + * <br>The init() method is called; see the corresponding + * documentation for more details. + * <br>A reference on an output stream is given, so + * that log outputs can be directed onto that stream. + * <br>Moreover, database connection parameters are given, so + * that database requests can use the corresponding access. + * @param[in] const BasLogParams& Parameters for the output log stream. + * @param[in] const BasDBParams& Parameters for the database session. + */ STDAIR_Service (const BasLogParams&, const BasDBParams&); - /** Destructor. */ + /** + * @brief Destructor. + */ ~STDAIR_Service(); // ///////////////// Getters /////////////////// - /** Get a reference on the BomRoot object. - <br>If the service context has not been initialised, that - method throws an exception (failing assertion). */ + /** + * @brief Get a reference on the BomRoot object. + * <br>If the service context has not been initialised, that + * method throws an exception (failing assertion). + * @param[out] BomRoot& Reference on the BomRoot. + */ BomRoot& getBomRoot () const { return _bomRoot; } private: // /////// Construction and Destruction helper methods /////// - /** Default constructor. */ + /** + * @brief Default constructor. + */ STDAIR_Service (); - /** Default copy constructor. */ + + /** + * @brief Default copy constructor. + * @param[in] const STDAIR_Service& Reference on the STDAIR_Service handler + * to be copied. + */ STDAIR_Service (const STDAIR_Service&); - /** Initialise the log. */ + + /** + * @brief Initialise the log. + * @param[in] const BasLogParams& Parameters for the output log stream. + */ void logInit (const BasLogParams&); - /** Initialise the database session. */ + + /** + * @brief Initialise the database session. + * @param[in] const BasDBParams& Parameters for the database session. + */ void dbInit (const BasDBParams&); - /** Initialise. - <br>The static instance of the log service (Logger object) is created. - <br>The static instance of the database session manager - (DBSessionManager object) is created. - <br>The static instance of the FacSupervisor object, itself referencing - all the other objects (factories and BOM), is created. - <br>As those three objects are static, there is no need to store them - in any service context. However, some lock mechanism may be needed - in order to secure the access to the corresponding resources. */ + + /** + * @brief Initialise. + * <br>The static instance of the log service (Logger object) is created. + * <br>The static instance of the database session manager + * (DBSessionManager object) is created. + * <br>The static instance of the FacSupervisor object, itself referencing + * all the other objects (factories and BOM), is created. + * <br>As those three objects are static, there is no need to store them + * in any service context. However, some lock mechanism may be needed + * in order to secure the access to the corresponding resources. + */ void init (); - /** Finalise. */ + + /** + * @brief Finalise. + */ void finalise (); private: // /////////////// Attributes /////////////// - /** Root of the BOM tree. */ + /** + * @brief Root of the BOM tree. + */ BomRoot& _bomRoot; }; } Modified: trunk/stdair/stdair/bom/BomContent.hpp =================================================================== --- trunk/stdair/stdair/bom/BomContent.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/bom/BomContent.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,8 @@ +/** + * @defgroup BomContent Content part of the Business Object Model (BOM) + * @author Anh Quan Nguyen <qua...@us...> + * @date 20/01/2010 + */ #ifndef __STDAIR_BOM_BOMCONTENT_HPP #define __STDAIR_BOM_BOMCONTENT_HPP @@ -7,12 +12,14 @@ // STL #include <iosfwd> #include <string> -// STDAIR +// StdAir #include <stdair/STDAIR_Types.hpp> namespace stdair { - /** Base class for the Business Object Model (BOM) layer. */ + /** + * @brief Base class for the Business Object Model (BOM) layer + */ class BomContent { friend class FacBomContent; public: Modified: trunk/stdair/stdair/bom/BomKey.hpp =================================================================== --- trunk/stdair/stdair/bom/BomKey.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/bom/BomKey.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,9 @@ +/** + * @defgroup BomKey Part of the Business Object Model (BOM) handling + * (hash-like )keys + * @author Anh Quan Nguyen <qua...@us...> + * @date 20/01/2010 + */ #ifndef __STDAIR_BOM_BOMKEY_HPP #define __STDAIR_BOM_BOMKEY_HPP @@ -12,31 +18,43 @@ namespace stdair { - /** Base class for the keys of Business Object Model (BOM) layer. - <br>Note that that key allows to differentiate two objects - at the same level only. For instance, the segment-date key allows - to differentiate two segment-dates under a given flight-date, - but does not allow to differentiate two segemnt-dates in general. */ + /** + * @brief Base class for the keys of Business Object Model (BOM) layer. + * <br>Note that that key allows to differentiate two objects + * at the same level only. For instance, the segment-date key allows + * to differentiate two segment-dates under a given flight-date, + * but does not allow to differentiate two segemnt-dates in general. + */ struct BomKey_T { public: // /////////// Display support methods ///////// - /** Dump a Business Object Key into an output stream. - @param ostream& the output stream. */ + /** + * @brief Dump a Business Object Key into an output stream. + * @param[inout] ostream& the output stream. + */ virtual void toStream (std::ostream& ioOut) const {} - /** Read a Business Object Key from an input stream. - @param istream& the input stream. */ + /** + * @brief Read a Business Object Key from an input stream. + * @param[inout] istream& the input stream. + */ virtual void fromStream (std::istream& ioIn) {} - /** Get the serialised version of the Business Object Key. - <br>That string is unique, at the level of a given Business Object, - when among children of a given parent Business Object. - <br>For instance, "H" and "K" allow to differentiate among two - marketing classes for the same segment-date. */ + /** + * @brief Get the serialised version of the Business Object Key. + * <br>That string is unique, at the level of a given Business Object, + * when among children of a given parent Business Object. + * <br>For instance, "H" and "K" allow to differentiate among two + * marketing classes for the same segment-date. + * @param[out] const std::string The serialised version of the Business + * Object Key. + */ virtual const std::string toString() const { return std::string("Hello!"); } - /** Default destructor. */ + /** + * @brief Default destructor. + */ virtual ~BomKey_T() {} }; Modified: trunk/stdair/stdair/bom/BomStructure.hpp =================================================================== --- trunk/stdair/stdair/bom/BomStructure.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/bom/BomStructure.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,8 @@ +/** + * @defgroup BomStructure Structure part of the Business Object Model (BOM) + * @author Anh Quan Nguyen <qua...@us...> + * @date 20/01/2010 + */ #ifndef __STDAIR_BOM_BOMSTRUCTURE_HPP #define __STDAIR_BOM_BOMSTRUCTURE_HPP @@ -12,7 +17,9 @@ namespace stdair { - /** Base class for the Business Object Model (BOM) tree structure. */ + /** + * @brief Base class for the Business Object Model (BOM) tree structure. + */ class BomStructure { friend class FacBomStructure; friend class FacBomContent; Modified: trunk/stdair/stdair/bom/Inventory.hpp =================================================================== --- trunk/stdair/stdair/bom/Inventory.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/bom/Inventory.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,6 @@ +/** + * @ingroup BomStructure + */ #ifndef __STDAIR_BOM_INVENTORY_HPP #define __STDAIR_BOM_INVENTORY_HPP @@ -18,6 +21,7 @@ #include <stdair/bom/FlightPeriodTypes.hpp> namespace stdair { + // Forward declarations class BomRoot; class FlightDate; @@ -26,8 +30,10 @@ struct FlightDateKey_T; struct FlightPeriodKey_T; - /** Class representing the actual functional/business content for - an airline inventory. */ + /** + * @brief Class representing the actual functional/business content for + * an airline inventory. + */ class Inventory : public InventoryContent { friend class FacBomContent; Modified: trunk/stdair/stdair/bom/InventoryContent.hpp =================================================================== --- trunk/stdair/stdair/bom/InventoryContent.hpp 2010-07-26 12:09:21 UTC (rev 244) +++ trunk/stdair/stdair/bom/InventoryContent.hpp 2010-07-26 14:49:05 UTC (rev 245) @@ -1,3 +1,6 @@ +/** + * @ingroup BomContent + */ #ifndef __STDAIR_BOM_INVENTORYCONTENT_HPP #define __STDAIR_BOM_INVENTORYCONTENT_HPP @@ -4,15 +7,18 @@ // ////////////////////////////////////////////////////////////////////// // Import section // ////////////////////////////////////////////////////////////////////// -// STDAIR +// StdAir #include <stdair/bom/BomContent.hpp> #include <stdair/bom/InventoryKey.hpp> namespace stdair { - /** Class representing the actual attributes for an airline inventory. */ + /** + * @brief Class representing the actual attributes for an airline inventory + */ class InventoryContent : public BomContent { public : + // Type definitions /** Definition allowing to retrieve the associated BOM key type. */ typedef InventoryKey_T Key_T; This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-26 12:09:28
|
Revision: 244 http://stdair.svn.sourceforge.net/stdair/?rev=244&view=rev Author: denis_arnaud Date: 2010-07-26 12:09:21 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Doc] The main links in the table of content are now taken into account by Doxygen. Modified Paths: -------------- trunk/stdair/doc/local/index.doc Modified: trunk/stdair/doc/local/index.doc =================================================================== --- trunk/stdair/doc/local/index.doc 2010-07-26 08:40:48 UTC (rev 243) +++ trunk/stdair/doc/local/index.doc 2010-07-26 12:09:21 UTC (rev 244) @@ -55,8 +55,9 @@ \section about About StdAir StdAir is a C++ library of classes and functions modeling typical -airline IT business objects. For instance, it is used by the Airline -Schedule C++ library project (http://www.sourceforge.net/projects/air-sched). +airline IT business objects. For instance, it is used by the C++ +Revenue Management Open Library project +(http://sourceforge.net/projects/rmol/). StdAir makes an extensive use of existing open-source libraries for increased functionality, speed and accuracy. In particular <a This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-26 08:40:54
|
Revision: 243 http://stdair.svn.sourceforge.net/stdair/?rev=243&view=rev Author: denis_arnaud Date: 2010-07-26 08:40:48 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Doc] The main links in the table of content are now taken into account by Doxygen. Modified Paths: -------------- trunk/stdair/doc/local/authors.doc Modified: trunk/stdair/doc/local/authors.doc =================================================================== --- trunk/stdair/doc/local/authors.doc 2010-07-26 08:33:24 UTC (rev 242) +++ trunk/stdair/doc/local/authors.doc 2010-07-26 08:40:48 UTC (rev 243) @@ -1,5 +1,5 @@ /*! -\page authors StdAir People +\page authors People \section admins Project Admins @@ -25,7 +25,9 @@ \section distributors Distribution Maintainers -- Denis Arnaud <den...@us...> (\ref N) +- <a href="http://fedoraproject.org">Fedora</a>/<a href="http://www.redhat.com">RedHat</a>: + Denis Arnaud <den...@us...> (\ref N) +- <a href="http://www.debian.org">Debian</a>: Emmanuel Bastien <eba...@us...> (\ref N) \note \anchor N This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-26 08:33:32
|
Revision: 242 http://stdair.svn.sourceforge.net/stdair/?rev=242&view=rev Author: denis_arnaud Date: 2010-07-26 08:33:24 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Doc] The main links in the table of content are now taken into account by Doxygen. Modified Paths: -------------- trunk/stdair/doc/local/codingrules.doc trunk/stdair/doc/local/features.doc trunk/stdair/doc/local/howto_release.doc trunk/stdair/doc/local/index.doc trunk/stdair/doc/local/installation.doc trunk/stdair/doc/local/verification.doc Modified: trunk/stdair/doc/local/codingrules.doc =================================================================== --- trunk/stdair/doc/local/codingrules.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/codingrules.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -1,5 +1,5 @@ /*! -\page codingrules Coding Rules +\page coding_rules Coding Rules In the following sections we describe the naming conventions which are used for files, classes, structures, local variables, and global variables. Modified: trunk/stdair/doc/local/features.doc =================================================================== --- trunk/stdair/doc/local/features.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/features.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -1,5 +1,5 @@ /*! -\page features Main features of StdAir +\page features Main features A short list of the main features of StdAir is given below sorted in different categories. Many more features and functions exist and for these we refer to Modified: trunk/stdair/doc/local/howto_release.doc =================================================================== --- trunk/stdair/doc/local/howto_release.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/howto_release.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -1,5 +1,5 @@ /*! -\page howto_release How to release a new version of StdAir +\page howto_release Make a new release \htmlonly <!-- Modified: trunk/stdair/doc/local/index.doc =================================================================== --- trunk/stdair/doc/local/index.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/index.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -11,17 +11,17 @@ \endhtmlonly \section getting_started Getting Started -- <a href="features.html">Features</a> -- <a href="installation.html">Installation</a> -- <a href="linking.html">Linking with StdAir</a> -- <a href="users__guide.html">Short Introduction to StdAir</a> -- <a href="tutorial.html">Some Tutorial Examples</a> -- <a href="verification.html">StdAir Verification</a> -- <a href="copyright.html">Copyright and License</a> -- <a href="help__wanted.html">Make a Difference</a> -- <a href="howto__release.html">Make a new release</a> -- <a href="authors.html">Authors</a> +- \ref features +- \ref installation +- \ref linking +- \ref users_guide +- \ref tutorial +- \ref verification +- \ref copyright +- \ref help_wanted +- \ref howto_release +- \ref authors \section at_sourceforge StdAir at SourceForge - <a href="http://sourceforge.net/projects/stdair/">Project page</a> @@ -36,9 +36,9 @@ \section development StdAir Development - <a href="http://stdair.svn.sourceforge.net/viewvc/stdair/">SVN Repository</a> -- <a href="codingrules.html">Coding Rules</a> -- <a href="documentation.html">Documentation Rules</a> -- <a href="test.html">Test Rules</a> +- \ref coding_rules +- \ref documentation +- \ref test \section external_libs External Libraries Modified: trunk/stdair/doc/local/installation.doc =================================================================== --- trunk/stdair/doc/local/installation.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/installation.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -1,5 +1,5 @@ /*! -\page installation StdAir Installation +\page installation Installation \section toc Table of Contents - \ref rpm_linux Modified: trunk/stdair/doc/local/verification.doc =================================================================== --- trunk/stdair/doc/local/verification.doc 2010-07-26 07:58:20 UTC (rev 241) +++ trunk/stdair/doc/local/verification.doc 2010-07-26 08:33:24 UTC (rev 242) @@ -1,5 +1,5 @@ /*! -\page verification StdAir Supported Systems +\page verification Supported Systems \section toc Table of Contents - \ref intro This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-26 07:58:26
|
Revision: 241 http://stdair.svn.sourceforge.net/stdair/?rev=241&view=rev Author: denis_arnaud Date: 2010-07-26 07:58:20 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Packaging] The RPM specification file is no longer generated by configure. Property Changed: ---------------- trunk/stdair/ Property changes on: trunk/stdair ___________________________________________________________________ Modified: svn:ignore - configure config.log config.status libtool aclocal.m4 autom4te.cache Makefile.in Makefile INSTALL stdair.spec stdair-config stdair.m4 stdair.pc stdair-*.tar.* + configure config.log config.status libtool aclocal.m4 autom4te.cache Makefile.in Makefile INSTALL stdair-config stdair.m4 stdair.pc stdair-*.tar.* This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-26 07:47:46
|
Revision: 240 http://stdair.svn.sourceforge.net/stdair/?rev=240&view=rev Author: denis_arnaud Date: 2010-07-26 07:47:40 +0000 (Mon, 26 Jul 2010) Log Message: ----------- [Packaging] The RPM specification file is no longer generated by configure. Modified Paths: -------------- trunk/stdair/configure.ac Added Paths: ----------- trunk/stdair/stdair.spec Removed Paths: ------------- trunk/stdair/stdair.spec.in Modified: trunk/stdair/configure.ac =================================================================== --- trunk/stdair/configure.ac 2010-07-25 21:55:40 UTC (rev 239) +++ trunk/stdair/configure.ac 2010-07-26 07:47:40 UTC (rev 240) @@ -210,7 +210,6 @@ Makefile stdair-config stdair.pc - stdair.spec stdair.m4 stdair/Makefile stdair/basic/Makefile Copied: trunk/stdair/stdair.spec (from rev 239, trunk/stdair/stdair.spec.in) =================================================================== --- trunk/stdair/stdair.spec (rev 0) +++ trunk/stdair/stdair.spec 2010-07-26 07:47:40 UTC (rev 240) @@ -0,0 +1,121 @@ +# +%global mydocs __tmp_docdir +# +Name: stdair +Version: 99.99.99 +Release: 1%{?dist} + +Summary: C++ Standard Airline IT Object Library + +Group: System Environment/Libraries +License: LGPLv2 +URL: http://sourceforge.net/projects/%{name}/ +Source0: http://downloads.sourceforge.net/%{name}/%{name}-%{version}.tar.bz2 +%{?el5:BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)} + +BuildRequires: boost-devel +BuildRequires: cppunit-devel +#Requires: + +%description +%{name} aims at providing a clean API, and the corresponding C++ +implementation, for the basis of Airline IT Business Object Model (BOM), +that is, to be used by several other Open Source projects, such as RMOL, +Air-Sched, Travel-CCM, OpenTREP, etc. + +Install the %{name} package if you need a library for Airline IT Standard +C++ fundaments. + +%package devel +Summary: Header files, libraries and development documentation for %{name} +Group: Development/Libraries +Requires: %{name} = %{version}-%{release} +Requires: pkgconfig +Requires(post): info +Requires(preun): info + +%description devel +This package contains the header files, static libraries and +development documentation for %{name}. If you would like to develop +programs using %{name}, you will need to install %{name}-devel. + +%package doc +Summary: HTML documentation for the %{name} library +Group: Documentation +%if 0%{?fedora} >= 10 +BuildArch: noarch +BuildRequires: texlive-latex +%endif +%if 0%{?fedora} < 10 +BuildRequires: tetex-latex +%endif +%{?el5:BuildRequires: tetex-latex} +BuildRequires: doxygen, ghostscript + +%description doc +This package contains the documentation in the HTML format of the %{name} +library. The documentation is the same as at the %{name} web page. + + +%prep +%setup -q +# find ./doc -type f -perm 755 -exec chmod 644 {} \; +# Fix some permissions and formats +rm -f INSTALL +chmod -x AUTHORS ChangeLog COPYING NEWS README +find . -type f -name '*.[hc]pp' -exec chmod 644 {} \; + + +%build +%configure --disable-static +make %{?_smp_mflags} + +%install +rm -rf $RPM_BUILD_ROOT +make install DESTDIR=$RPM_BUILD_ROOT +# remove unpackaged files from the buildroot +rm -f $RPM_BUILD_ROOT%{_infodir}/dir +rm -f $RPM_BUILD_ROOT%{_libdir}/lib%{name}.la +rm -f $RPM_BUILD_ROOT%{_libdir}/libextracppunit.la +rm -rf %{mydocs} && mkdir -p %{mydocs} +mv $RPM_BUILD_ROOT%{_docdir}/%{name}-%{version}/html %{mydocs} + +%clean +rm -rf $RPM_BUILD_ROOT + +%post -p /sbin/ldconfig + +%postun -p /sbin/ldconfig + + +%files +%defattr(-,root,root,-) +%doc AUTHORS ChangeLog COPYING NEWS README +%{_bindir}/%{name} +%{_libdir}/lib*.so.* +%{_mandir}/man3/%{name}.3.* + +%files devel +%defattr(-,root,root,-) +%{_includedir}/%{name} +%{_includedir}/extracppunit +%{_bindir}/%{name}-config +%{_libdir}/lib%{name}.so +%{_libdir}/libextracppunit.so +%{_libdir}/pkgconfig/%{name}.pc +%{_datadir}/aclocal/%{name}.m4 +%{_mandir}/man1/%{name}-config.1.* + +%files doc +%defattr(-,root,root,-) +%doc %{mydocs}/html +%doc AUTHORS ChangeLog COPYING NEWS README + + +%changelog +* Sun Jul 26 2010 Son Nguyen Kim <ngu...@gm...> 99.99.99-1 +- Upstream update + +* Wed Jul 13 2010 Son Nguyen Kim <ngu...@gm...> 0.1.0-1 +- First RPM release + Deleted: trunk/stdair/stdair.spec.in =================================================================== --- trunk/stdair/stdair.spec.in 2010-07-25 21:55:40 UTC (rev 239) +++ trunk/stdair/stdair.spec.in 2010-07-26 07:47:40 UTC (rev 240) @@ -1,118 +0,0 @@ -# -%define mydocs __tmp_docdir -# -Name: @PACKAGE@ -Version: @VERSION@ -Release: @RPM_RELEASE@%{?dist} - -Summary: C++ Standard Airline IT Object Library - -Group: System Environment/Libraries -License: LGPLv2 -URL: http://sourceforge.net/projects/%{name}/ -Source0: http://downloads.sourceforge.net/%{name}/%{name}-%{version}.tar.bz2 -BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) - -BuildRequires: boost-devel -BuildRequires: cppunit-devel -#Requires: - -%description -@PACKAGE_NAME@ aims at providing a clean API, and the corresponding C++ -implementation, for the basis of Airline IT Business Object Model (BOM), -that is, to be used by several other Open Source projects, such as RMOL, -Air-Sched, Travel-CCM, OpenTREP, etc. - -Install the %{name} package if you need a library for Airline IT Standard -C++ fundaments. - -%package devel -Summary: Header files, libraries and development documentation for %{name} -Group: Development/Libraries -Requires: %{name} = %{version}-%{release} -Requires: pkgconfig -Requires(post): info -Requires(preun): info - -%description devel -This package contains the header files, static libraries and -development documentation for %{name}. If you would like to develop -programs using %{name}, you will need to install %{name}-devel. - -%package doc -Summary: HTML documentation for the @PACKAGE_NAME@ library -Group: Documentation -%if 0%{?fedora} >= 10 -BuildArch: noarch -BuildRequires: texlive-latex -%endif -%if 0%{?fedora} < 10 -BuildRequires: tetex-latex -%endif -%{?el5:BuildRequires: tetex-latex} -BuildRequires: doxygen, ghostscript - -%description doc -This package contains the documentation in the HTML format of the @PACKAGE_NAME@ -library. The documentation is the same as at the @PACKAGE_NAME@ web page. - - -%prep -%setup -q -# find ./doc -type f -perm 755 -exec chmod 644 {} \; -# Fix some permissions and formats -rm -f INSTALL -chmod -x AUTHORS ChangeLog COPYING NEWS README -find . -type f -name '*.[hc]pp' -exec chmod 644 {} \; - - -%build -%configure --disable-static -make %{?_smp_mflags} - -%install -rm -rf $RPM_BUILD_ROOT -make install DESTDIR=$RPM_BUILD_ROOT -# remove unpackaged files from the buildroot -rm -f $RPM_BUILD_ROOT%{_infodir}/dir -rm -f $RPM_BUILD_ROOT%{_libdir}/lib%{name}.la -rm -f $RPM_BUILD_ROOT%{_libdir}/libextracppunit.la -rm -rf %{mydocs} && mkdir -p %{mydocs} -mv $RPM_BUILD_ROOT%{_docdir}/%{name}-%{version}/html %{mydocs} - -%clean -rm -rf $RPM_BUILD_ROOT - -%post -p /sbin/ldconfig - -%postun -p /sbin/ldconfig - - -%files -%defattr(-,root,root,-) -%doc AUTHORS ChangeLog COPYING NEWS README -%{_bindir}/%{name} -%{_libdir}/lib*.so.* -%{_mandir}/man3/%{name}.3.* - -%files devel -%defattr(-,root,root,-) -%{_includedir}/%{name} -%{_includedir}/extracppunit -%{_bindir}/%{name}-config -%{_libdir}/lib%{name}.so -%{_libdir}/libextracppunit.so -%{_libdir}/pkgconfig/%{name}.pc -%{_datadir}/aclocal/%{name}.m4 -%{_mandir}/man1/%{name}-config.1.* - -%files doc -%defattr(-,root,root,-) -%doc %{mydocs}/html -%doc AUTHORS ChangeLog COPYING NEWS README - - -%changelog -* Wed Jul 13 2010 Son Nguyen Kim <ngu...@gm...> 0.1.0-1 -- First RPM release - This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:55:46
|
Revision: 239 http://stdair.svn.sourceforge.net/stdair/?rev=239&view=rev Author: denis_arnaud Date: 2010-07-25 21:55:40 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Branch 0.2.0] Updated the RPM specification file. Modified Paths: -------------- branches/stdair/0.2.0/main/stdair.spec.in Modified: branches/stdair/0.2.0/main/stdair.spec.in =================================================================== --- branches/stdair/0.2.0/main/stdair.spec.in 2010-07-25 21:37:43 UTC (rev 238) +++ branches/stdair/0.2.0/main/stdair.spec.in 2010-07-25 21:55:40 UTC (rev 239) @@ -113,6 +113,9 @@ %changelog -* Wed Jul 13 2010 Son Nguyen Kim <ngu...@gm...> 0.1.0-1 +* Sun Jul 25 2010 Denis Arnaud <ngu...@gm...> 0.2.0-1 +- Upstream update + +* Wed Jul 13 2010 Son Nguyen Kim <ngu...@gm...> 0.1.0-1 - First RPM release This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:37:49
|
Revision: 238 http://stdair.svn.sourceforge.net/stdair/?rev=238&view=rev Author: denis_arnaud Date: 2010-07-25 21:37:43 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Doc] Updated the links of the 'how-to release' document. Modified Paths: -------------- trunk/stdair/doc/local/howto_release.doc Modified: trunk/stdair/doc/local/howto_release.doc =================================================================== --- trunk/stdair/doc/local/howto_release.doc 2010-07-25 21:31:46 UTC (rev 237) +++ trunk/stdair/doc/local/howto_release.doc 2010-07-25 21:37:43 UTC (rev 238) @@ -41,23 +41,23 @@ \verbatim cd ~/dev cd stdairsvn/branches/stdair -mkdir 0.1.0 -svn add 0.1.0 -svn ci -m "[Branch 0.1.0] Prepared the branch 0.1.0 to be copied from head of the trunk." +mkdir 0.2.0 +svn add 0.2.0 +svn ci -m "[Branch 0.2.0] Prepared the branch 0.2.0 to be copied from head of the trunk." \endverbatim \section check_release_revision Check Subversion revision for the release Check to which Subversion revision the release corresponds to. For instance -the <a href="http://sourceforge.net/apps/trac/stdair/changeset/220/">StdAir - release 0.1.0 corresponds to Subversion revision r218</a>. -The trunk <tt>configure.ac</tt> file specifies a fake release number, namely +the <a href="http://sourceforge.net/apps/trac/stdair/changeset/233/">StdAir + release 0.2.0 corresponds to Subversion revision r233</a>. +The trunk \c configure.ac file specifies a fake release number, namely 99.99.99, for current (head) development. When a release is made, two Subversion revisions are committed with, as the sole change, the release number within -the <tt>configure.ac</tt> file: +the \c configure.ac file: - one revision is committed with the to-be-released version number (e.g., - 0.1.0) and commit message prefixed with "[Release x.y.z]", + 0.2.0) and commit message prefixed with "[Release x.y.z]", - and another one with the release number back to 99.99.99 and message stating "[Release] Back to working version (99.99.99)." . @@ -75,18 +75,18 @@ Create a release branch by copying the <a href="https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair">source tree</a> to be released, from the found revision (e.g., -<a href="http://sourceforge.net/apps/trac/stdair/changeset/218">r218</a>) +<a href="http://sourceforge.net/apps/trac/stdair/changeset/233">r233</a>) into the dedicated -<a href="https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0">'branches' sub-directory of the Subversion repository</a>, e.g.: +<a href="https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.2.0">'branches' sub-directory of the Subversion repository</a>, e.g.: \verbatim -svn copy -r218 \ +svn copy -r233 \ https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair \ - https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0/main \ - -m "[Release] Created the main 0.1.0 release branch, from revision r218." + https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.2.0/main \ + -m "[Release] Created the main 0.2.0 release branch, from revision r233." \endverbatim Check the results:<br> -\c firefox -new-tab \"<a href="http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main">http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main</a>\" +\c firefox -new-tab \"<a href="http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.2.0/main">http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.2.0/main</a>\" \section checkout_new_release Check-out the new release @@ -95,7 +95,7 @@ may be made (for instance, on the RPM specification file): \verbatim cd ~/dev -cd stdairsvn/branches/stdair/0.1.0 +cd stdairsvn/branches/stdair/0.2.0 svn up cd main \endverbatim @@ -121,13 +121,13 @@ Create the distribution packages using the following command:<br> \verbatim cd ~/dev -cd stdairsvn/branches/stdair/0.1.0/main +cd stdairsvn/branches/stdair/0.2.0/main ./autogen.sh && make distcheck \endverbatim This will configure, compile and check the package. The output packages will -be named, for instance, \c stdair-0.1.0.tar.gz and \c stdair-0.1.0.tar.bz2. +be named, for instance, \c stdair-0.2.0.tar.gz and \c stdair-0.2.0.tar.bz2. \section generate_rpm_packages Generation the RPM packages @@ -136,7 +136,7 @@ <a href="http://fedoraproject.org">Fedora</a>/<a href="http://www.redhat.com">RedHat</a>): \verbatim cd ~/dev -cd stdairsvn/branches/stdair/0.1.0/main +cd stdairsvn/branches/stdair/0.2.0/main ./autogen.sh && make dist \endverbatim @@ -144,10 +144,10 @@ available in the system. \verbatim cp stdair.spec ~/dev/packages/SPECS \ - && cp stdair-0.1.0.tar.bz2 ~/dev/packages/SOURCES + && cp stdair-0.2.0.tar.bz2 ~/dev/packages/SOURCES cd ~/dev/packages/SPECS rpmbuild -ba stdair.spec -rpmlint -i ../SPECS/stdair.spec ../SRPMS/stdair-0.1.0-1.fc13.src.rpm \ +rpmlint -i ../SPECS/stdair.spec ../SRPMS/stdair-0.2.0-1.fc13.src.rpm \ ../RPMS/i686/stdair-* \endverbatim @@ -167,9 +167,9 @@ \c make dist-html and \c make dist-tex The output documentation packages will be named, for instance: -- \c stdair-doc-0.1.0.tar.gz and \c stdair-doc-0.1.0.tar.bz2 for the +- \c stdair-doc-0.2.0.tar.gz and \c stdair-doc-0.2.0.tar.bz2 for the HTML documentation. -- \c stdair-pdf-0.1.0.tar.gz and \c stdair-pdf-0.1.0.tar.bz2 for the +- \c stdair-pdf-0.2.0.tar.gz and \c stdair-pdf-0.2.0.tar.bz2 for the PDF documentation. @@ -186,7 +186,7 @@ - <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service#Accessingyourfileswithothertools">synchronise them with rsync and SSH</a>: \verbatim cd ~/dev -cd stdairsvn/branches/stdair/0.1.0/main +cd stdairsvn/branches/stdair/0.2.0/main rsync -aiv doc/html joe,st...@we...:htdocs/ \endverbatim where \c -aiv options mean: This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:31:52
|
Revision: 237 http://stdair.svn.sourceforge.net/stdair/?rev=237&view=rev Author: denis_arnaud Date: 2010-07-25 21:31:46 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Release] Created the main 0.2.0 release branch, from revision r233. Added Paths: ----------- branches/stdair/0.2.0/main/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:28:14
|
Revision: 236 http://stdair.svn.sourceforge.net/stdair/?rev=236&view=rev Author: denis_arnaud Date: 2010-07-25 21:28:07 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Branch 0.2.0] Prepared the branch 0.2.0 to be copied from head of the trunk. Added Paths: ----------- branches/stdair/0.2.0/ Removed Paths: ------------- branches/0.2.0/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:27:18
|
Revision: 235 http://stdair.svn.sourceforge.net/stdair/?rev=235&view=rev Author: denis_arnaud Date: 2010-07-25 21:27:11 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Branch 0.2.0] Prepared the branch 0.2.0 to be copied from head of the trunk. Added Paths: ----------- branches/0.2.0/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:26:13
|
Revision: 234 http://stdair.svn.sourceforge.net/stdair/?rev=234&view=rev Author: denis_arnaud Date: 2010-07-25 21:26:06 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Release] Back to working version (99.99.99). Modified Paths: -------------- trunk/stdair/configure.ac Modified: trunk/stdair/configure.ac =================================================================== --- trunk/stdair/configure.ac 2010-07-25 21:25:05 UTC (rev 233) +++ trunk/stdair/configure.ac 2010-07-25 21:26:06 UTC (rev 234) @@ -2,7 +2,7 @@ #------------------------------------------------------------------- AC_PREREQ(2.59) AC_COPYRIGHT([Copyright (C) 2007-2010 Denis Arnaud <den...@us...>]) -AC_INIT([STDAIR],[0.2.0],[den...@us...],[stdair]) +AC_INIT([STDAIR],[99.99.99],[den...@us...],[stdair]) AC_CONFIG_HEADER([stdair/config.h]) AC_CONFIG_SRCDIR([stdair/bom/BomKey.hpp]) AC_CONFIG_AUX_DIR([config]) @@ -15,7 +15,7 @@ AC_SUBST(RPM_RELEASE) # Shared library versioning -GENERIC_LIBRARY_VERSION="0:2:0" +GENERIC_LIBRARY_VERSION="99:99:99" # | | | # +------+ | +---+ # | | | This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:25:11
|
Revision: 233 http://stdair.svn.sourceforge.net/stdair/?rev=233&view=rev Author: denis_arnaud Date: 2010-07-25 21:25:05 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Release 0.2.0] Release 0.2.0. Modified Paths: -------------- trunk/stdair/configure.ac Modified: trunk/stdair/configure.ac =================================================================== --- trunk/stdair/configure.ac 2010-07-25 21:23:53 UTC (rev 232) +++ trunk/stdair/configure.ac 2010-07-25 21:25:05 UTC (rev 233) @@ -2,7 +2,7 @@ #------------------------------------------------------------------- AC_PREREQ(2.59) AC_COPYRIGHT([Copyright (C) 2007-2010 Denis Arnaud <den...@us...>]) -AC_INIT([STDAIR],[99.99.99],[den...@us...],[stdair]) +AC_INIT([STDAIR],[0.2.0],[den...@us...],[stdair]) AC_CONFIG_HEADER([stdair/config.h]) AC_CONFIG_SRCDIR([stdair/bom/BomKey.hpp]) AC_CONFIG_AUX_DIR([config]) @@ -15,7 +15,7 @@ AC_SUBST(RPM_RELEASE) # Shared library versioning -GENERIC_LIBRARY_VERSION="99:99:99" +GENERIC_LIBRARY_VERSION="0:2:0" # | | | # +------+ | +---+ # | | | This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-25 21:24:02
|
Revision: 232 http://stdair.svn.sourceforge.net/stdair/?rev=232&view=rev Author: denis_arnaud Date: 2010-07-25 21:23:53 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Doc] Improved (a lot) the generated documentation. Modified Paths: -------------- trunk/stdair/Makefile.am trunk/stdair/doc/Makefile.am trunk/stdair/doc/local/authors.doc trunk/stdair/doc/local/codingrules.doc trunk/stdair/doc/local/documentation.doc trunk/stdair/doc/local/features.doc trunk/stdair/doc/local/help_wanted.doc trunk/stdair/doc/local/index.doc trunk/stdair/doc/local/installation.doc trunk/stdair/doc/local/linking.doc trunk/stdair/doc/local/sources.mk trunk/stdair/doc/local/verification.doc trunk/stdair/doc/sourceforge/howto_release_stdair.html trunk/stdair/doc/tutorial/tutorial.doc Added Paths: ----------- trunk/stdair/doc/local/howto_release.doc Modified: trunk/stdair/Makefile.am =================================================================== --- trunk/stdair/Makefile.am 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/Makefile.am 2010-07-25 21:23:53 UTC (rev 232) @@ -44,11 +44,11 @@ dist-html: $(MAKE) -C doc dist-html -dist-tex: - $(MAKE) -C doc dist-tex +dist-pdf: + $(MAKE) -C doc dist-pdf -snapshot: snapshot-src snapshot-html snapshot-tex +snapshot: snapshot-src snapshot-html snapshot-pdf snapshot-src: @@ -57,10 +57,10 @@ snapshot-html: $(MAKE) -C doc dist-html html_tarname=@PACKAGE_TARNAME@-doc-`date +"%Y%m%d"` -snapshot-tex: - $(MAKE) -C doc dist-tex tex_tarname=@PACKAGE_TARNAME@-tex-`date +"%Y%m%d"` +snapshot-pdf: + $(MAKE) -C doc dist-pdf pdf_tarname=@PACKAGE_TARNAME@-pdf-`date +"%Y%m%d"` -upload: upload-src upload-html upload-tex +upload: upload-src upload-html upload-pdf upload-src: dist @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-@VERSION@.tar.gz \ @@ -70,6 +70,6 @@ @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-doc-@VERSION@.tar.gz \ @PACKAGE_TARNAME@-doc-@VERSION@.tar.bz2 -upload-tex: dist-tex - @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-tex-@VERSION@.tar.gz \ - @PACKAGE_TARNAME@-tex-@VERSION@.tar.bz2 +upload-pdf: dist-pdf + @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-pdf-@VERSION@.tar.gz \ + @PACKAGE_TARNAME@-pdf-@VERSION@.tar.bz2 Modified: trunk/stdair/doc/Makefile.am =================================================================== --- trunk/stdair/doc/Makefile.am 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/Makefile.am 2010-07-25 21:23:53 UTC (rev 232) @@ -15,10 +15,11 @@ docdir = @docdir@ html_tarname = @PACKAGE_TARNAME@-doc-@PACKAGE_VERSION@ -tex_tarname = @PACKAGE_TARNAME@-tex-@PACKAGE_VERSION@ +pdf_tarname = @PACKAGE_TARNAME@-pdf-@PACKAGE_VERSION@ -noinst_DATA = sourceforge/howto_release_stdair.html.in -EXTRA_DIST = $(noinst_DATA) +#noinst_DATA = sourceforge/howto_release_stdair.html.in +#EXTRA_DIST = $(noinst_DATA) +EXTRA_DIST = # Targets all-local: html-local @@ -50,13 +51,13 @@ bzip2 -9 -c > $(top_builddir)/$(html_tarname).tar.bz2 rm -rf $(top_builddir)/$(html_tarname) -dist-tex: html-local - cp -a $(top_builddir)/doc/latex $(top_builddir)/$(tex_tarname) - tar chof - $(top_builddir)/$(tex_tarname) | \ - gzip --best -c > $(top_builddir)/$(tex_tarname).tar.gz - tar chof - $(top_builddir)/$(tex_tarname) | \ - bzip2 -9 -c > $(top_builddir)/$(tex_tarname).tar.bz2 - rm -rf $(top_builddir)/$(tex_tarname) +dist-pdf: html-local + cp -a $(top_builddir)/doc/latex $(top_builddir)/$(pdf_tarname) + tar chof - $(top_builddir)/$(pdf_tarname) | \ + gzip --best -c > $(top_builddir)/$(pdf_tarname).tar.gz + tar chof - $(top_builddir)/$(pdf_tarname) | \ + bzip2 -9 -c > $(top_builddir)/$(pdf_tarname).tar.bz2 + rm -rf $(top_builddir)/$(pdf_tarname) install-data-local: html-local $(mkinstalldirs) $(DESTDIR)$(docdir) Modified: trunk/stdair/doc/local/authors.doc =================================================================== --- trunk/stdair/doc/local/authors.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/authors.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -10,23 +10,22 @@ \section developers Developers -- Daniel Perez <dan...@us...> (\ref N) - Christophe Lacombe <dd...@us...> (\ref N) \section retired Retired Developers -- Rémi Casacci (\ref N) +- Son Nguyen Kim <sng...@us...> (\ref N) \section contributors Contributors -- Emmanuel Bastien (\ref N) +- Emmanuel Bastien <eba...@us...> (\ref N) \section distributors Distribution Maintainers -- Denis Arnaud <den...@us...> +- Denis Arnaud <den...@us...> (\ref N) \note \anchor N Modified: trunk/stdair/doc/local/codingrules.doc =================================================================== --- trunk/stdair/doc/local/codingrules.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/codingrules.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -7,80 +7,46 @@ \section cr_variables Default Naming Rules for Variables -Variables are named using lower-case letters and words are separated -using under-score. Abbreviations, when used in variable names, are also -written with lower-case letters. Examples: +Variables names follow Java naming conventions. +Examples: +- \c `lNumberOfPassengers' +- \c `lSeatAvailability' -<ul> -<li> \c `fft_size' </li> -<li> \c `nrof_paths' </li> -<li> \c `my_variable_name' </li> -</ul> -Some variable names or parts of variable names are commonly used in -several different functions and files to denote the same thing. For -instance the following common names and prefixes should be used: - -<ul> -<li> \c `rows' - number of rows in a matrix </li> -<li> \c `cols' - number of columns in a matrix </li> -<li> \c `nrof_' - number of ... </li> -</ul> - - -\section cr_files Default Naming Rules for Files - -Files are named using lower-case letters and words are separated using -under-score. Abbreviations, when used in file names, are also written -with lower-case letters. - -Source files are named using <tt>`.cpp'</tt> suffix, whereas header -files end with <tt>`.h'</tt> extension. Examples: - -<ul> -<li> <tt>`my_file.h'</tt> </li> -<li> <tt>`my_file.cpp'</tt> </li> -</ul> - - \section cr_functions Default Naming Rules for Functions -Function names are named using lower-case letters and words are -separated using under-score. Abbreviations, when used in function -names, are also written with lower-case letters. This rule applies -both to stand-alone functions as well as to member functions of -classes. Example: +Function names follow Java naming conventions. Example: +- \c `int \c myFunctionName (\c const \c int& \c a, \c int \c b)' -<ul> -<li> <tt>int my_function_name(int a, int b)</tt> </li> -</ul> - \section cr_classes Default Naming Rules for Classes and Structures Each new word in a class or structure name should always start with a capital letter and the words should be separated with an under-score. Abbreviations are written with capital letters. Examples: +- \c `MyClassName' +- \c `MyStructName' -<ul> -<li> \c `My_Class_Name' </li> -<li> \c `My_Struct_Name' </li> -<li> \c `OFDM' </li> -</ul> +\section cr_files Default Naming Rules for Files +Files are named after the C++ class names. + +Source files are named using \c `.cpp' suffix, whereas header +files end with \c `.hpp' extension. Examples: +- \c `FlightDate.hpp' +- \c `SegmentDate.cpp' + + + \section cr_classes_functionality Default Functionality of Classes All classes that are configured by input parameters should include: +- default empty constructor +- one or more additional constructor(s) that takes input parameters + and initializes the class instance +- setup function, preferably named \c `setup' or \c `set_parameters' -<ul> -<li> default empty constructor </li> -<li> one or more additional constructor(s) that takes input parameters -and initializes the class instance </li> -<li> setup function, preferably named \c `setup' or \c -`set_parameters' </li> -</ul> - Explicit destructor functions are not required, unless they are needed. It shall not be possible to use any of the other member functions unless the class has been properly initiated with the input Modified: trunk/stdair/doc/local/documentation.doc =================================================================== --- trunk/stdair/doc/local/documentation.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/documentation.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -3,26 +3,24 @@ \section doc_general General Rules -All classes in IT++ should be properly documented with Doxygen -comments in include (`.h') files. Source (`.cpp') files should be +All classes in StdAir should be properly documented with Doxygen +comments in include (\c `.hpp') files. Source (\c `.cpp') files should be documented according to a normal standard for well documented C++ code. -An example of how the interface of a class shall be documented in IT++ +An example of how the interface of a class shall be documented in StdAir is shown here: \verbatim /*! - * \brief Brief description of My_Class here + * \brief Brief description of MyClass here * - * Detailed description of My_Class here. With example code if needed. + * Detailed description of MyClass here. With example code if needed. */ -class My_Class { - +class MyClass { public: - //! Default constructor - My_Class(void) { setup_done = false; } + MyClass(void) { setup_done = false; } /*! * \brief Constructor that initializes the class with parameters @@ -32,10 +30,10 @@ * \param[in] param1 Description of \a param1 here * \param[in] param2 Description of \a param2 here */ - My_Class(TYPE1 param1, TYPE2 param2) { setup(param1, param2); } + MyClass(TYPE1 param1, TYPE2 param2) { setup(param1, param2); } /*! - * \brief Setup function for My_Class + * \brief Setup function for MyClass * * Detailed description of the setup function here if needed * @@ -45,23 +43,23 @@ void setup(TYPE1 param1, TYPE2 param2); /*! - * \brief Brief description of member_function1 + * \brief Brief description of memberFunction1 * - * Detailed description of member_function1 here if needed + * Detailed description of memberFunction1 here if needed * * \param[in] param1 Description of \a param1 here * \param[in] param2 Description of \a param2 here * \param[in,out] param3 Description of \a param3 here * \return Description of the return value here */ - TYPE4 member_function1(TYPE1 param1, TYPE2 param2, TYPE3 ¶m3); + TYPE4 memberFunction1(TYPE1 param1, TYPE2 param2, TYPE3 ¶m3); private: - bool setup_done; /*!< Variable that checks if the class is properly + bool _setupDone; /*!< Variable that checks if the class is properly initialized with parameters */ - TYPE1 private_variable1; //!< Short description of private_variable1 here - TYPE2 private_variable2; //!< Short description of private_variable2 here + TYPE1 _privateVariable1; //!< Short description of _privateVariable1 here + TYPE2 _privateVariable2; //!< Short description of _privateVariable2 here }; \endverbatim @@ -85,14 +83,13 @@ * * ------------------------------------------------------------------------- * - * IT++ - C++ library of mathematical, signal processing, speech processing, - * and communications classes and functions + * StdAir - C++ Standard Airline IT Object Library * - * Copyright (C) 1995-2005 (see AUTHORS file for a list of contributors) + * Copyright (C) 2009-2010 (see AUTHORS file for a list of contributors) * * This program is free software; you can redistribute it and/or modify - * it under the terms of the GNU General Public License as published by - * the Free Software Foundation; either version 2 of the License, or + * it under the terms of the GNU Lesser General Public License as published + * by the Free Software Foundation; either version 2 of the License, or * (at your option) any later version. * * This program is distributed in the hope that it will be useful, @@ -125,20 +122,20 @@ The following example shows how to document the function \c -`my_function' and how to add it to the group \c `my_group': +`myFunction' and how to add it to the group \c `my_group': \verbatim /*! - * \brief Brief description of my_function here + * \brief Brief description of myFunction here * \ingroup my_group * - * Detailed description of my_function here + * Detailed description of myFunction here * * \param[in] param1 Description of \a param1 here * \param[in] param2 Description of \a param2 here * \return Description of the return value here */ -TYPE3 my_function(TYPE1 param1, TYPE2 ¶m2); +TYPE3 myFunction(TYPE1 param1, TYPE2 ¶m2); \endverbatim */ Modified: trunk/stdair/doc/local/features.doc =================================================================== --- trunk/stdair/doc/local/features.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/features.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -1,75 +1,29 @@ /*! -\page features Main features of IT++ +\page features Main features of StdAir -A short list of the main features of IT++ is given below sorted in different +A short list of the main features of StdAir is given below sorted in different categories. Many more features and functions exist and for these we refer to the reference documentation. -\section prog_features Programming features -- templated array and stack container classes -- input and file argument parser -- timing functions and classes +\section airline_it_bom Standard Airline IT Business Object Model (BOM) +- (Airline) Network-related classes: + - Network, ReachableUniverse +- (Air) Travel-related classes: + - TravelSolution, OriginDestination, +- (Airline) Inventory-related classes: + - Inventory, FlightDate, SegmentDate, SegmentCabin, BookingClass, + LegDate, LegCabin, + Bucket +- (Airline) Schedule-related classes: + - FlightPeriod, SegmentPeriod, LegPeriod +- (Simulated) Passenger-related demand classes: + - DemandStream, BookingRequest +- (Air) Price-related classes: + - YieldStore -\section math_features Basic mathematical features -- templated vector and matrix classes -- sparse vectors and matrix classes -- elementary functions on vectors and matrices -- statistics classes and functions -- matrix decompositions such as eigenvalue, Cholesky, LU, Schur, SVD, and QR -- solving linear system of equations (including over and underdetermined) -- random number generation (Mersenne Twister generator) -- binary and Galois types (both scalar and vector and matrices) -- integration of 1-dimensional functions -- unconditional nonlinear optimization (Quasi-Newton search) +\section architecture Architecture of the StdAir library +- Separate structure and content classes +- <a href="http://www.boost.org/doc/libs/1_43_0/libs/fusion/doc/html/index.html">Boost.Fusion</a> - -\section sigproc_features Signal processing -- filter functions and classes -- frequency domain filtering -- FFT, DFT, DCT, and Hadamard transforms -- time and frequency domain windows -- evaluating and finding roots of polynomials (and inverse operations) -- filter design functions -- fast independent component analysis (fast ICA) - - -\section comm_features Communications -- modulators (BPSK, PSK, PAM, QAM) -- vector modulators (e.g. for OFDM and MIMO) -- OFDM and CDMA modulators -- pulse shaping filters (including RC and RRC) -- binary symmetric (BSC) and additive white Gaussian Noise (AWGN) channels -- multipath fading channels (both frequency-flat and frequency-selective) -- COST 207, COST 257, and ITU channel models -- Hamming, extended Golay, and CRC codes -- BCH and Reed-Solomon codes -- convolutional and punctured convolutional codes -- recursive convolutional codes -- turbo codes -- interleavers - - -\section protocol_features Protocol simulation -- event-based simulation classes -- signal and slots for simplified syntax -- TCP clients and servers -- selective repeat ARQ -- queue classes -- packet generators - - -\section srccode_features Source coding -- Scalar Quantizer (SQ) and Vector Quantizer (VQ) classes and functions for - training of these -- LPC, LSF, and cepstrum parameter calculation for speech processing -- Gaussian Mixture Modeling -- reading and saving several different audiofile formats -- reading and saving images in PNM format - - -\section other_features Other features -- binary file format for most built in and IT++ types -- fixed-point scalar, vector and matrix types - */ Modified: trunk/stdair/doc/local/help_wanted.doc =================================================================== --- trunk/stdair/doc/local/help_wanted.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/help_wanted.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -1,29 +1,29 @@ /*! \page help_wanted Make a Difference -<b>Do not ask what IT++ can do for you. Ask what you can do for IT++.</b> +<b>Do not ask what StdAir can do for you. Ask what you can do for StdAir.</b> -You can help us to develop the IT++ library. There are always a lot of things +You can help us to develop the StdAir library. There are always a lot of things you can do: -- Start using IT++ -- Tell your friends about IT++ and help them to get started using it +- Start using StdAir +- Tell your friends about StdAir and help them to get started using it - If you find a bug, report it to us. Without your help we can never hope to produce a bug free code. - Help us to improve the documentation by providing information about documentation bugs -- Answer support requests in the IT++ discussion forums on SourceForge. If -you know the answer to a question, help others to overcome their IT++ +- Answer support requests in the StdAir discussion forums on SourceForge. If +you know the answer to a question, help others to overcome their StdAir problems. - Help us to improve our algorithms. If you know of a better way (e.g. that is faster or requires less memory) to implement some of our algorithms, then let us know. -- Help us to port IT++ to new platforms. If you manage to compile IT++ on a +- Help us to port StdAir to new platforms. If you manage to compile StdAir on a new platform, then tell us how you did it. -- Send us your code. If you have a good IT++ compatible code, which you can -release under the GPL, and you think it should be included in IT++, then +- Send us your code. If you have a good StdAir compatible code, which you can +release under the GPL, and you think it should be included in StdAir, then send it to us. -- Become an IT++ developer. Send us an e-mail and tell what you can do for -IT++. +- Become an StdAir developer. Send us an e-mail and tell what you can do for +StdAir. */ Copied: trunk/stdair/doc/local/howto_release.doc (from rev 231, trunk/stdair/doc/sourceforge/howto_release_stdair.html) =================================================================== --- trunk/stdair/doc/local/howto_release.doc (rev 0) +++ trunk/stdair/doc/local/howto_release.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -0,0 +1,216 @@ +/*! +\page howto_release How to release a new version of StdAir + +\htmlonly +<!-- +The following tags are permitted: a, b, blockquote, br, code, dd, div, +dl, dt, em, hr, i, li, ol, p, pre, strong, tt, ul, u. All other tags will be +stripped. All tags aside from the following must be closed: br, hr, li, p. +Failure to close tags may result in HTML output which is not rendered +properly. Any style attributes or on* attributes (such as mouseover) will be +stripped. JavaScript will result in the total stripping of HTML tags from +your input. Please limit your input to properly formed HTML snippets +conforming to the above rules. +--> +\endhtmlonly + +\section description Introduction + +This document describes briefly the recommended procedure of releasing +a new version of StdAir using a Linux development machine and the +SourceForge project site. + +The following steps are required to make a release of the distribution package. + + +\section initialisation Initialisation + +Check out locally the full +<a href="https://stdair.svn.sourceforge.net/svnroot/stdair">Subversion project</a>: +\verbatim +cd ~ +mkdir -p dev +cd ~/dev +svn co https://stdair.svn.sourceforge.net/svnroot/stdair stdairsvn +\endverbatim + + +\section branch_preparation Branch preparation + +Prepare the branch for its creation on the Subversion repository: +\verbatim +cd ~/dev +cd stdairsvn/branches/stdair +mkdir 0.1.0 +svn add 0.1.0 +svn ci -m "[Branch 0.1.0] Prepared the branch 0.1.0 to be copied from head of the trunk." +\endverbatim + +\section check_release_revision Check Subversion revision for the release + +Check to which Subversion revision the release corresponds to. For instance +the <a href="http://sourceforge.net/apps/trac/stdair/changeset/220/">StdAir + release 0.1.0 corresponds to Subversion revision r218</a>. +The trunk <tt>configure.ac</tt> file specifies a fake release number, namely +99.99.99, +for current (head) development. When a release is made, two Subversion +revisions are committed with, as the sole change, the release number within +the <tt>configure.ac</tt> file: +- one revision is committed with the to-be-released version number (e.g., + 0.1.0) and commit message prefixed with "[Release x.y.z]", +- and another one with the release number back to 99.99.99 and message stating + "[Release] Back to working version (99.99.99)." +. +That way, it is then easy to spot the starting point of any release within +the Subversion repository, with something like: +\verbatim +cd ~/dev +cd stdairsvn/trunk/stdair +svn log configure.ac | less +\endverbatim + + +\section create_release_branch Create the release branch + +Create a release branch by copying the +<a href="https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair">source + tree</a> to be released, from the found revision (e.g., +<a href="http://sourceforge.net/apps/trac/stdair/changeset/218">r218</a>) +into the dedicated +<a href="https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0">'branches' sub-directory of the Subversion repository</a>, e.g.: +\verbatim +svn copy -r218 \ + https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair \ + https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0/main \ + -m "[Release] Created the main 0.1.0 release branch, from revision r218." +\endverbatim + +Check the results:<br> +\c firefox -new-tab \"<a href="http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main">http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main</a>\" + + +\section checkout_new_release Check-out the new release + +Check-out the release StdAir sources from the branch, so that patches +may be made (for instance, on the RPM specification file): +\verbatim +cd ~/dev +cd stdairsvn/branches/stdair/0.1.0 +svn up +cd main +\endverbatim + + +\section alter_released_files Alter released files + +<b>Only if needed</b>, alter a few files on the branch. + +<b>Note that the release branch is not the place where to develop for a +release.</b> +The <b>release</b> branch is aimed at keeping track of a release and of all +the patches having made their way into that branch, so that the software +can always be generated according to that release. + +Developments for a particular release should be made on the trunk (e.g., by +adding features not activated by default, but activated for the release +developers only) or, if really needed, on a dedicated <b>development</b> branch. + + +\section create_packages Create distribution packages + +Create the distribution packages using the following command:<br> +\verbatim +cd ~/dev +cd stdairsvn/branches/stdair/0.1.0/main +./autogen.sh && make distcheck +\endverbatim + + +This will configure, compile and check the package. The output packages will +be named, for instance, \c stdair-0.1.0.tar.gz and \c stdair-0.1.0.tar.bz2. + + +\section generate_rpm_packages Generation the RPM packages + +Optionally, generate the RPM package (for instance, for +<a href="http://fedoraproject.org">Fedora</a>/<a href="http://www.redhat.com">RedHat</a>): +\verbatim +cd ~/dev +cd stdairsvn/branches/stdair/0.1.0/main +./autogen.sh && make dist +\endverbatim + +To perform this step, autoconf, automake and libtool tools have to be +available in the system. +\verbatim +cp stdair.spec ~/dev/packages/SPECS \ + && cp stdair-0.1.0.tar.bz2 ~/dev/packages/SOURCES +cd ~/dev/packages/SPECS +rpmbuild -ba stdair.spec +rpmlint -i ../SPECS/stdair.spec ../SRPMS/stdair-0.1.0-1.fc13.src.rpm \ + ../RPMS/i686/stdair-* +\endverbatim + + +\section update_changelog Update distributed change log + +Update the \c NEWS and \c ChangeLog files with appropriate +information, including what has changed since the previous release. Then +commit the changes into the +<a href="https://sourceforge.net/apps/trac/stdair/browser">StdAir's + Subversion (SVN) repository</a>. + + +\section create_doc_packages Create the documentation packages + +Create the documentation packages using the following command: +\c make dist-html and \c make dist-tex + +The output documentation packages will be named, for instance: +- \c stdair-doc-0.1.0.tar.gz and \c stdair-doc-0.1.0.tar.bz2 for the + HTML documentation. +- \c stdair-pdf-0.1.0.tar.gz and \c stdair-pdf-0.1.0.tar.bz2 for the + PDF documentation. + + +\section upload_files Upload the files to SourceForge + +Upload the distribution and documentation packages to the SourceForge server. +Check +<a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download#SCP">SourceForge help page on uploading software</a>. + + +\section upload_doc Upload the documentation to SourceForge + +In order to update the Web site files, either: +- <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service#Accessingyourfileswithothertools">synchronise them with rsync and SSH</a>: +\verbatim +cd ~/dev +cd stdairsvn/branches/stdair/0.1.0/main +rsync -aiv doc/html joe,st...@we...:htdocs/ +\endverbatim +where \c -aiv options mean: + - \c -a: archive/mirror mode; equals \c -rlptgoD + (no \c -H, \c -A, \c -X) + - \c -v: increase verbosity + - \c -i: output a change-summary for all updates +- or use the + <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service">SourceForge Shell service</a>. + + +\section post_news Make a new post + +- submit a new entry in the <a href="https://sourceforge.net/news/submit.php?group_id=267760">SourceForge project-related news feed</a> +- make a new post on the <a href="https://sourceforge.net/apps/wordpress/stdair/wp-admin/">SourceForge hosted WordPress blog</a> +- and update, if necessary, +<a href="https://sourceforge.net/apps/trac/stdair/report">Trac tickets</a>. + + +\section send_announce Send an email on the announcement mailing-list + +Finally, you should send an announcement to + <a href="mailto:std...@li...">std...@li...</a> + (see <a href="https://lists.sourceforge.net/lists/listinfo/stdair-announce">https://lists.sourceforge.net/lists/listinfo/stdair-announce</a> + for the archives) + +*/ Modified: trunk/stdair/doc/local/index.doc =================================================================== --- trunk/stdair/doc/local/index.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/index.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -8,47 +8,46 @@ <div style="float:right; width:200px; background-color: #eeeeff; border: 1px solid #b0b0b0; margin: 0 0 10px 20px; padding: 10px; font-size: 90%;"> +\endhtmlonly -<b>Getting Started:</b> -<ul> -<li><a href="features.html">Features</a></li> -<li><a href="installation.html">Installation</a></li> -<li><a href="linking.html">Linking with StdAir</a></li> -<li><a href="users_guide.html">Short Introduction to StdAir</a></li> -<li><a href="tutorial.html">Some Tutorial Examples</a></li> -<li><a href="verification.html">StdAir Verification</a></li> -<li><a href="copyright.html">Copyright and License</a></li> -<li><a href="help_wanted.html">Make a Difference</a></li> -<li><a href="authors.html">Authors</a></li> -</ul> +\section getting_started Getting Started +- <a href="features.html">Features</a> +- <a href="installation.html">Installation</a> +- <a href="linking.html">Linking with StdAir</a> +- <a href="users__guide.html">Short Introduction to StdAir</a> +- <a href="tutorial.html">Some Tutorial Examples</a> +- <a href="verification.html">StdAir Verification</a> +- <a href="copyright.html">Copyright and License</a> +- <a href="help__wanted.html">Make a Difference</a> +- <a href="howto__release.html">Make a new release</a> +- <a href="authors.html">Authors</a> -<a href="http://sourceforge.net/projects/stdair/"><b>StdAir at SourceForge:</b></a> -<ul> -<li><a href="http://sourceforge.net/project/showfiles.php?group_id=267760">Download StdAir</a></li> -<li><a href="http://stdair.sourceforge.net/RPM-GPG-KEY-freshrpms-free">RPM-GPG-Key</a> for StdAir RPMs (save the file, and type 'rpm --import RPM-GPG-KEY-freshrpms-free' as root)</li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882290">Bug Reports</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882293">Feature Requests</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882292">Submit Patches</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882291">Support Request</a></li> -<li><a href="http://sourceforge.net/mail/?group_id=267760">Mailing lists</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613897">Discuss about Development issues</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613896">Ask for Help</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613895">Discuss StdAir</a></li> -</ul> -<b>StdAir Development:</b> -<ul> -<li><a href="http://stdair.svn.sourceforge.net/viewvc/stdair/">SVN Repository</a></li> -<li><a href="codingrules.html">Coding Rules</a></li> -<li><a href="documentation.html">Documentation Rules</a></li> -<li><a href="test.html">Test Rules</a></li> -</ul> +\section at_sourceforge StdAir at SourceForge +- <a href="http://sourceforge.net/projects/stdair/">Project page</a> +- <a href="http://sourceforge.net/project/showfiles.php?group_id=267760">Download StdAir</a> +- <a href="https://sourceforge.net/apps/trac/stdair/newticket">Open a ticket fora bug or feature</a> +- <a href="http://sourceforge.net/mail/?group_id=267760">Mailing lists</a> +- <a href="https://sourceforge.net/apps/phpbb/stdair/">Forums</a> + - <a href="https://sourceforge.net/apps/phpbb/stdair/viewforum.php?f=1">Discuss about Development issues</a> + - <a href="https://sourceforge.net/apps/phpbb/stdair/viewforum.php?f=2">Ask for Help</a> + - <a href="https://sourceforge.net/apps/phpbb/stdair/viewforum.php?f=3">Discuss StdAir</a> -<b>External Libraries:</b> -<ul> -<li><a href="http://www.gnu.org/software/gsl">GSL</a></li> -</ul> +\section development StdAir Development +- <a href="http://stdair.svn.sourceforge.net/viewvc/stdair/">SVN Repository</a> +- <a href="codingrules.html">Coding Rules</a> +- <a href="documentation.html">Documentation Rules</a> +- <a href="test.html">Test Rules</a> + + +\section external_libs External Libraries +- <a href="http://www.boost.org">Boost (C++ STL extensions)</a> +- <a href="http://dev.mysql.com/">MySQL client</a> +- <a href="http://soci.sourceforge.net/">SOCI (C++ DB API)</a> + + +\htmlonly </div> <!-- end of left margin --> \endhtmlonly Modified: trunk/stdair/doc/local/installation.doc =================================================================== --- trunk/stdair/doc/local/installation.doc 2010-07-25 16:06:47 UTC (rev 231) +++ trunk/stdair/doc/local/installation.doc 2010-07-25 21:23:53 UTC (rev 232) @@ -1,597 +1,542 @@ /*! -\page installation IT++ Installation +\page installation StdAir Installation \section toc Table of Contents +- \ref rpm_linux - \ref requirements -- \ref download -- \ref compilation -- \ref macosx -- \ref localinst -- \ref msvc +- \ref basic_instructions +- \ref compilers +- \ref compiling_for_multi_arch +- \ref installation_names +- \ref optional_features +- \ref particular_systems +- \ref specifying_system_type +- \ref sharing_defaults +- \ref defining_variables +- \ref configure_invocation -\section requirements IT++ Requirements +\section rpm_linux Fedora/RedHat Linux distributions -IT++ should compile without errors or warnings on most GNU/Linux systems, +Note that on +<a href="http://fedoraproject.org">Fedora</a>/<a href="http://www.redhat.com">RedHat</a> +Linux distributions, RPM packages are available and can be installed +with your usual package manager. For instance:<br> +<code> yum -y install stdair-devel stdair-doc </code> + +RPM packages can also be available on the +<a href="http://sourceforge.net/project/showfiles.php?group_id=267760">SourceForge download site</a>. + + +\section requirements StdAir Requirements + +StdAir should compile without errors or warnings on most GNU/Linux systems, on UNIX systems like Solaris SunOS, and on POSIX based environments for Microsoft Windows like Cygwin or MinGW with MSYS. It can be also built on Microsoft Windows NT/2000/XP using Microsoft's Visual C++ .NET, but our support for this compiler is limited. For GNU/Linux, SunOS, Cygwin and MinGW we assume that you have at least the following GNU software installed on your computer: -- <a href="http://www.gnu.org/software/make/">GNU make</a>, version 3.72.1 -or later (check version with <tt>`make --version'</tt>) -- <a href="http://gcc.gnu.org/">GCC</a> - GNU Compilers Collection (gcc, g++ -and g77 or gfortran), version 3.3.x or later (check version with <tt>`gcc ---version'</tt>) +- GNU Autotools: + - <a href="http://www.gnu.org/software/autoconf/">autoconf</a>, + - <a href="http://www.gnu.org/software/automake/">automake</a>, + - <a href="http://www.gnu.org/software/libtool/">libtool</a>, + - <a href="http://www.gnu.org/software/make/">make</a>, version 3.72.1 + or later (check version with \c `make --version') +- <a href="http://gcc.gnu.org/">GCC</a> - GNU C++ Compiler (g++), version 4.3.x + or later (check version with \c `gcc --version') +- <a href="http://www.boost.org/">Boost</a> - C++ STL extensions, version 1.35 + or later (check version with + \c `grep "define BOOST_LIB_VERSION" /usr/include/boost/version.hpp') +- <a href="http://dev.mysql.com/">MySQL</a> - Database client libraries, + version 5.0 or later (check version with \c `mysql --version') +- <a href="http://soci.sourceforge.net/">SOCI</a> - C++ database client + library wrapper, version 3.0.0 or later (check version with + \c `soci-config --version') . -To perform tests, two command line programs: \c sed and \c diff are -required. Optionally, you might need a few additional programs, i.e. +Optionally, you might need a few additional programs: <a href="http://www.doxygen.org/">Doxygen</a>, <a href="http://www.latex-project.org/">LaTeX</a>, <a href="http://www.radicaleye.com/dvips.html">Dvips</a> and <a href="http://www.cs.wisc.edu/~ghost/">Ghostscript</a>, to generate the -HTML documentation. +HTML and PDF documentation. We strongly recommend that you use recent stable releases of the GCC, if possible. We do not actively work on supporting older versions of the GCC, and they may therefore (without prior notice) become unsupported in future -releases of IT++. +releases of StdAir. -In order to use all functionality provided by the IT++ library, it is -recommended that you have some external libraries compiled and installed in -your computer. The basic set of them is: -<a href="http://www.netlib.org/blas/">BLAS</a>, -<a href="http://www.netlib.org/lapack/">LAPACK</a> and -<a href="http://www.fftw.org/">FFTW</a> (version 3.0.0 or later). To improve -some vector based operations a C interface of BLAS, namely -<a href="http://www.netlib.org/blas/">CBLAS</a>, is also recommended. -Instead of NetLib's reference BLAS, CBLAS and LAPACK implementations, some -optimized platform-specific libraries can be used as well, i.e.: -- <a href="http://math-atlas.sourceforge.net/">ATLAS</a> (<em>Automatically - Tuned Linear Algebra Software</em>) - includes optimised BLAS, CBLAS and a - limited set of LAPACK routines (version 3.6.0 or later) -- <a href="http://www.intel.com/cd/software/products/asmo-na/eng/perflib/mkl/">MKL</a> - (<em>Intel Math Kernel Library</em>) - includes all required BLAS, CBLAS, - LAPACK and FFT routines (version 8.0.0 or later; FFTW not required) -- <a href="http://developer.amd.com/acml.aspx">ACML</a> (<em>AMD Core Math - Library</em>) - includes BLAS, CBLAS, LAPACK and FFT routines (version - 2.5.3 or later; FFTW not required) +\section basic_instructions Basic Installation -It is possible to compile and use IT++ without these libraries, but the -functionality will be reduced. We therefore recommend that you take some -time and effort to provide these external libraries in your system. Please -note, that some of them (FFTW, BLAS and LAPACK) are usually included in -most modern Linux distributions. + Briefly, the shell commands \c `./configure; make; make install' +should configure, build, and install this package. The following +more-detailed instructions are generic; see the \c `README' file for +instructions specific to this package. Some packages provide this +\c `INSTALL' file but do not implement all of the features documented +below. The lack of an optional feature in a given package is not +necessarily a bug. More recommendations for GNU packages can be found +in the info page corresponding to "Makefile Conventions: +(standards)Makefile Conventions". + The \c `configure' shell script attempts to guess correct values for +various system-dependent variables used during compilation. It uses +those values to create a \c `Makefile' in each directory of the package. +It may also create one or more \c `.h' files containing system-dependent +definitions. Finally, it creates a shell script \c `config.status' that +you can run in the future to recreate the current configuration, and a +file \c `config.log' containing compiler output (useful mainly for +debugging \c `configure'). -\section download Obtaining the IT++ Source Codes + It can also use an optional file (typically called \c `config.cache' +and enabled with \c `--cache-file=config.cache' or simply \c `-C') that +saves the results of its tests to speed up reconfiguring. Caching is +disabled by default to prevent problems with accidental use of stale +cache files. -IT++ is released under the GNU General Public License (GPL) and hence the -source code of the IT++ library is available for free download. To obtain -the IT++ source code, visit the project pages on SourceForge: -- <a href="http://itpp.sourceforge.net/">http://itpp.sourceforge.net/</a> -. -and download the file named \c itpp-\<VERSION\>.tar.gz or -\c itpp-\<VERSION\>.tar.bz2, where \c \<VERSION\> is the latest release -number, e.g. 3.9.0. + If you need to do unusual things to compile the package, please try +to figure out how `configure' could check whether to do them, and mail +diffs or instructions to the address given in the \c `README' so they can +be considered for the next release. If you are using the cache, and at +some point \c `config.cache' contains results you don't want to keep, you +may remove or edit it. + The file \c `configure.ac' (or \c `configure.in') is used to create +\c `configure' by a program called \c `autoconf'. You need \c `configure.ac' +if you want to change it or regenerate \c `configure' using a newer version +of \c `autoconf'. -\section compilation General IT++ Configuration, Compilation and Installation Instructions +The simplest way to compile this package is: +-# \c `cd' to the directory containing the package's source code and type + \c `./configure' to configure the package for your system. + Running \c `configure' might take a while. While running, it prints + some messages telling which features it is checking for. +-# Type \c `make' to compile the package. +-# Optionally, type \c `make check' to run any self-tests that come with + the package, generally using the just-built uninstalled binaries. +-# Type \c `make install' to install the programs and any data files and + documentation. When installing into a prefix owned by root, it is + recommended that the package be configured and built as a regular + user, and only the `make install' phase executed with root + privileges. +-# Optionally, type \c `make installcheck' to repeat any self-tests, but + this time using the binaries in their final installed location. + This target does not install anything. Running this target as a + regular user, particularly if the prior \c `make install' required + root privileges, verifies that the installation completed + correctly. +-# You can remove the program binaries and object files from the + source code directory by typing \c `make clean'. To also remove the + files that \c `configure' created (so you can compile the package for + a different kind of computer), type \c `make distclean'. There is + also a \c `make maintainer-clean' target, but that is intended mainly + for the package's developers. If you use it, you may have to get + all sorts of other programs in order to regenerate files that came + with the distribution. +-# Often, you can also type \c `make uninstall' to remove the installed + files again. In practice, not all packages have tested that + uninstallation works correctly, even though it is required by the + GNU Coding Standards. +-# Some packages, particularly those that use Automake, provide \c `make + distcheck', which can by used by developers to test that all other + targets like \c `make install' and \c `make uninstall' work correctly. + This target is generally not run by end users. -Assuming that you have already downloaded the latest IT++ sources, untar -and unpack the sources, and enter the unpacked directory. Depending on the -package type you have downloaded, use the following commands: -\verbatim -% gzip -cd itpp-<VERSION>.tar.gz | tar xf - -% cd itpp-<VERSION> -\endverbatim +\section compilers Compilers and Options -\verbatim -% bzip2 -cd itpp-<VERSION>.tar.bz2 | tar xf - -% cd itpp-<VERSION> -\endverbatim + Some systems require unusual options for compilation or linking that +the \c `configure' script does not know about. Run \c `./configure --help' +for details on some of the pertinent environment variables. -Since version 3.9.0, the IT++ library uses autoconf, automake and libtool -for preparing Makefiles and configuration script, so the compilation -procedure resembles a standard, well-known GNU method, i.e. + You can give \c `configure' initial values for configuration parameters +by setting variables in the command line or in the environment. Here +is an example: -\verbatim -% ./configure -% make +\verbatim +./configure CC=c99 CFLAGS=-g LIBS=-lposix \endverbatim -The \c `configure' command can be invoked with additional switches and -options (run <tt>`./configure --help'</tt> to get a list of them). The -most important are: -- \c `--prefix=PREFIX' - set top installation directory to a certain \c - PREFIX value. By default it is set to \c `/usr/local', so <tt>`make - install'</tt> will install appropriate files into \c `/usr/local/include', - \c `/usr/local/lib`, etc. -- \c `--enable-debug' - build an extra library named \c `libitpp_debug.*' - using special debugging flags for compiler and linker (disabled by default) -- \c `--enable-exceptions' - enable exceptions handling of run-time errors - instead of aborting the program (disabled by default) -- \c `--disable-html-doc' - do not generate and install the HTML - documentation (enabled by default) -- \c `--disable-shared' - do not build the shared version of the library - (enabled by default for non Windows based platforms) -- \c `--disable-static' - do not build the static version of the library - (enabled by default for Windows based platforms) -. -Plese note that each \c `--enable-\<OPTION\>' switch can be replaced -with its opposite switch \c `--disable-\<OPTION\>'. + *Note \ref defining_variables for more details. -Since version 3.99.0, a modularization of the library has been introduced. -Therefore, several additional switches have been added to the configure -script, which can be used to disable building some of the library -components. Here is a list of them: -- \c `--disable-comm' - do not build the `Communications' module -- \c `--disable-fixed' - do not build the `Fixed-point' module -- \c `--disable-optim' - do not build the `Numerical optimisations' module -- \c `--disable-protocol' - do not include the `Protocols' module -- \c `--disable-signal' - do not build the `Signal processing' module -- \c `--disable-srccode' - do not build the `Source coding' module -By default, the \c `configure' script checks for a few external libraries, -which might be used by the IT++ library (cf. \ref requirements). BLAS and -LAPACK libraries require a fortran compiler for linking. Therefore, if no -fortran compiler can be found, only some FFT library is searched. -Otherwise, the detection procedure is as follows: --# First, the presence of a BLAS library among the MKL, ACML, ATLAS and - NetLib's reference BLAS is checked. If one of the above mentioned can be - used, \c HAVE_BLAS is defined. --# If the BLAS library can be found, the C interface of BLAS, namely CBLAS, - is detected. The CBLAS is provided by default by the MKL, ATLAS and - NetLib's reference CBLAS libraries. The ACML has also a C interface of - BLAS, which can be used, but it is not compatible with the standard - CBLAS. On success, \c HAVE_CBLAS is defined. --# Next, some LAPACK library is searched, but only if a BLAS library - is available. Full set of LAPACK routines can be found in the MKL, ACML - and NetLib's reference LAPACK libraries. Besides, the ATLAS contains a - subset of optimised LAPACK routines, which can be used with NetLib's LAPACK - library (this is described in the ATLAS documentation). If a LAPACK - library can be found, \c HAVE_LAPACK is defined. --# Finally, a set of separate checks for some FFT library is executed. - Currently three different libraries providing FFT/IFFT routines can be - used: MKL, ACML and FFTW. If at least one of them is found, \c HAVE_FFT - id defined. Besides, one of the following: \c HAVE_FFT_MKL8, \c - HAVE_FFT_ACML or \c HAVE_FFTW3 is defined. +\section compiling_for_multi_arch Compiling For Multiple Architectures -If some external libraries are installed in a non-standard location in your -system, e.g. MKL in <tt>`/opt/intel/mkl/8.0.1'</tt>, the \c `configure' script -will not detect them automatically. In such a case, you should use LDFLAGS -and CPPFLAGS environment variables to define additional directories to be -searched for libraries (LDFLAGS) and include files (CPPFLAGS). For instance, -to configure IT++ to link to the MKL 8.0.1 external library, which is -installed in <tt>`/opt/intel/mkl/8.0.1'</tt> directory, you should use the -following commands: + You can compile the package for more than one kind of computer at the +same time, by placing the object files for each architecture in their +own directory. To do this, you can use GNU `make'. `cd' to the +directory where you want the object files and executables to go and run +the `configure' script. `configure' automatically checks for the +source code in the directory that `configure' is in and in `..'. This +is known as a "VPATH" build. -\verbatim -% export LDFLAGS="-L/opt/intel/mkl/8.0.1/lib/32" -% export CPPFLAGS="-I/opt/intel/mkl/8.0.1/include" -% ./configure -\endverbatim + With a non-GNU `make', it is safer to compile the package for one +architecture at a time in the source code directory. After you have +installed the package for one architecture, use `make distclean' before +reconfiguring for another architecture. -In the case that external libraries have non-standard names, e.g. -<tt>`libcblas-3.a'</tt> for CBLAS, you might specify them to the configure -using \c `--with-\<LIBNAME\>' switches, where \c \<LIBNAME\> is one of the -following: \c `blas', \c `cblas', \c `lapack' or \c `fft'. You might use -more then one library names by quoting them with doublequotes, e.g. + On MacOS X 10.5 and later systems, you can create libraries and +executables that work on multiple system types--known as "fat" or +"universal" binaries--by specifying multiple `-arch' options to the +compiler but only a single `-arch' option to the preprocessor. Like +this: \verbatim -% ./configure --with-blas="-latlas -lblas" +./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ + CPP="gcc -E" CXXCPP="g++ -E" \endverbatim -If there is only one library specified, you can use a simplified notation -without the preceding `-l', e.g. \c `--with-fft=fftw3' instead of \c -`--with-fftw=-lfftw3'. + This is not guaranteed to produce working output in all cases, you +may have to build one architecture at a time and combine the results +using the `lipo' tool if you have problems. -Although it is not recommended, you can intentionally prevent detection of -some external libraries. To do this you should use \c -`--without-\<LIBNAME\>' or \c `--with-\<LIBNAME\>=no', e.g.: -\verbatim -% ./configure --without-cblas --without-lapack -\endverbatim +\section installation_names Installation Names -It is recommended to set CXXFLAGS environment variable with some -compiler- and platform-specific optimisation flags before invoking the -\c `configure' command. For example, in the case of using the Intel Pentium -4 processor one might employ the following flags: + By default, \c `make install' installs the package's commands under +\c `/usr/local/bin', include files under \c `/usr/local/include', etc. You +can specify an installation prefix other than \c `/usr/local' by giving +\c `configure' the option \c `--prefix=PREFIX', where \c PREFIX must be an +absolute file name. -\verbatim -% CXXFLAGS="-O3 -pipe -march=pentium4" ./configure -\endverbatim + You can specify separate installation prefixes for +architecture-specific files and architecture-independent files. If you +pass the option \c `--exec-prefix=PREFIX' to `configure', the package uses +\c PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. -In the case of Sun's UltraSPARC 64-bit platform and GCC compiler, the flags -might be set as follows: + In addition, if you use an unusual directory layout you can give +options like \c `--bindir=DIR' to specify different values for particular +kinds of files. Run `configure --help' for a list of the directories +you can set and what kinds of files go in them. In general, the +default for these options is expressed in terms of \c `${prefix}', so that +specifying just \c `--prefix' will affect all of the other directory +specifications that were not explicitly provided. -\verbatim -% export CXXFLAGS="-O3 -pipe -mcpu=v9 -m64" -% ./confiugre -\endverbatim + The most portable way to affect installation locations is to pass the +correct locations to \c `configure'; however, many packages provide one or +both of the following shortcuts of passing variable assignments to the +\c `make install' command line to change installation locations without +having to reconfigure or recompile. -If CXXFLAGS is not set in the environment, it will be initialised with -the default flags, i.e. <tt>"-DASSERT_LEVEL=1 -O3 -pipe"</tt>. + The first method involves providing an override variable for each +affected directory. For example, +\c `make install prefix=/alternate/directory' will choose an alternate location +for all directory configuration variables that were expressed in terms of +\c `${prefix}'. Any directories that were specified during \c `configure', +but not in terms of \c `${prefix}', must each be overridden at install +time for the entire installation to be relocated. The approach of +makefile variable overrides for each directory variable is required by +the GNU Coding Standards, and ideally causes no recompilation. +However, some platforms have known limitations with the semantics of +shared libraries that end up requiring recompilation when using this +method, particularly noticeable in packages that use GNU Libtool. -When the configuration process is finished, a status message is displayed. -For instance, after having invoked the following configuration -command on a recent Gentoo Linux system: + The second method involves providing the \c `DESTDIR' variable. For +example, \c `make install DESTDIR=/alternate/directory' will prepend +\c `/alternate/directory' before all installation names. The approach of +\c `DESTDIR' overrides is not required by the GNU Coding Standards, and +does not work on platforms that have drive letters. On the other hand, +it does better at avoiding recompilation issues, and works well even +when some directory options were not specified in terms of \c `${prefix}' +at \c `configure' time. -\verbatim -% ./configure --with-blas="-lblas" -\endverbatim -one can observe something like this: +\section optional_features Optional Features -\verbatim ------------------------------------------------------------------------------- -itpp-3.99.0 library configuration: ------------------------------------------------------------------------------- + If the package supports it, you can cause programs to be installed +with an extra prefix or suffix on their names by giving \c `configure' the +option \c `--program-prefix=PREFIX' or \c `--program-suffix=SUFFIX'. -Directories: - - prefix ......... : /usr/local - - exec_prefix .... : ${prefix} - - includedir ..... : ${prefix}/include - - libdir ......... : ${exec_prefix}/lib - - docdir ......... : ${prefix}/share/doc/itpp-3.99.0 + Some packages pay attention to \c `--enable-FEATURE' options to +\c `configure', where \c FEATURE indicates an optional part of the package. +They may also pay attention to \c `--with-PACKAGE' options, where \c PACKAGE +is something like \c `gnu-as' or \c `x' (for the X Window System). The +\c `README' should mention any \c `--enable-' and \c `--with-' options that +the package recognizes. -Switches: - - debug .......... : no - - exceptions ..... : no - - html-doc ....... : yes - - shared ......... : yes - - static ......... : no + For packages that use the X Window System, \c `configure' can usually +find the X include and library files automatically, but if it doesn't, +you can use the \c `configure' options \c `--x-includes=DIR' and +\c `--x-libraries=DIR' to specify their locations. -Documentation tools: - - doxygen ........ : yes - - latex .......... : yes - - dvips .......... : yes - - ghostscript .... : yes + Some packages offer the ability to configure how verbose the +execution of `make' will be. For these packages, running \c `./configure +--enable-silent-rules' sets the default to minimal output, which can be +overridden with \c `make V=1'; while running \c `./configure +--disable-silent-rules' sets the default to verbose, which can be +overridden with \c `make V=0'. -Testing tools: - - diff ........... : yes - - sed ............ : yes -Optional modules: - - comm ........... : yes - - fixed .......... : yes - - optim .......... : yes - - protocol ....... : yes - - signal ......... : yes - - srccode ........ : yes +\section particular_systems Particular systems -External libs: - - BLAS ........... : yes - * MKL .......... : no - * ACML ......... : no - * ATLAS ........ : yes - - CBLAS .......... : yes - - LAPACK ......... : yes - - FFT ............ : yes - * MKL .......... : no - * ACML ......... : no - * FFTW ......... : yes + On HP-UX, the default C compiler is not ANSI C compatible. If GNU +CC is not installed, it is recommended to use the following options in +order to use an ANSI C compiler: -Compiler/linker flags/libs/defs: - - CXX ............ : g++ - - F77 ............ : gfortran - - CXXFLAGS ....... : -DASSERT_LEVEL=1 -O3 -fno-exceptions -pipe - - CXXFLAGS_DEBUG . : - - CPPFLAGS ....... : - - LDFLAGS ........ : - - LIBS ........... : -lfftw3 -llapack -lcblas -lblas -lgfortran +\verbatim +./configure CC="cc -Ae -D_XOPEN_SOURCE=500" +\endverbatim ------------------------------------------------------------------------------- -Now type 'make && make install' to build and install itpp-3.99.0 library ------------------------------------------------------------------------------- +and if that doesn't work, install pre-built binaries of GCC for HP-UX. + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot +parse its \c `<wchar.h>' header file. The option \c `-nodtk' can be used as +a workaround. If GNU CC is not installed, it is therefore recommended +to try + +\verbatim +./configure CC="cc" \endverbatim -Now, it is time for compiling and linking the IT++ library. To do so, -please simply run the following command: +and if that doesn't work, try \verbatim -% make +./configure CC="cc -nodtk" \endverbatim -IT++ should compile without any errors or warnings. If this is not the -case, please submit a bug-report on the IT++ project page at SourceForge. -Please include information about your OS, compiler version, external -libraries and their versions, etc. + On Solaris, don't put \c `/usr/ucb' early in your \c `PATH'. This +directory contains several dysfunctional programs; working variants of +these programs are available in \c `/usr/bin'. So, if you need \c `/usr/ucb' +in your \c `PATH', put it _after_ \c `/usr/bin'. -It is recommended that you check if your library has been compiled and -linked properly and works as expected. To do so, you should execute the -testing process: + On Haiku, software installed for all users goes in \c `/boot/common', +not \c `/usr/local'. It is recommended to use the following options: \verbatim -% make check +./configure --prefix=/boot/common \endverbatim -As a result, you should obtain a similar report: -\verbatim ------------------------------------------------------------------------------- -Test `array_test' PASSED. ------------------------------------------------------------------------------- -Test `bessel_test' PASSED. ------------------------------------------------------------------------------- +\section specifying_system_type Specifying the System Type -[...] + There may be some features \c `configure' cannot figure out +automatically, but needs to determine by the type of machine the package +will run on. Usually, assuming the package is built to be run on the +_same_ architectures, `configure' can figure that out, but if it prints +a message saying it cannot guess the machine type, give it the +\c `--build=TYPE' option. \c TYPE can either be a short name for the +system type, such as \c `sun4', or a canonical name which has the form +\c CPU-COMPANY-SYSTEM ------------------------------------------------------------------------------- -Test `window_test' PASSED. ------------------------------------------------------------------------------- -Test `histogram_test' PASSED. ------------------------------------------------------------------------------- -Test `stat_test' PASSED. ------------------------------------------------------------------------------- -\endverbatim +where \c SYSTEM can have one of these forms: +- \c OS +- \c KERNEL-OS -Check if all the executed tests PASSED. If not, please contact us by filling -a bug-report. + See the file `config.sub' for the possible values of each field. If +\c `config.sub' isn't included in this package, then this package doesn't +need to know the machine type. -Finally, you should install the compiled and linked library, include files -and (optionally) HTML documentation by typing: + If you are _building_ compiler tools for cross-compiling, you should +use the opt... [truncated message content] |
From: <den...@us...> - 2010-07-25 16:06:55
|
Revision: 231 http://stdair.svn.sourceforge.net/stdair/?rev=231&view=rev Author: denis_arnaud Date: 2010-07-25 16:06:47 +0000 (Sun, 25 Jul 2010) Log Message: ----------- [Doc] HTML documentation is no longer generated (as it is, nevertheless, specific to each project). Modified Paths: -------------- trunk/stdair/configure.ac trunk/stdair/doc/local/Makefile.am trunk/stdair/doc/local/sources.mk Added Paths: ----------- trunk/stdair/doc/local/index.doc trunk/stdair/doc/sourceforge/howto_release_stdair.html Removed Paths: ------------- trunk/stdair/doc/local/index.doc.in trunk/stdair/doc/sourceforge/howto_release_stdair.html.in Property Changed: ---------------- trunk/stdair/doc/local/ trunk/stdair/doc/sourceforge/ Modified: trunk/stdair/configure.ac =================================================================== --- trunk/stdair/configure.ac 2010-07-24 17:09:19 UTC (rev 230) +++ trunk/stdair/configure.ac 2010-07-25 16:06:47 UTC (rev 231) @@ -222,15 +222,13 @@ stdair/service/Makefile stdair/core/Makefile stdair/batches/Makefile - man/Makefile + man/Makefile doc/Makefile doc/images/Makefile doc/tutorial/Makefile doc/tutorial/src/Makefile doc/local/Makefile - doc/local/index.doc doc/doxygen_html.cfg - doc/sourceforge/howto_release_stdair.html extracppunit/Makefile test/Makefile test/samples/Makefile Property changes on: trunk/stdair/doc/local ___________________________________________________________________ Modified: svn:ignore - Makefile Makefile.in index.doc + Makefile Makefile.in Modified: trunk/stdair/doc/local/Makefile.am =================================================================== --- trunk/stdair/doc/local/Makefile.am 2010-07-24 17:09:19 UTC (rev 230) +++ trunk/stdair/doc/local/Makefile.am 2010-07-25 16:06:47 UTC (rev 231) @@ -1,3 +1,4 @@ +# stdair/doc/local sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk Added: trunk/stdair/doc/local/index.doc =================================================================== --- trunk/stdair/doc/local/index.doc (rev 0) +++ trunk/stdair/doc/local/index.doc 2010-07-25 16:06:47 UTC (rev 231) @@ -0,0 +1,87 @@ +/*! +\mainpage StdAir Documentation + +\htmlonly +<!-- start of main block --> +<div style="width: 100%;"> +<!-- start of left margin --> +<div style="float:right; width:200px; background-color: #eeeeff; + border: 1px solid #b0b0b0; margin: 0 0 10px 20px; padding: 10px; + font-size: 90%;"> + +<b>Getting Started:</b> +<ul> +<li><a href="features.html">Features</a></li> +<li><a href="installation.html">Installation</a></li> +<li><a href="linking.html">Linking with StdAir</a></li> +<li><a href="users_guide.html">Short Introduction to StdAir</a></li> +<li><a href="tutorial.html">Some Tutorial Examples</a></li> +<li><a href="verification.html">StdAir Verification</a></li> +<li><a href="copyright.html">Copyright and License</a></li> +<li><a href="help_wanted.html">Make a Difference</a></li> +<li><a href="authors.html">Authors</a></li> +</ul> + +<a href="http://sourceforge.net/projects/stdair/"><b>StdAir at SourceForge:</b></a> +<ul> +<li><a href="http://sourceforge.net/project/showfiles.php?group_id=267760">Download StdAir</a></li> +<li><a href="http://stdair.sourceforge.net/RPM-GPG-KEY-freshrpms-free">RPM-GPG-Key</a> for StdAir RPMs (save the file, and type 'rpm --import RPM-GPG-KEY-freshrpms-free' as root)</li> +<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882290">Bug Reports</a></li> +<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882293">Feature Requests</a></li> +<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882292">Submit Patches</a></li> +<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882291">Support Request</a></li> +<li><a href="http://sourceforge.net/mail/?group_id=267760">Mailing lists</a></li> +<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613897">Discuss about Development issues</a></li> +<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613896">Ask for Help</a></li> +<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613895">Discuss StdAir</a></li> +</ul> + +<b>StdAir Development:</b> +<ul> +<li><a href="http://stdair.svn.sourceforge.net/viewvc/stdair/">SVN Repository</a></li> +<li><a href="codingrules.html">Coding Rules</a></li> +<li><a href="documentation.html">Documentation Rules</a></li> +<li><a href="test.html">Test Rules</a></li> +</ul> + +<b>External Libraries:</b> +<ul> +<li><a href="http://www.gnu.org/software/gsl">GSL</a></li> +</ul> + +</div> +<!-- end of left margin --> +\endhtmlonly + +\section about About StdAir + +StdAir is a C++ library of classes and functions modeling typical +airline IT business objects. For instance, it is used by the Airline +Schedule C++ library project (http://www.sourceforge.net/projects/air-sched). + +StdAir makes an extensive use of existing open-source libraries for +increased functionality, speed and accuracy. In particular <a +href="http://www.boost.org">Boost</a> (<em>C++ STL Extensions</em>) library is +used. + +The StdAir library originates from the department of Operational +Research and Innovation at <a +href="http://www.amadeus.com">Amadeus</a>, Sophia Antipolis, +France. StdAir is released under the terms of the <a +href="http://www.gnu.org/licenses/lgpl.html">GNU Lesser General Public +License</a> (LGPL) for you to enjoy. + +StdAir should work on +<a href="http://en.wikipedia.org/wiki/GNU/Linux">GNU/Linux</a>, +<a href="http://www.sun.com/software/solaris/">Sun Solaris</a>, +Microsoft Windows (with <a href="http://www.cygwin.com/">Cygwin</a>, +<a href="http://www.mingw.org/">MinGW/MSYS</a>, or +<a href="http://msdn.microsoft.com/visualc/">Microsoft Visual C++ .NET</a>) and +<a href="http://www.apple.com/macosx/">Mac OS X</a> operating systems. + +\htmlonly +</div> +<!-- end of main block --> +\endhtmlonly + +*/ Deleted: trunk/stdair/doc/local/index.doc.in =================================================================== --- trunk/stdair/doc/local/index.doc.in 2010-07-24 17:09:19 UTC (rev 230) +++ trunk/stdair/doc/local/index.doc.in 2010-07-25 16:06:47 UTC (rev 231) @@ -1,85 +0,0 @@ -/*! -\mainpage StdAir Documentation - -\htmlonly -<!-- start of main block --> -<div style="width: 100%;"> -<!-- start of left margin --> -<div style="float:right; width:200px; background-color: #eeeeff; border: 1px solid #b0b0b0; margin: 0 0 10px 20px; padding: 10px; font-size: 90%;"> - -<b>Getting Started:</b> -<ul> -<li><a href="features.html">Features</a></li> -<li><a href="installation.html">Installation</a></li> -<li><a href="linking.html">Linking with StdAir</a></li> -<li><a href="users_guide.html">Short Introduction to StdAir</a></li> -<li><a href="tutorial.html">Some Tutorial Examples</a></li> -<li><a href="verification.html">StdAir Verification</a></li> -<li><a href="copyright.html">Copyright and License</a></li> -<li><a href="help_wanted.html">Make a Difference</a></li> -<li><a href="authors.html">Authors</a></li> -</ul> - -<a href="http://sourceforge.net/projects/stdair/"><b>StdAir at SourceForge:</b></a> -<ul> -<li><a href="http://sourceforge.net/project/showfiles.php?group_id=267760">Download StdAir</a></li> -<li><a href="http://stdair.sourceforge.net/RPM-GPG-KEY-freshrpms-free">RPM-GPG-Key</a> for StdAir RPMs (save the file, and type 'rpm --import RPM-GPG-KEY-freshrpms-free' as root)</li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882290">Bug Reports</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882293">Feature Requests</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882292">Submit Patches</a></li> -<li><a href="http://sourceforge.net/tracker/?group_id=267760&atid=882291">Support Request</a></li> -<li><a href="http://sourceforge.net/mail/?group_id=267760">Mailing lists</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613897">Discuss about Development issues</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613896">Ask for Help</a></li> -<li><a href="http://sourceforge.net/forum/forum.php?forum_id=613895">Discuss StdAir</a></li> -</ul> - -<b>StdAir Development:</b> -<ul> -<li><a href="http://stdair.svn.sourceforge.net/viewvc/stdair/">SVN Repository</a></li> -<li><a href="codingrules.html">Coding Rules</a></li> -<li><a href="documentation.html">Documentation Rules</a></li> -<li><a href="test.html">Test Rules</a></li> -</ul> - -<b>External Libraries:</b> -<ul> -<li><a href="http://www.gnu.org/software/gsl">GSL</a></li> -</ul> - -</div> -<!-- end of left margin --> -\endhtmlonly - -\section about About StdAir - -StdAir is a C++ library of classes and functions modeling typical -airline IT business objects. For instance, it is used by the Airline -Schedule C++ library project (http://www.sourceforge.net/projects/air-sched). - -StdAir makes an extensive use of existing open-source libraries for -increased functionality, speed and accuracy. In particular <a -href="http://www.boost.org">Boost</a> (<em>C++ STL Extensions</em>) library is -used. - -The StdAir library originates from the department of Operational -Research and Innovation at <a -href="http://www.amadeus.com">Amadeus</a>, Sophia Antipolis, -France. StdAir is released under the terms of the <a -href="http://www.gnu.org/licenses/lgpl.html">GNU Lesser General Public -License</a> (LGPL) for you to enjoy. - -StdAir should work on -<a href="http://en.wikipedia.org/wiki/GNU/Linux">GNU/Linux</a>, -<a href="http://www.sun.com/software/solaris/">Sun Solaris</a>, -Microsoft Windows (with <a href="http://www.cygwin.com/">Cygwin</a>, -<a href="http://www.mingw.org/">MinGW/MSYS</a>, or -<a href="http://msdn.microsoft.com/visualc/">Microsoft Visual C++ .NET</a>) and -<a href="http://www.apple.com/macosx/">Mac OS X</a> operating systems. - -\htmlonly -</div> -<!-- end of main block --> -\endhtmlonly - -*/ Modified: trunk/stdair/doc/local/sources.mk =================================================================== --- trunk/stdair/doc/local/sources.mk 2010-07-24 17:09:19 UTC (rev 230) +++ trunk/stdair/doc/local/sources.mk 2010-07-25 16:06:47 UTC (rev 231) @@ -1,4 +1,5 @@ doc_local_sources = \ + $(top_srcdir)/doc/local/index.doc \ $(top_srcdir)/doc/local/authors.doc \ $(top_srcdir)/doc/local/codingrules.doc \ $(top_srcdir)/doc/local/copyright.doc \ Property changes on: trunk/stdair/doc/sourceforge ___________________________________________________________________ Modified: svn:ignore - howto_release_stdair.html + Added: trunk/stdair/doc/sourceforge/howto_release_stdair.html =================================================================== --- trunk/stdair/doc/sourceforge/howto_release_stdair.html (rev 0) +++ trunk/stdair/doc/sourceforge/howto_release_stdair.html 2010-07-25 16:06:47 UTC (rev 231) @@ -0,0 +1,180 @@ +<!-- +The following tags are permitted: a, b, blockquote, br, code, dd, div, +dl, dt, em, hr, i, li, ol, p, pre, strong, tt, ul, u. All other tags will be +stripped. All tags aside from the following must be closed: br, hr, li, p. +Failure to close tags may result in HTML output which is not rendered +properly. Any style attributes or on* attributes (such as mouseover) will be +stripped. JavaScript will result in the total stripping of HTML tags from +your input. Please limit your input to properly formed HTML snippets +conforming to the above rules. +--> + +<h2> How to release a new version of StdAir </h2> + + +<p> This document describes briefly the recommended procedure of releasing a + new version of StdAir using a Linux development machine and the SourceForge + project site. </p> + +<p> The following steps are required to make a release of the distribution + package: </p> + +<ul> + +<li> Initialisation: check out locally the full Subversion project:<br> + <code> + cd ~<br> + mkdir -p dev<br> + cd ~/dev<br> + svn co <a href="https://stdair.svn.sourceforge.net/svnroot/stdair">https://stdair.svn.sourceforge.net/svnroot/stdair</a> stdairsvn + </code> +</li> + +<li> Prepare the branch for its creation on the Subversion repository:<br> + <code> + cd ~/dev<br> + cd stdairsvn/branches/stdair<br> + mkdir 0.1.0<br> + svn add 0.1.0<br> + svn ci -m "[Branch 0.1.0] Prepared the branch 0.1.0 to be copied from head + of the trunk." + </code> +</li> + +<li> Check to which Subversion revision the release corresponds to. For instance + the <a href="http://sourceforge.net/apps/trac/stdair/changeset/220/">StdAir + release 0.1.0 corresponds to Subversion revision r218</a>. + The trunk <tt>configure.ac</tt> file specifies a fake release number, namely + 99.99.99, + for current (head) development. When a release is made, two Subversion + revisions are committed with, as the sole change, the release number within + the <tt>configure.ac</tt> file. One revision is committed with the + to-be-released version number (e.g., 0.1.0) and commit message prefixed with + "[Release x.y.z]", and another one with the release number back to + 99.99.99 and message stating "[Release] Back to working version (99.99.99)." + That way, it is then easy to spot the starting point of any release within + the Subversion repository, with something like:<br> + <code>cd ~/dev<br> + cd stdairsvn/trunk/stdair<br> + svn log configure.ac | less</code> +</li> + +<li> Create a release branch by copying the source tree to be released + into the dedicated + <a href="https://sourceforge.net/apps/trac/stdair/browser/branches/stdair">'branches' sub-directory of the Subversion repository</a>, e.g.:<br> + <code> + svn copy -<a href="http://sourceforge.net/apps/trac/stdair/changeset/218">r218</a> \<br> + <a href="https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair">https://stdair.svn.sourceforge.net/svnroot/stdair/trunk/stdair</a> \<br> + <a href="https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0/main">https://stdair.svn.sourceforge.net/svnroot/stdair/branches/stdair/0.1.0/main</a> \<br> + -m "[Release] Created the main 0.1.0 release branch, from revision + <a href="http://sourceforge.net/apps/trac/stdair/changeset/218">r218</a>."<br> + </code> + # Check the results:<br> + <code> + firefox -new-tab "<a href="http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main">http://sourceforge.net/apps/trac/stdair/browser/branches/stdair/0.1.0/main</a>" + </code> +</li> + +<li> Check-out the release StdAir sources from the branch, so that patches +may be made (for instance, on the RPM specification file):<br> + <code> + cd ~/dev<br> + cd stdairsvn/branches/stdair/0.1.0<br> + svn up<br> + cd main + </code> +</li> + +<li> <b>Only if needed</b>, alter a few files on the branch.<br> +<b>Note that the release branch is not the place where to develop for a +release.</b> +The <b>release</b> branch is aimed at keeping track of a release and of all +the patches having made their way into that branch, so that the software +can always be generated according to that release.<br> +Developments for a particular release should be made on the trunk (e.g., by +adding features not activated by default, but activated the release developers +only) or, if really needed, on a dedicated <b>development</b> branch. +</li> + +<li> Create the distribution packages using the following command:<br> + <code> + cd ~/dev<br> + cd stdairsvn/branches/stdair/0.1.0/main<br> + ./autogen.sh && make distcheck<br> + </code> + This will configure, compile and check the package. The output packages will + be named <tt>stdair-0.1.0.tar.gz</tt> and <tt>stdair-0.1.0.tar.bz2</tt>, for + instance. +</li> + +<li> Optionally, generate the RPM package (for instance, for Fedora/RedHat)<br> + <code> + cd ~/dev<br> + cd stdairsvn/branches/stdair/0.1.0/main<br> + ./autogen.sh && make dist<br> + </code> + # To perform this step, autoconf, automake and libtool tools have to be + available in the system.<br> + <code> + cp stdair.spec ~/dev/packages/SPECS \<br> + && cp stdair-0.1.0.tar.bz2 ~/dev/packages/SOURCES<br> + cd ~/dev/packages/SPECS<br> + rpmbuild -ba stdair.spec<br> + rpmlint -i ../SPECS/stdair.spec ../SRPMS/stdair-0.1.0-1.fc13.src.rpm \<br> + ../RPMS/i686/stdair-*<br> + </code> +</li> + +<li> Update the <tt>NEWS</tt> and <tt>ChangeLog</tt> files with appropriate + information, including what has changed since the previous release. Then + commit the changes into the + <a href="https://sourceforge.net/apps/trac/stdair/browser">StdAir's + Subversion (SVN) repository</a>. +</li> + +<li> Create the documentation packages using the following command:<br> + <code>make dist-html</code><br> + The output documentation packages will be + named <tt>stdair-doc-0.1.0.tar.gz</tt> + and <tt>stdair-doc-0.1.0.tar.bz2</tt>, for example. +</li> + +<li> Upload the distribution and documentation packages to the SourceForge + server. Check + <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download#SCP">SourceForge help page on uploading software</a>. +</li> + +<li> In order to update the Web site files, either: + <ul> + <li> <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service#Accessingyourfileswithothertools">synchronise + them with rsync and SSH</a>:<br> + <code> + cd ~/dev<br> + cd stdairsvn/branches/stdair/0.1.0/main<br> + rsync -aiv doc/html joe,st...@we...:htdocs/<br> + </code> + where <tt>-aiv</tt> options mean: + <ul> + <li> -a: archive/mirror mode; equals -rlptgoD (no -H,-A,-X)</li> + <li> -v: increase verbosity</li> + <li> -i: output a change-summary for all updates</li> + </ul> + </li> + <li> or use the + <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Shell%20service">SourceForge Shell service</a>. + </li> + </ul> +</li> + +<li> Do a new post on the + <a href="https://sourceforge.net/apps/wordpress/stdair/wp-admin/">SourceForge hosted WordPress blog</a> and update, if necessary, + <a href="https://sourceforge.net/apps/trac/stdair/report">Trac tickets</a>. +</li> + +<li> Finally, you should send an announcement to + <a href="mailto:std...@li...">std...@li...</a> + (see <a href="https://lists.sourceforge.net/lists/listinfo/stdair-announce">https://lists.sourceforge.net/lists/listinfo/stdair-announce</a> + for the archives)</p> +</li> +</ul> + Deleted: trunk/stdair/doc/sourceforge/howto_release_stdair.html.in =================================================================== --- trunk/stdair/doc/sourceforge/howto_release_stdair.html.in 2010-07-24 17:09:19 UTC (rev 230) +++ trunk/stdair/doc/sourceforge/howto_release_stdair.html.in 2010-07-25 16:06:47 UTC (rev 231) @@ -1,120 +0,0 @@ -<!-- -The following tags are permitted: a, b, blockquote, br, code, dd, div, -dl, dt, em, hr, i, li, ol, p, pre, strong, tt, ul, u. All other tags will be -stripped. All tags aside from the following must be closed: br, hr, li, p. -Failure to close tags may result in HTML output which is not rendered -properly. Any style attributes or on* attributes (such as mouseover) will be -stripped. JavaScript will result in the total stripping of HTML tags from -your input. Please limit your input to properly formed HTML snippets -conforming to the above rules. ---> - -<h2> How to release a new version of StdAir </h2> - - -<p> This document describes briefly the recommended procedure of releasing a -new version of StdAir using SourceForge project site. </p> - - -<p> The following steps are required to prepare and release of the -distribution package: </p> - -<ul> - -<li> Update <tt>NEWS</tt> and <tt>ChangeLog</tt> files with appropriate - information including what has changed since the previous release. Then - commit the changes into the SVN repository. </li> - -<li> Create a release tag by copying the source tree to be released to the - tags subdirectory in the SVN repository, e.g.:<br> -<code>% svn copy https://@PACKAGE@.svn.sourceforge.net/svnroot/@PACKAGE@/trunk https://@PACKAGE@.svn.sourceforge.net/svnroot/@PACKAGE@/tags/release-0-11-0</code> -</li> - -<li> Export a clean, unversioned copy of the StdAir sources using the release - tag:<br> -<code>% svn export https://@PACKAGE@.svn.sourceforge.net/svnroot/@PACKAGE@/tags/release-0-1-0 @PACKAGE@-@VERSION@</code> -</li> - -<li> Regenerate the <tt>configure</tt> script and other autogenerated files - using:<br> -<code>% ./autogen.sh</code><br> -To perform this step, autoconf, automake and libtool tools have to be -available in the system. </li> - -<li> Configure the exported sources:<br> -<code>% ./configure</code> </li> - -<li> Create the distribution packages using the following command:<br> -<code>% make distcheck</code><br> -This will configure, compile and check the package. The output packages will -be named <tt>@PACKAGE@-@VERSION@.tar.gz</tt> and <tt>@PACKAGE@-@VERSION@.tar.bz2</tt>, for -instance. </li> - -<li> Create the documentation packages using the following command:<br> -<code>% make dist-html</code><br> -The output documentation packages will be -named <tt>@PACKAGE@-html-doc-@VERSION@.tar.gz</tt> -and <tt>@PACKAGE@-html-doc-@VERSION@.tar.bz2</tt>, for example. </li> - -<li> Upload the distribution and documentation packages to the SourceForge - server: </li> - -<ul> - -<li> Start ftp connection with the SourceForge upload server:<br> -<code>% ftp upload.sourceforge.net</code> </li> - -<li> Login as <tt>anonymous</tt> and give email as password </li> - -<li> Change remote directory to <tt>/incoming</tt>:<br> -<code>% cd /incoming</code></li> - -<li> Upload packages:<br> -<code>% mput @PACKAGE@*-@VERSION@.tar.*</code> </li> - -</ul> - -<li> Access SourceForge file release interface and add the packages. - Remember to fill in the Release Notes and ChangeLog parts with appropriate - infmormation. </li> - -</ul> - - -<p> In order to update the online HTML documentation, the following -procedure is required: </p> - -<ul> - -<li> Upload the documentation package into the SourceForge shell server:<br> -<code>% scp @PACKAGE@-html-doc-@VERSION@.tar.gz you...@sh...:/home/groups/o/op/@PACKAGE@/htdocs/</code> -</li> - -<li> Login into the SourceForge shell account:<br> -<code>% ssh you...@sh...</code> </li> - -<li> Change the current directory:<br> -<code>% cd /home/groups/o/op/@PACKAGE@/htdocs</code> </li> - -<li> Unpack the uploaded documentation:<br> -<code>% tar zxf @PACKAGE@-html-doc-@VERSION@.tar.gz</code> </li> - -<li> Rename the unpacked directory to <tt>@VERSION@</tt>:<br> -<code>% mv @PACKAGE@-html-doc-@VERSION@ @VERSION@</code> </li> - -<li> Update the <tt>latest</tt> link:<br> -<code>% rm latest; ln -s @VERSION@ latest</code> </li> - -<li> Change the group properties of the uploaded files:<br> -<code>% chmod -R g+w @VERSION@</code> </li> - -<li> Remove the package from the shell server:<br> -<code>% rm @PACKAGE@-html-doc-@VERSION@.tar.gz</code> </li> - -</ul> - -<p> Finally, you should send an announcement to: -<a href="mailto:@PACKAGE@-an...@li..."> -@PACKAGE@-an...@li... </a> </p> - -</ul> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-24 17:09:26
|
Revision: 230 http://stdair.svn.sourceforge.net/stdair/?rev=230&view=rev Author: denis_arnaud Date: 2010-07-24 17:09:19 +0000 (Sat, 24 Jul 2010) Log Message: ----------- [Doc] Updated the licence for generated documentation. Modified Paths: -------------- trunk/stdair/doc/local/copyright.doc Modified: trunk/stdair/doc/local/copyright.doc =================================================================== --- trunk/stdair/doc/local/copyright.doc 2010-07-24 17:00:24 UTC (rev 229) +++ trunk/stdair/doc/local/copyright.doc 2010-07-24 17:09:19 UTC (rev 230) @@ -2,16 +2,20 @@ \page copyright Copyright and License -\section gnugpl GNU GENERAL PUBLIC LICENSE +\section gnugpl GNU LESSER GENERAL PUBLIC LICENSE -\subsection version Version 2, June 1991 +\subsection version Version 2.1, February 1999 \verbatim -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +Copyright (C) 1991, 1999 Free Software Foundation, Inc. +51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. + +[This is the first released version of the Lesser GPL. It also counts +as the successor of the GNU Library Public License, version 2, hence +the version number 2.1.] \endverbatim @@ -19,212 +23,383 @@ The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. +Licenses are intended to guarantee your freedom to share and change +free software--to make sure the software is free for all its users. - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. + This license, the Lesser General Public License, applies to some +specially designated software packages--typically libraries--of the +Free Software Foundation and other authors who decide to use it. You +can use it too, but we suggest you first think carefully about whether +this license or the ordinary General Public License is the better +strategy to use in any particular case, based on the explanations below. + When we speak of free software, we are referring to freedom of use, +not price. Our General Public Licenses are designed to make sure that +you have the freedom to distribute copies of free software (and charge +for this service if you wish); that you receive source code or can get +it if you want it; that you can change the software and use pieces of +it in new free programs; and that you are informed that you can do +these things. + To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. +distributors to deny you these rights or to ask you to surrender these +rights. These restrictions translate to certain responsibilities for +you if you distribute copies of the library or if you modify it. - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. + For example, if you distribute copies of the library, whether gratis +or for a fee, you must give the recipients all the rights that we gave +you. You must make sure that they, too, receive or can get the source +code. If you link other code with the library, you must provide +complete object files to the recipients, so that they can relink them +with the library after making changes to the library and recompiling +it. And you must show them these terms so they know their rights. - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. + We protect your rights with a two-step method: (1) we copyright the +library, and (2) we offer you this license, which gives you legal +permission to copy, distribute and/or modify the library. - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. + To protect each distributor, we want to make it very clear that +there is no warranty for the free library. Also, if the library is +modified by someone else and passed on, the recipients should know +that what they have is not the original version, so that the original +author's reputation will not be affected by problems that might be +introduced by others. - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. + Finally, software patents pose a constant threat to the existence of +any free program. We wish to make sure that a company cannot +effectively restrict the users of a free program by obtaining a +restrictive license from a patent holder. Therefore, we insist that +any patent license obtained for a version of the library must be +consistent with the full freedom of use specified in this license. + Most GNU software, including some libraries, is covered by the +ordinary GNU General Public License. This license, the GNU Lesser +General Public License, applies to certain designated libraries, and +is quite different from the ordinary General Public License. We use +this license for certain libraries in order to permit linking those +libraries into non-free programs. + + When a program is linked with a library, whether statically or using +a shared library, the combination of the two is legally speaking a +combined work, a derivative of the original library. The ordinary +General Public License therefore permits such linking only if the +entire combination fits its criteria of freedom. The Lesser General +Public License permits more lax criteria for linking other code with +the library. + + We call this license the "Lesser" General Public License because it +does Less to protect the user's freedom than the ordinary General +Public License. It also provides other free software developers Less +of an advantage over competing non-free programs. These disadvantages +are the reason we use the ordinary General Public License for many +libraries. However, the Lesser license provides advantages in certain +special circumstances. + + For example, on rare occasions, there may be a special need to +encourage the widest possible use of a certain library, so that it becomes +a de-facto standard. To achieve this, non-free programs must be +allowed to use the library. A more frequent case is that a free +library does the same job as widely used non-free libraries. In this +case, there is little to gain by limiting the free library to free +software only, so we use the Lesser General Public License. + + In other cases, permission to use a particular library in non-free +programs enables a greater number of people to use a large body of +free software. For example, permission to use the GNU C Library in +non-free programs enables many more people to use the whole GNU +operating system, as well as its variant, the GNU/Linux operating +system. + + Although the Lesser General Public License is Less protective of the +users' freedom, it does ensure that the user of a program that is +linked with the Library has the freedom and the wherewithal to run +that program using a modified version of the Library. + The precise terms and conditions for copying, distribution and -modification follow. +modification follow. Pay close attention to the difference between a +"work based on the library" and a "work that uses the library". The +former contains code derived from the library, whereas the latter must +be combined with the library in order to run. - \section terms TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". + 0. This License Agreement applies to any software library or other +program which contains a notice placed by the copyright holder or +other authorized party saying it may be distributed under the terms of +this Lesser General Public License (also called "this License"). +Each licensee is addressed as "you". -Activities other than copying, distribution and modification are not + A "library" means a collection of software functions and/or data +prepared so as to be conveniently linked with application programs +(which use some of those functions and data) to form executables. + + The "Library", below, refers to any such software library or work +which has been distributed under these terms. A "work based on the +Library" means either the Library or any derivative work under +copyright law: that is to say, a work containing the Library or a +portion of it, either verbatim or with modifications and/or translated +straightforwardly into another language. (Hereinafter, translation is +included without limitation in the term "modification".) + + "Source code" for a work means the preferred form of the work for +making modifications to it. For a library, complete source code means +all the source code for all modules it contains, plus any associated +interface definition files, plus the scripts used to control compilation +and installation of the library. + + Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. +running a program using the Library is not restricted, and output from +such a program is covered only if its contents constitute a work based +on the Library (independent of the use of the Library in a tool for +writing it). Whether that is true depends on what the Library does +and what the program that uses the Library does. + + 1. You may copy and distribute verbatim copies of the Library's +complete source code as you receive it, in any medium, provided that +you conspicuously and appropriately publish on each copy an +appropriate copyright notice and disclaimer of warranty; keep intact +all the notices that refer to this License and to the absence of any +warranty; and distribute a copy of this License along with the +Library. - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. + You may charge a fee for the physical act of transferring a copy, +and you may at your option offer warranty protection in exchange for a +fee. -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and + 2. You may modify your copy or copies of the Library or any portion +of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: - a) You must cause the modified files to carry prominent notices + a) The modified work must itself be a software library. + + b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. + c) You must cause the whole of the work to be licensed at no + charge to all third parties under the terms of this License. - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) + d) If a facility in the modified Library refers to a function or a + table of data to be supplied by an application program that uses + the facility, other than as an argument passed when the facility + is invoked, then you must make a good faith effort to ensure that, + in the event an application does not supply such function or + table, the facility still operates, and performs whatever part of + its purpose remains meaningful. + (For example, a function in a library to compute square roots has + a purpose that is entirely well-defined independent of the + application. Therefore, Subsection 2d requires that any + application-supplied function or table used by this function must + be optional: if the application does not supply it, the square + root function must still compute square roots.) + These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, +identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of +on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. +entire whole, and thus to each and every part regardless of who wrote +it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or -collective works based on the Program. +collective works based on the Library. -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of +In addition, mere aggregation of another work not based on the Library +with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: + 3. You may opt to apply the terms of the ordinary GNU General Public +License instead of this License to a given copy of the Library. To do +this, you must alter all the notices that refer to this License, so +that they refer to the ordinary GNU General Public License, version 2, +instead of to this License. (If a newer version than version 2 of the +ordinary GNU General Public License has appeared, then you can specify +that version instead if you wish.) Do not make any other change in +these notices. - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, + Once this change is made in a given copy, it is irreversible for +that copy, so the ordinary GNU General Public License applies to all +subsequent copies and derivative works made from that copy. - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, + This option is useful when you wish to copy part of the code of +the Library into a program that is not a library. - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) + 4. You may copy and distribute the Library (or a portion or +derivative of it, under Section 2) in object code or executable form +under the terms of Sections 1 and 2 above provided that you accompany +it with the complete corresponding machine-readable source code, which +must be distributed under the terms of Sections 1 and 2 above on a +medium customarily used for software interchange. -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not + If distribution of object code is made by offering access to copy +from a designated place, then offering equivalent access to copy the +source code from the same place satisfies the requirement to +distribute the source code, even though third parties are not compelled to copy the source along with the object code. - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. + 5. A program that contains no derivative of any portion of the +Library, but is designed to work with the Library by being compiled or +linked with it, is called a "work that uses the Library". Such a +work, in isolation, is not a derivative work of the Library, and +therefore falls outside the scope of this License. - 5. You are not required to accept this License, since you have not + However, linking a "work that uses the Library" with the Library +creates an executable that is a derivative of the Library (because it +contains portions of the Library), rather than a "work that uses the +library". The executable is therefore covered by this License. +Section 6 states terms for distribution of such executables. + + When a "work that uses the Library" uses material from a header file +that is part of the Library, the object code for the work may be a +derivative work of the Library even though the source code is not. +Whether this is true is especially significant if the work can be +linked without the Library, or if the work is itself a library. The +threshold for this to be true is not precisely defined by law. + + If such an object file uses only numerical parameters, data +structure layouts and accessors, and small macros and small inline +functions (ten lines or less in length), then the use of the object +file is unrestricted, regardless of whether it is legally a derivative +work. (Executables containing this object code plus portions of the +Library will still fall under Section 6.) + + Otherwise, if the work is a derivative of the Library, you may +distribute the object code for the work under the terms of Section 6. +Any executables containing that work also fall under Section 6, +whether or not they are linked directly with the Library itself. + + 6. As an exception to the Sections above, you may also combine or +link a "work that uses the Library" with the Library to produce a +work containing portions of the Library, and distribute that work +under terms of your choice, provided that the terms permit +modification of the work for the customer's own use and reverse +engineering for debugging such modifications. + + You must give prominent notice with each copy of the work that the +Library is used in it and that the Library and its use are covered by +this License. You must supply a copy of this License. If the work +during execution displays copyright notices, you must include the +copyright notice for the Library among them, as well as a reference +directing the user to the copy of this License. Also, you must do one +of these things: + + a) Accompany the work with the complete corresponding + machine-readable source code for the Library including whatever + changes were used in the work (which must be distributed under + Sections 1 and 2 above); and, if the work is an executable linked + with the Library, with the complete machine-readable "work that + uses the Library", as object code and/or source code, so that the + user can modify the Library and then relink to produce a modified + executable containing the modified Library. (It is understood + that the user who changes the contents of definitions files in the + Library will not necessarily be able to recompile the application + to use the modified definitions.) + + b) Use a suitable shared library mechanism for linking with the + Library. A suitable mechanism is one that (1) uses at run time a + copy of the library already present on the user's computer system, + rather than copying library functions into the executable, and (2) + will operate properly with a modified version of the library, if + the user installs one, as long as the modified version is + interface-compatible with the version that the work was made with. + + c) Accompany the work with a written offer, valid for at + least three years, to give the same user the materials + specified in Subsection 6a, above, for a charge no more + than the cost of performing this distribution. + + d) If distribution of the work is made by offering access to copy + from a designated place, offer equivalent access to copy the above + specified materials from the same place. + + e) Verify that the user has already received a copy of these + materials or that you have already sent this user a copy. + + For an executable, the required form of the "work that uses the +Library" must include any data and utility programs needed for +reproducing the executable from it. However, as a special exception, +the materials to be distributed need not include anything that is +normally distributed (in either source or binary form) with the major +components (compiler, kernel, and so on) of the operating system on +which the executable runs, unless that component itself accompanies +the executable. + + It may happen that this requirement contradicts the license +restrictions of other proprietary libraries that do not normally +accompany the operating system. Such a contradiction means you cannot +use both them and the Library together in an executable that you +distribute. + + 7. You may place library facilities that are a work based on the +Library side-by-side in a single library together with other library +facilities not covered by this License, and distribute such a combined +library, provided that the separate distribution of the work based on +the Library and of the other library facilities is otherwise +permitted, and provided that you do these two things: + + a) Accompany the combined library with a copy of the same work + based on the Library, uncombined with any other library + facilities. This must be distributed under the terms of the + Sections above. + + b) Give prominent notice with the combined library of the fact + that part of it is a work based on the Library, and explaining + where to find the accompanying uncombined form of the same work. + + 8. You may not copy, modify, sublicense, link with, or distribute +the Library except as expressly provided under this License. Any +attempt otherwise to copy, modify, sublicense, link with, or +distribute the Library is void, and will automatically terminate your +rights under this License. However, parties who have received copies, +or rights, from you under this License will not have their licenses +terminated so long as such parties remain in full compliance. + + 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are +distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and +modifying or distributing the Library (or any work based on the +Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying -the Program or works based on it. +the Library or works based on it. - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further + 10. Each time you redistribute the Library (or any work based on the +Library), the recipient automatically receives a license from the +original licensor to copy, distribute, link with or modify the Library +subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to +You are not responsible for enforcing compliance by third parties with this License. - 7. If, as a consequence of a court judgment or allegation of patent + 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by +may not distribute the Library at all. For example, if a patent +license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. +refrain entirely from distribution of the Library. -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. +If any portion of this section is held invalid or unenforceable under any +particular circumstance, the balance of the section is intended to apply, +and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is +integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that @@ -235,122 +410,109 @@ This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. - 8. If the distribution and/or use of the Program is restricted in + 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. +original copyright holder who places the Library under this License may add +an explicit geographical distribution limitation excluding those countries, +so that distribution is permitted only in or among countries not thus +excluded. In such case, this License incorporates the limitation as if +written in the body of this License. - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. + 13. The Free Software Foundation may publish revised and/or new +versions of the Lesser General Public License from time to time. +Such new versions will be similar in spirit to the present version, +but may differ in detail to address new problems or concerns. -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. +Each version is given a distinguishing version number. If the Library +specifies a version number of this License which applies to it and +"any later version", you have the option of following the terms and +conditions either of that version or of any later version published by +the Free Software Foundation. If the Library does not specify a +license version number, you may choose any version ever published by +the Free Software Foundation. - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. + 14. If you wish to incorporate parts of the Library into other free +programs whose distribution conditions are incompatible with these, +write to the author to ask for permission. For software which is +copyrighted by the Free Software Foundation, write to the Free +Software Foundation; we sometimes make exceptions for this. Our +decision will be guided by the two goals of preserving the free status +of all derivatives of our free software and of promoting the sharing +and reuse of software generally. \subsection nowarranty NO WARRANTY - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. + 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO +WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. +EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR +OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY +KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE +LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME +THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. + 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN +WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY +AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU +FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR +CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE +LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING +RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A +FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF +SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH +DAMAGES. \subsection endofterms END OF TERMS AND CONDITIONS \section howtoapply How to Apply These Terms to Your New Programs - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. + If you develop a new library, and you want it to be of the greatest +possible use to the public, we recommend making it free software that +everyone can redistribute and change. You can do so by permitting +redistribution under these terms (or, alternatively, under the terms of the +ordinary General Public License). - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. + To apply these terms, attach the following notices to the library. It is +safest to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least the +"copyright" line and a pointer to where the full notice is found. \verbatim - <one line to give the program's name and a brief idea of what it does.> + <one line to give the library's name and a brief idea of what it does.> Copyright (C) <year> <name of author> - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Lesser General Public + License as published by the Free Software Foundation; either + version 2.1 of the License, or (at your option) any later version. - This program is distributed in the hope that it will be useful, + This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + Lesser General Public License for more details. - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + You should have received a copy of the GNU Lesser General Public + License along with this library; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA \endverbatim Also add information on how to contact you by electronic and paper mail. -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - -\verbatim - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. -\endverbatim - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if +school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: \verbatim - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. + Yoyodyne, Inc., hereby disclaims all copyright interest in the + library `Frob' (a library for tweaking knobs) written by James Random Hacker. - <signature of Ty Coon>, 1 April 1989 + <signature of Ty Coon>, 1 April 1990 Ty Coon, President of Vice \endverbatim -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. - +That's all there is to it! + +<a href="http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html">Source</a> + */ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-24 17:00:31
|
Revision: 229 http://stdair.svn.sourceforge.net/stdair/?rev=229&view=rev Author: denis_arnaud Date: 2010-07-24 17:00:24 +0000 (Sat, 24 Jul 2010) Log Message: ----------- [Doc] Updated the tool for document generation (in order to produce PDF documents). Modified Paths: -------------- trunk/stdair/doc/Makefile.am Modified: trunk/stdair/doc/Makefile.am =================================================================== --- trunk/stdair/doc/Makefile.am 2010-07-24 16:56:03 UTC (rev 228) +++ trunk/stdair/doc/Makefile.am 2010-07-24 17:00:24 UTC (rev 229) @@ -78,4 +78,4 @@ rm -rf $(DESTDIR)$(docdir) clean-local: - rm -rf html *.log *.tag + rm -rf html latex *.log *.tag This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-24 16:56:10
|
Revision: 228 http://stdair.svn.sourceforge.net/stdair/?rev=228&view=rev Author: denis_arnaud Date: 2010-07-24 16:56:03 +0000 (Sat, 24 Jul 2010) Log Message: ----------- [Doc] Updated the tool for document generation (in order to produce PDF documents). Modified Paths: -------------- trunk/stdair/Makefile.am trunk/stdair/doc/Makefile.am trunk/stdair/doc/doxygen_html.cfg.in Modified: trunk/stdair/Makefile.am =================================================================== --- trunk/stdair/Makefile.am 2010-07-24 15:45:56 UTC (rev 227) +++ trunk/stdair/Makefile.am 2010-07-24 16:56:03 UTC (rev 228) @@ -44,18 +44,24 @@ dist-html: $(MAKE) -C doc dist-html +dist-tex: + $(MAKE) -C doc dist-tex -snapshot: snapshot-src snapshot-html +snapshot: snapshot-src snapshot-html snapshot-tex + snapshot-src: $(MAKE) dist distdir=@PACKAGE_TARNAME@-`date +"%Y%m%d"` snapshot-html: $(MAKE) -C doc dist-html html_tarname=@PACKAGE_TARNAME@-doc-`date +"%Y%m%d"` -upload: upload-src upload-html +snapshot-tex: + $(MAKE) -C doc dist-tex tex_tarname=@PACKAGE_TARNAME@-tex-`date +"%Y%m%d"` +upload: upload-src upload-html upload-tex + upload-src: dist @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-@VERSION@.tar.gz \ @PACKAGE_TARNAME@-@VERSION@.tar.bz2 @@ -64,3 +70,6 @@ @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-doc-@VERSION@.tar.gz \ @PACKAGE_TARNAME@-doc-@VERSION@.tar.bz2 +upload-tex: dist-tex + @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-tex-@VERSION@.tar.gz \ + @PACKAGE_TARNAME@-tex-@VERSION@.tar.bz2 Modified: trunk/stdair/doc/Makefile.am =================================================================== --- trunk/stdair/doc/Makefile.am 2010-07-24 15:45:56 UTC (rev 227) +++ trunk/stdair/doc/Makefile.am 2010-07-24 16:56:03 UTC (rev 228) @@ -15,6 +15,7 @@ docdir = @docdir@ html_tarname = @PACKAGE_TARNAME@-doc-@PACKAGE_VERSION@ +tex_tarname = @PACKAGE_TARNAME@-tex-@PACKAGE_VERSION@ noinst_DATA = sourceforge/howto_release_stdair.html.in EXTRA_DIST = $(noinst_DATA) @@ -49,6 +50,14 @@ bzip2 -9 -c > $(top_builddir)/$(html_tarname).tar.bz2 rm -rf $(top_builddir)/$(html_tarname) +dist-tex: html-local + cp -a $(top_builddir)/doc/latex $(top_builddir)/$(tex_tarname) + tar chof - $(top_builddir)/$(tex_tarname) | \ + gzip --best -c > $(top_builddir)/$(tex_tarname).tar.gz + tar chof - $(top_builddir)/$(tex_tarname) | \ + bzip2 -9 -c > $(top_builddir)/$(tex_tarname).tar.bz2 + rm -rf $(top_builddir)/$(tex_tarname) + install-data-local: html-local $(mkinstalldirs) $(DESTDIR)$(docdir) if test -d html; then \ @@ -57,6 +66,13 @@ $(INSTALL_DATA) $$f $(DESTDIR)$(docdir)/html; \ done \ fi + $(mkinstalldirs) $(DESTDIR)$(docdir) + if test -d latex; then \ + $(mkinstalldirs) $(DESTDIR)$(docdir)/latex; \ + for f in latex/*; do \ + $(INSTALL_DATA) $$f $(DESTDIR)$(docdir)/latex; \ + done \ + fi uninstall-local: rm -rf $(DESTDIR)$(docdir) Modified: trunk/stdair/doc/doxygen_html.cfg.in =================================================================== --- trunk/stdair/doc/doxygen_html.cfg.in 2010-07-24 15:45:56 UTC (rev 227) +++ trunk/stdair/doc/doxygen_html.cfg.in 2010-07-24 16:56:03 UTC (rev 228) @@ -1,4 +1,4 @@ -# Doxyfile 1.5.2 +# Doxyfile 1.6.2-20100208 # This file describes the settings to be used by the documentation system # doxygen (www.doxygen.org) for a project @@ -14,190 +14,215 @@ # Project related configuration options #--------------------------------------------------------------------------- -# This tag specifies the encoding used for all characters in the config file that -# follow. The default is UTF-8 which is also the encoding used for all text before -# the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into -# libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of -# possible encodings. +# This tag specifies the encoding used for all characters in the config file +# that follow. The default is UTF-8 which is also the encoding used for all +# text before the first occurrence of this tag. Doxygen uses libiconv (or the +# iconv built into libc) for the transcoding. See +# http://www.gnu.org/software/libiconv for the list of possible encodings. DOXYFILE_ENCODING = UTF-8 -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded # by quotes) that should identify the project. PROJECT_NAME = @PACKAGE_NAME@ -# The PROJECT_NUMBER tag can be used to enter a project or revision number. -# This could be handy for archiving the generated documentation or +# The PROJECT_NUMBER tag can be used to enter a project or revision number. +# This could be handy for archiving the generated documentation or # if some version control system is used. PROJECT_NUMBER = @PACKAGE_VERSION@ -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) -# base path where the generated documentation will be put. -# If a relative path is entered, it will be relative to the location +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) +# base path where the generated documentation will be put. +# If a relative path is entered, it will be relative to the location # where doxygen was started. If left blank the current directory will be used. -OUTPUT_DIRECTORY = +OUTPUT_DIRECTORY = -# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create -# 4096 sub-directories (in 2 levels) under the output directory of each output -# format and will distribute the generated files over these directories. -# Enabling this option can be useful when feeding doxygen a huge amount of -# source files, where putting all generated files in the same directory would +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create +# 4096 sub-directories (in 2 levels) under the output directory of each output +# format and will distribute the generated files over these directories. +# Enabling this option can be useful when feeding doxygen a huge amount of +# source files, where putting all generated files in the same directory would # otherwise cause performance problems for the file system. CREATE_SUBDIRS = NO -# The OUTPUT_LANGUAGE tag is used to specify the language in which all -# documentation generated by doxygen is written. Doxygen will use this -# information to generate all constant output in the proper language. -# The default language is English, other supported languages are: -# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, -# Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, -# Italian, Japanese, Japanese-en (Japanese with English messages), Korean, -# Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, -# Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. +# The OUTPUT_LANGUAGE tag is used to specify the language in which all +# documentation generated by doxygen is written. Doxygen will use this +# information to generate all constant output in the proper language. +# The default language is English, other supported languages are: +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, +# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, +# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English +# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, +# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, +# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. OUTPUT_LANGUAGE = English -# 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). +# 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 -# 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 +# 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 -# This tag implements a quasi-intelligent brief description abbreviator -# that is used to form the text in various listings. Each string -# in this list, if found as the leading text of the brief description, will be -# stripped from the text and the result after processing the whole list, is -# used as the annotated text. Otherwise, the brief description is used as-is. -# If left blank, the following values are used ("$name" is automatically -# replaced with the name of the entity): "The $name class" "The $name widget" -# "The $name file" "is" "provides" "specifies" "contains" +# This tag implements a quasi-intelligent brief description abbreviator +# that is used to form the text in various listings. Each string +# in this list, if found as the leading text of the brief description, will be +# stripped from the text and the result after processing the whole list, is +# used as the annotated text. Otherwise, the brief description is used as-is. +# If left blank, the following values are used ("$name" is automatically +# replaced with the name of the entity): "The $name class" "The $name widget" +# "The $name file" "is" "provides" "specifies" "contains" # "represents" "a" "an" "the" -ABBREVIATE_BRIEF = +ABBREVIATE_BRIEF = -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then -# Doxygen will generate a detailed section even if there is only a brief +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then +# Doxygen will generate a detailed section even if there is only a brief # description. ALWAYS_DETAILED_SEC = NO -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all -# inherited members of a class in the documentation of that class as if those -# members were ordinary class members. Constructors, destructors and assignment +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all +# inherited members of a class in the documentation of that class as if those +# members were ordinary class members. Constructors, destructors and assignment # operators of the base classes will not be shown. INLINE_INHERITED_MEMB = YES -# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full -# path before files name in the file list and in the header files. If set +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full +# path before files name in the file list and in the header files. If set # to NO the shortest path that makes the file name unique will be used. FULL_PATH_NAMES = YES -# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag -# can be used to strip a user-defined part of the path. Stripping is -# only done if one of the specified strings matches the left-hand part of -# the path. The tag can be used to show relative paths in the file list. -# If left blank the directory from which doxygen is run is used as the +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag +# can be used to strip a user-defined part of the path. Stripping is +# only done if one of the specified strings matches the left-hand part of +# the path. The tag can be used to show relative paths in the file list. +# If left blank the directory from which doxygen is run is used as the # path to strip. STRIP_FROM_PATH = @top_srcdir@/ -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of -# the path mentioned in the documentation of a class, which tells -# the reader which header file to include in order to use a class. -# If left blank only the name of the header file containing the class -# definition is used. Otherwise one should specify the include paths that +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of +# the path mentioned in the documentation of a class, which tells +# the reader which header file to include in order to use a class. +# If left blank only the name of the header file containing the class +# definition is used. Otherwise one should specify the include paths that # are normally passed to the compiler using the -I flag. STRIP_FROM_INC_PATH = @top_srcdir@/ -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter -# (but less readable) file names. This can be useful is your file systems +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter +# (but less readable) file names. This can be useful is your file systems # doesn't support long names like on DOS, Mac, or CD-ROM. SHORT_NAMES = NO -# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen -# will interpret the first line (until the first dot) of a JavaDoc-style -# comment as the brief description. If set to NO, the JavaDoc -# comments will behave just like the Qt-style comments (thus requiring an -# explicit @brief command for a brief description. +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen +# will interpret the first line (until the first dot) of a JavaDoc-style +# comment as the brief description. If set to NO, the JavaDoc +# comments will behave just like regular Qt-style comments +# (thus requiring an explicit @brief command for a brief description.) JAVADOC_AUTOBRIEF = NO -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen -# treat a multi-line C++ special comment block (i.e. a block of //! or /// -# comments) as a brief description. This used to be the default behaviour. -# The new default is to treat a multi-line C++ comment block as a detailed +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will +# interpret the first line (until the first dot) of a Qt-style +# comment as the brief description. If set to NO, the comments +# will behave just like regular Qt-style comments (thus requiring +# an explicit \brief command for a brief description.) + +QT_AUTOBRIEF = NO + +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen +# treat a multi-line C++ special comment block (i.e. a block of //! or /// +# comments) as a brief description. This used to be the default behaviour. +# The new default is to treat a multi-line C++ comment block as a detailed # description. Set this tag to YES if you prefer the old behaviour instead. MULTILINE_CPP_IS_BRIEF = NO -# If the DETAILS_AT_TOP tag is set to YES then Doxygen -# will output the detailed description near the top, like JavaDoc. -# If set to NO, the detailed description appears after the member -# documentation. - -DETAILS_AT_TOP = YES - -# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented -# member inherits the documentation from any documented member that it +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented +# member inherits the documentation from any documented member that it # re-implements. INHERIT_DOCS = YES -# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce -# a new page for each member. If set to NO, the documentation of a member will +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce +# a new page for each member. If set to NO, the documentation of a member will # be part of the file/class/namespace that contains it. SEPARATE_MEMBER_PAGES = NO -# The TAB_SIZE tag can be used to set the number of spaces in a tab. +# The TAB_SIZE tag can be used to set the number of spaces in a tab. # Doxygen uses this value to replace tabs by spaces in code fragments. TAB_SIZE = 8 -# This tag can be used to specify a number of aliases that acts -# as commands in the documentation. An alias has the form "name=value". -# For example adding "sideeffect=\par Side Effects:\n" will allow you to -# put the command \sideeffect (or @sideeffect) in the documentation, which -# will result in a user-defined paragraph with heading "Side Effects:". +# This tag can be used to specify a number of aliases that acts +# as commands in the documentation. An alias has the form "name=value". +# For example adding "sideeffect=\par Side Effects:\n" will allow you to +# put the command \sideeffect (or @sideeffect) in the documentation, which +# will result in a user-defined paragraph with heading "Side Effects:". # You can put \n's in the value part of an alias to insert newlines. -ALIASES = +ALIASES = -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C -# sources only. Doxygen will then generate output that is more tailored for C. -# For instance, some of the names that are used will be different. The list +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C +# sources only. Doxygen will then generate output that is more tailored for C. +# For instance, some of the names that are used will be different. The list # of all members will be omitted, etc. OPTIMIZE_OUTPUT_FOR_C = NO -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java -# sources only. Doxygen will then generate output that is more tailored for Java. -# For instance, namespaces will be presented as packages, qualified scopes -# will look different, etc. +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java +# sources only. Doxygen will then generate output that is more tailored for +# Java. For instance, namespaces will be presented as packages, qualified +# scopes will look different, etc. OPTIMIZE_OUTPUT_JAVA = NO -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to -# include (a tag file for) the STL sources as input, then you should -# set this tag to YES in order to let doxygen match functions declarations and -# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. -# func(std::string) {}). This also make the inheritance and collaboration +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran +# sources only. Doxygen will then generate output that is more tailored for +# Fortran. + +OPTIMIZE_FOR_FORTRAN = NO + +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL +# sources. Doxygen will then generate output that is tailored for +# VHDL. + +OPTIMIZE_OUTPUT_VHDL = NO + +# Doxygen selects the parser to use depending on the extension of the files it parses. +# With this tag you can assign which parser to use for a given extension. +# Doxygen has a built-in mapping, but you can override or extend it using this tag. +# The format is ext=language, where ext is a file extension, and language is one of +# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, +# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat +# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), +# use: inc=Fortran f=C. Note that for custom extensions you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. + +EXTENSION_MAPPING = + +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want +# to include (a tag file for) the STL sources as input, then you should +# set this tag to YES in order to let doxygen match functions declarations and +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. +# func(std::string) {}). This also make the inheritance and collaboration # diagrams that involve STL classes more complete and accurate. BUILTIN_STL_SUPPORT = YES @@ -207,248 +232,335 @@ CPP_CLI_SUPPORT = 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 -# member in the group (if any) for the other members of the group. By default +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. +# Doxygen will parse them like normal C++ but will assume all classes use public +# instead of private inheritance when no explicit protection keyword is present. + +SIP_SUPPORT = NO + +# For Microsoft's IDL there are propget and propput attributes to indicate getter +# and setter methods for a property. Setting this option to YES (the default) +# will make doxygen to replace the get and set methods by a property in the +# documentation. This will only work if the methods are indeed getting or +# setting a simple type. If this is not the case, or you want to show the +# methods anyway, you should set this option to NO. + +IDL_PROPERTY_SUPPORT = YES + +# 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 +# member in the group (if any) for the other members of the group. By default # all members of a group must be documented explicitly. DISTRIBUTE_GROUP_DOC = YES -# Set the SUBGROUPING tag to YES (the default) to allow class member groups of -# the same type (for instance a group of public functions) to be put as a -# subgroup of that type (e.g. under the Public Functions section). Set it to -# NO to prevent subgrouping. Alternatively, this can be done per class using +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of +# the same type (for instance a group of public functions) to be put as a +# subgroup of that type (e.g. under the Public Functions section). Set it to +# NO to prevent subgrouping. Alternatively, this can be done per class using # the \nosubgrouping command. SUBGROUPING = YES +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum +# is documented as struct, union, or enum with the name of the typedef. So +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct +# with name TypeT. When disabled the typedef will appear as a member of a file, +# namespace, or class. And the struct will be named TypeS. This can typically +# be useful for C code in case the coding convention dictates that all compound +# types are typedef'ed and only the typedef is referenced, never the tag name. + +TYPEDEF_HIDES_STRUCT = NO + +# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to +# determine which symbols to keep in memory and which to flush to disk. +# When the cache is full, less often used symbols will be written to disk. +# For small to medium size projects (<1000 input files) the default value is +# probably good enough. For larger projects a too small cache size can cause +# doxygen to be busy swapping symbols to and from disk most of the time +# causing a significant performance penality. +# If the system has enough physical memory increasing the cache will improve the +# performance by keeping more symbols in memory. Note that the value works on +# a logarithmic scale so increasing the size by one will rougly double the +# memory usage. The cache size is given by this formula: +# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, +# corresponding to a cache size of 2^16 = 65536 symbols + +SYMBOL_CACHE_SIZE = 0 + #--------------------------------------------------------------------------- # Build related configuration options #--------------------------------------------------------------------------- -# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in -# documentation are documented, even if no documentation was available. -# Private class members and static file members will be hidden unless +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in +# documentation are documented, even if no documentation was available. +# 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 -# If the EXTRACT_PRIVATE tag is set to YES all private members of a class +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class # will be included in the documentation. EXTRACT_PRIVATE = NO -# If the EXTRACT_STATIC tag is set to YES all static members of a file +# If the EXTRACT_STATIC tag is set to YES all static members of a file # will be included in the documentation. EXTRACT_STATIC = YES -# 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 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 -# 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 -# the interface are included in the documentation. +# 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 +# the interface are included in the documentation. # If set to NO (the default) only methods in the interface are included. EXTRACT_LOCAL_METHODS = NO -# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all -# undocumented members of documented classes, files or namespaces. -# If set to NO (the default) these members will be included in the -# various overviews, but no documentation section is generated. +# If this flag is set to YES, the members of anonymous namespaces will be +# extracted and appear in the documentation as a namespace called +# 'anonymous_namespace{file}', where file will be replaced with the base +# name of the file that contains the anonymous namespace. By default +# anonymous namespace are hidden. + +EXTRACT_ANON_NSPACES = NO + +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all +# undocumented members of documented classes, files or namespaces. +# If set to NO (the default) these members will be included in the +# various overviews, but no documentation section is generated. # This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_MEMBERS = NO -# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all -# undocumented classes that are normally visible in the class hierarchy. -# If set to NO (the default) these classes will be included in the various +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all +# undocumented classes that are normally visible in the class hierarchy. +# If set to NO (the default) these classes will be included in the various # overviews. This option has no effect if EXTRACT_ALL is enabled. HIDE_UNDOC_CLASSES = YES -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all -# friend (class|struct|union) declarations. -# If set to NO (the default) these declarations will be included in the +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all +# friend (class|struct|union) declarations. +# If set to NO (the default) these declarations will be included in the # documentation. HIDE_FRIEND_COMPOUNDS = NO -# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any -# documentation blocks found inside the body of a function. -# If set to NO (the default) these blocks will be appended to the +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any +# documentation blocks found inside the body of a function. +# If set to NO (the default) these blocks will be appended to the # function's detailed documentation block. HIDE_IN_BODY_DOCS = YES -# The INTERNAL_DOCS tag determines if documentation -# that is typed after a \internal command is included. If the tag is set -# to NO (the default) then the documentation will be excluded. +# The INTERNAL_DOCS tag determines if documentation +# that is typed after a \internal command is included. If the tag is set +# to NO (the default) then the documentation will be excluded. # Set it to YES to include the internal documentation. INTERNAL_DOCS = YES -# 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 -# allowed. This is useful if you have classes or files whose names only differ -# in case and if your file system supports case sensitive file names. Windows +# 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 +# allowed. This is useful if you have classes or files whose names only differ +# in case and if your file system supports case sensitive file names. Windows # and Mac users are advised to set this option to NO. CASE_SENSE_NAMES = YES -# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen -# will show members with their full class and namespace scopes in the +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen +# will show members with their full class and namespace scopes in the # documentation. If set to YES the scope will be hidden. HIDE_SCOPE_NAMES = NO -# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen -# will put a list of the files that are included by a file in the documentation +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen +# will put a list of the files that are included by a file in the documentation # of that file. SHOW_INCLUDE_FILES = YES -# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] +# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen +# will list include files with double quotes in the documentation +# rather than with sharp brackets. + +FORCE_LOCAL_INCLUDES = 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 -# 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 +# 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 = 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 -# by member name. If set to NO (the default) the members will appear in +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the +# brief documentation of file, namespace and class members alphabetically +# by member name. If set to NO (the default) the members will appear in # declaration order. SORT_BRIEF_DOCS = NO -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be -# sorted by fully-qualified names, including namespaces. If set to -# NO (the default), the class list will be sorted only by class name, -# not including the namespace part. +# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the (brief and detailed) documentation of class members so that constructors and destructors are listed first. If set to NO (the default) the constructors will appear in the respective orders defined by SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. + +SORT_MEMBERS_CTORS_1ST = NO + +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the +# hierarchy of group names into alphabetical order. If set to NO (the default) +# the group names will appear in their defined order. + +SORT_GROUP_NAMES = NO + +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be +# sorted by fully-qualified names, including namespaces. If set to +# NO (the default), the class list will be sorted only by class name, +# not including the namespace part. # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. -# Note: This option applies only to the class list, not to the +# Note: This option applies only to the class list, not to the # alphabetical list. SORT_BY_SCOPE_NAME = NO -# The GENERATE_TODOLIST tag can be used to enable (YES) or -# disable (NO) the todo list. This list is created by putting \todo +# The GENERATE_TODOLIST tag can be used to enable (YES) or +# disable (NO) the todo list. This list is created by putting \todo # commands in the documentation. GENERATE_TODOLIST = YES -# The GENERATE_TESTLIST tag can be used to enable (YES) or -# disable (NO) the test list. This list is created by putting \test +# 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 -# The GENERATE_BUGLIST tag can be used to enable (YES) or -# disable (NO) the bug list. This list is created by putting \bug +# 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 -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or -# disable (NO) the deprecated list. This list is created by putting +# 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 -# The ENABLED_SECTIONS tag can be used to enable conditional +# The ENABLED_SECTIONS tag can be used to enable conditional # documentation sections, marked by \if sectionname ... \endif. -ENABLED_SECTIONS = +ENABLED_SECTIONS = -# 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 -# the documentation. If the initializer consists of more lines than specified -# here it will be hidden. Use a value of 0 to hide initializers completely. -# The appearance of the initializer of individual variables and defines in the -# documentation can be controlled using \showinitializer or \hideinitializer +# 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 +# the documentation. If the initializer consists of more lines than specified +# here it will be hidden. Use a value of 0 to hide initializers completely. +# The appearance of the initializer of individual variables and defines in the +# documentation can be controlled using \showinitializer or \hideinitializer # command in the documentation regardless of this setting. MAX_INITIALIZER_LINES = 30 -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated -# at the bottom of the documentation of classes and structs. If set to YES the +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated +# 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 -# If the sources in your project are distributed over multiple directories -# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy +# 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. The default is NO. SHOW_DIRECTORIES = YES -# 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 -# version control system). Doxygen will invoke the program by executing (via -# popen()) the command <command> <input-file>, where <command> is the value of -# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file -# provided by doxygen. Whatever the program writes to standard output +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. +# This will remove the Files entry from the Quick Index and from the +# Folder Tree View (if specified). The default is YES. + +SHOW_FILES = YES + +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the +# Namespaces page. +# This will remove the Namespaces entry from the Quick Index +# and from the Folder Tree View (if specified). The default is YES. + +SHOW_NAMESPACES = YES + +# 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 version control system). Doxygen will invoke the program by executing (via +# popen()) the command <command> <input-file>, where <command> is the value of +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file +# provided by doxygen. Whatever the program writes to standard output # is used as the file version. See the manual for examples. -FILE_VERSION_FILTER = +FILE_VERSION_FILTER = +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by +# doxygen. The layout file controls the global structure of the generated output files +# in an output format independent way. The create the layout file that represents +# doxygen's defaults, run doxygen with the -l option. You can optionally specify a +# file name after the option, if omitted DoxygenLayout.xml will be used as the name +# of the layout file. + +LAYOUT_FILE = + #--------------------------------------------------------------------------- # configuration options related to warning and progress messages #--------------------------------------------------------------------------- -# The QUIET tag can be used to turn on/off the messages that are generated +# The QUIET tag can be used to turn on/off the messages that are generated # by doxygen. Possible values are YES and NO. If left blank NO is used. QUIET = NO -# The WARNINGS tag can be used to turn on/off the warning messages that are -# generated by doxygen. Possible values are YES and NO. If left blank +# The WARNINGS tag can be used to turn on/off the warning messages that are +# generated by doxygen. Possible values are YES and NO. If left blank # NO is used. WARNINGS = YES -# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings -# for undocumented members. If EXTRACT_ALL is set to YES then this flag will +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will # automatically be disabled. WARN_IF_UNDOCUMENTED = YES -# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for -# potential errors in the documentation, such as not documenting some -# parameters in a documented function, or documenting parameters that +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for +# potential errors in the documentation, such as not documenting some +# parameters in a documented function, or documenting parameters that # don't exist or using markup commands wrongly. WARN_IF_DOC_ERROR = YES -# This WARN_NO_PARAMDOC option can be abled to get warnings for -# functions that are documented, but have no documentation for their parameters -# or return value. If set to NO (the default) doxygen will only warn about -# wrong or incomplete parameter documentation, but not about the absence of +# This WARN_NO_PARAMDOC option can be abled to get warnings for +# functions that are documented, but have no documentation for their parameters +# or return value. If set to NO (the default) doxygen will only warn about +# wrong or incomplete parameter documentation, but not about the absence of # documentation. WARN_NO_PARAMDOC = NO -# The WARN_FORMAT tag determines the format of the warning messages that -# doxygen can produce. The string should contain the $file, $line, and $text -# tags, which will be replaced by the file and line number from which the -# warning originated and the warning text. Optionally the format may contain -# $version, which will be replaced by the version of the file (if it could +# The WARN_FORMAT tag determines the format of the warning messages that +# doxygen can produce. The string should contain the $file, $line, and $text +# tags, which will be replaced by the file and line number from which the +# warning originated and the warning text. Optionally the format may contain +# $version, which will be replaced by the version of the file (if it could # be obtained via FILE_VERSION_FILTER) WARN_FORMAT = "$file:$line: $text" -# The WARN_LOGFILE tag can be used to specify a file to which warning -# and error messages should be written. If left blank the output is written +# The WARN_LOGFILE tag can be used to specify a file to which warning +# and error messages should be written. If left blank the output is written # to stderr. WARN_LOGFILE = doxygen_html.log @@ -457,9 +569,9 @@ # configuration options related to the input files #--------------------------------------------------------------------------- -# The INPUT tag can be used to specify the files and/or directories that contain -# documented source files. You may enter file names like "myfile.cpp" or -# directories like "/usr/src/myproject". Separate the files or directories +# The INPUT tag can be used to specify the files and/or directories that contain +# documented source files. You may enter file names like "myfile.cpp" or +# directories like "/usr/src/myproject". Separate the files or directories # with spaces. INPUT = @top_srcdir@/@PACKAGE@ \ @@ -467,108 +579,113 @@ @top_builddir@/doc/local \ @top_srcdir@/doc/tutorial -# This tag can be used to specify the character encoding of the source files that -# doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default -# input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. -# See http://www.gnu.org/software/libiconv for the list of possible encodings. +# This tag can be used to specify the character encoding of the source files +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is +# also the default input encoding. Doxygen uses libiconv (or the iconv built +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for +# the list of possible encodings. INPUT_ENCODING = UTF-8 -# If the value of the INPUT tag contains directories, you can use the -# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left -# blank the following patterns are tested: -# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx -# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py +# If the value of the INPUT tag contains directories, you can use the +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left +# blank the following patterns are tested: +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx +# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90 FILE_PATTERNS = *.hpp \ *.cpp \ *.doc -# The RECURSIVE tag can be used to turn specify whether or not subdirectories -# should be searched for input files as well. Possible values are YES and NO. +# The RECURSIVE tag can be used to turn specify whether or not subdirectories +# should be searched for input files as well. Possible values are YES and NO. # If left blank NO is used. RECURSIVE = YES -# 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 +# 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 = @top_builddir@/@PACKAGE@/config.h \ @top_srcdir@/@PACKAGE@/config_msvc.h -# The EXCLUDE_SYMLINKS tag can be used select whether or not files or -# directories that are symbolic links (a Unix filesystem feature) are excluded +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or +# directories that are symbolic links (a Unix filesystem feature) are excluded # from the input. EXCLUDE_SYMLINKS = NO -# If the value of the INPUT tag contains directories, you can use the -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude -# certain files from those directories. Note that the wildcards are matched -# against the file with absolute path, so to exclude all test directories +# If the value of the INPUT tag contains directories, you can use the +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude +# certain files from those directories. Note that the wildcards are matched +# against the file with absolute path, so to exclude all test directories # for example use the pattern */test/* -EXCLUDE_PATTERNS = +EXCLUDE_PATTERNS = -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names -# (namespaces, classes, functions, etc.) that should be excluded from the output. -# The symbol name can be a fully qualified name, a word, or if the wildcard * is used, -# a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names +# (namespaces, classes, functions, etc.) that should be excluded from the +# output. The symbol name can be a fully qualified name, a word, or if the +# wildcard * is used, a substring. Examples: ANamespace, AClass, +# AClass::ANamespace, ANamespace::*Test -EXCLUDE_SYMBOLS = +EXCLUDE_SYMBOLS = -# The EXAMPLE_PATH tag can be used to specify one or more files or -# directories that contain example code fragments that are included (see +# The EXAMPLE_PATH tag can be used to specify one or more files or +# directories that contain example code fragments that are included (see # the \include command). EXAMPLE_PATH = @top_srcdir@/doc/tutorial/src \ @top_srcdir@/test -# If the value of the EXAMPLE_PATH tag contains directories, you can use the -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp -# and *.h) to filter out the source-files in the directories. If left +# If the value of the EXAMPLE_PATH tag contains directories, you can use the +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp +# and *.h) to filter out the source-files in the directories. If left # blank all files are included. EXAMPLE_PATTERNS = *.hpp \ *.cpp \ *.ref -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude -# commands irrespective of the value of the RECURSIVE tag. +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be +# searched for input files to be used with the \include or \dontinclude +# commands irrespective of the value of the RECURSIVE tag. # Possible values are YES and NO. If left blank NO is used. EXAMPLE_RECURSIVE = NO -# The IMAGE_PATH tag can be used to specify one or more files or -# directories that contain image that are included in the documentation (see +# The IMAGE_PATH tag can be used to specify one or more files or +# directories that contain image that are included in the documentation (see # the \image command). IMAGE_PATH = @top_srcdir@/doc/images -# The INPUT_FILTER tag can be used to specify a program that doxygen should -# invoke to filter for each input file. Doxygen will invoke the filter program -# by executing (via popen()) the command <filter> <input-file>, where <filter> -# is the value of the INPUT_FILTER tag, and <input-file> is the name of an -# input file. Doxygen will then use the output that the filter program writes -# to standard output. If FILTER_PATTERNS is specified, this tag will be +# The INPUT_FILTER tag can be used to specify a program that doxygen should +# invoke to filter for each input file. Doxygen will invoke the filter program +# by executing (via popen()) the command <filter> <input-file>, where <filter> +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an +# input file. Doxygen will then use the output that the filter program writes +# to standard output. +# If FILTER_PATTERNS is specified, this tag will be # ignored. -INPUT_FILTER = +INPUT_FILTER = -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern -# basis. Doxygen will compare the file name with each pattern and apply the -# filter if there is a match. The filters are a list of the form: -# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further -# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern +# basis. +# Doxygen will compare the file name with each pattern and apply the +# filter if there is a match. +# The filters are a list of the form: +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER # is applied to all files. -FILTER_PATTERNS = +FILTER_PATTERNS = -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using -# INPUT_FILTER) will be used to filter the input files when producing source +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using +# INPUT_FILTER) will be used to filter the input files when producing source # files to browse (i.e. when SOURCE_BROWSER is set to YES). FILTER_SOURCE_FILES = NO @@ -577,32 +694,32 @@ # configuration options related to source browsing #--------------------------------------------------------------------------- -# If the SOURCE_BROWSER tag is set to YES then a list of source files will -# be generated. Documented entities will be cross-referenced with these sources. -# Note: To get rid of all source code in the generated output, make sure also +# If the SOURCE_BROWSER tag is set to YES then a list of source files will +# be generated. Documented entities will be cross-referenced with these sources. +# Note: To get rid of all source code in the generated output, make sure also # VERBATIM_HEADERS is set to NO. SOURCE_BROWSER = YES -# Setting the INLINE_SOURCES tag to YES will include the body +# Setting the INLINE_SOURCES tag to YES will include the body # of functions and classes directly in the documentation. INLINE_SOURCES = NO -# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct -# doxygen to hide any special comment blocks from generated source code +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct +# doxygen to hide any special comment blocks from generated source code # fragments. Normal C and C++ comments will always remain visible. STRIP_CODE_COMMENTS = YES -# If the REFERENCED_BY_RELATION tag is set to YES (the default) -# then for each documented function all documented +# If the REFERENCED_BY_RELATION tag is set to YES +# then for each documented function all documented # functions referencing it will be listed. REFERENCED_BY_RELATION = YES -# If the REFERENCES_RELATION tag is set to YES (the default) -# then for each documented function all documented entities +# If the REFERENCES_RELATION tag is set to YES +# then for each documented function all documented entities # called/used by that function will be listed. REFERENCES_RELATION = YES @@ -610,20 +727,21 @@ # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will -# link to the source code. Otherwise they will link to the documentstion. +# link to the source code. +# Otherwise they will link to the documentation. REFERENCES_LINK_SOURCE = YES -# If the USE_HTAGS tag is set to YES then the references to source code -# will point to the HTML generated by the htags(1) tool instead of doxygen -# built-in source browser. The htags tool is part of GNU's global source -# tagging system (see http://www.gnu.org/software/global/global.html). You +# If the USE_HTAGS tag is set to YES then the references to source code +# will point to the HTML generated by the htags(1) tool instead of doxygen +# built-in source browser. The htags tool is part of GNU's global source +# tagging system (see http://www.gnu.org/software/global/global.html). You # will need version 4.8.6 or higher. USE_HTAGS = 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 +# 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 # which an include is specified. Set to NO to disable this. VERBATIM_HEADERS = YES @@ -632,279 +750,429 @@ # configuration options related to the alphabetical class index #--------------------------------------------------------------------------- -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index -# of all compounds will be generated. Enable this if the project +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index +# of all compounds will be generated. Enable this if the project # contains a lot of classes, structs, unions or interfaces. ALPHABETICAL_INDEX = YES -# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then -# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns # in which this list will be split (can be a number in the range [1..20]) COLS_IN_ALPHA_INDEX = 4 -# In case all classes in a project start with a common prefix, all -# classes will be put under the same header in the alphabetical index. -# The IGNORE_PREFIX tag can be used to specify one or more prefixes that +# In case all classes in a project start with a common prefix, all +# classes will be put under the same header in the alphabetical index. +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that # should be ignored while generating the index headers. -IGNORE_PREFIX = +IGNORE_PREFIX = #--------------------------------------------------------------------------- # configuration options related to the HTML output #--------------------------------------------------------------------------- -# If the GENERATE_HTML tag is set to YES (the default) Doxygen will +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will # generate HTML output. GENERATE_HTML = YES -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. -# If a relative path is entered the value of OUTPUT_DIRECTORY will be +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. +# If a relative path is entered the value of OUTPUT_DIRECTORY will be # put in front of it. If left blank `html' will be used as the default path. HTML_OUTPUT = html -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for -# each generated HTML page (for example: .htm,.php,.asp). If it is left blank +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank # doxygen will generate files with .html extension. HTML_FILE_EXTENSION = .html -# The HTML_HEADER tag can be used to specify a personal HTML header for -# each generated HTML page. If it is left blank doxygen will generate a +# The HTML_HEADER tag can be used to specify a personal HTML header for +# each generated HTML page. If it is left blank doxygen will generate a # standard header. HTML_HEADER = @top_srcdir@/doc/local/@PACKAGE@_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 +# 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 # standard footer. HTML_FOOTER = @top_srcdir@/doc/local/@PACKAGE@_footer.html -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading -# style sheet that is used by each HTML page. It can be used to -# fine-tune the look of the HTML output. If the tag is left blank doxygen -# will generate a default style sheet. Note that doxygen will try to copy -# the style sheet file to the HTML output directory, so don't put your own +# If the HTML_TIMESTAMP tag is set to YES then the generated HTML +# documentation will contain the timesstamp. + +HTML_TIMESTAMP = NO + +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading +# style sheet that is used by each HTML page. It can be used to +# fine-tune the look of the HTML output. If the tag is left blank doxygen +# will generate a default style sheet. Note that doxygen will try to copy +# the style sheet file to the HTML output directory, so don't put your own # stylesheet in the HTML output directory as well, or it will be erased! -HTML_STYLESHEET = +HTML_STYLESHEET = -# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, -# files or namespaces will be aligned in HTML using tables. If set to +# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML +# page will contain the date and time when the page was generated. Setting +# this to NO can help when comparing the output of multiple runs. + +HTML_TIMESTAMP = NO + +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, +# files or namespaces will be aligned in HTML using tables. If set to # NO a bullet list will be used. HTML_ALIGN_MEMBERS = YES -# If the GENERATE_HTMLHELP tag is set to YES, additional index files -# will be generated that can be used as input for tools like the -# Microsoft HTML help workshop to generate a compressed HTML help file (.chm) +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML +# documentation will contain sections that can be hidden and shown after the +# page has loaded. For this to work a browser that supports +# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox +# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). + +HTML... [truncated message content] |
From: <den...@us...> - 2010-07-24 15:46:02
|
Revision: 227 http://stdair.svn.sourceforge.net/stdair/?rev=227&view=rev Author: denis_arnaud Date: 2010-07-24 15:45:56 +0000 (Sat, 24 Jul 2010) Log Message: ----------- [Config] Fixed the look-up procedure for the Open MPI ompi_info utility. Modified Paths: -------------- trunk/stdair/config/openmpi.m4 Modified: trunk/stdair/config/openmpi.m4 =================================================================== --- trunk/stdair/config/openmpi.m4 2010-07-23 12:15:17 UTC (rev 226) +++ trunk/stdair/config/openmpi.m4 2010-07-24 15:45:56 UTC (rev 227) @@ -132,7 +132,7 @@ # Look for OpenMPI configuration # # OpenMPI configuration binary - OPENMPI_VERBIN1=ompi_info + OPENMPI_VERBIN=ompi_info AC_MSG_CHECKING([for OpenMPI configuration]) OPENMPI_verdir= @@ -169,7 +169,7 @@ # Derive the full version, e.g., 1.3.3 if test ! -z "$OPENMPI_verdir" then - OPENMPI_VERSION=`${OPENMPI_verdir}/${OPENMPI_VERBIN} | grep "Open MPI:" | cut -d: -f2 | cut -d\ -f2` + OPENMPI_VERSION=`${OPENMPI_verdir}/${OPENMPI_VERBIN} -v ompi full | grep "Open MPI:" | cut -d: -f2 | cut -d\ -f2` fi if test -z "${OPENMPI_VERSION}" ; then OPENMPI_VERSION=${OPENMPI_DEF_VERSION} This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-23 12:15:23
|
Revision: 226 http://stdair.svn.sourceforge.net/stdair/?rev=226&view=rev Author: denis_arnaud Date: 2010-07-23 12:15:17 +0000 (Fri, 23 Jul 2010) Log Message: ----------- [Doc] Updated the manual pages. Modified Paths: -------------- trunk/stdair/man/Makefile.am trunk/stdair/man/stdair-config.1 trunk/stdair/man/stdair.3 Modified: trunk/stdair/man/Makefile.am =================================================================== --- trunk/stdair/man/Makefile.am 2010-07-20 23:43:28 UTC (rev 225) +++ trunk/stdair/man/Makefile.am 2010-07-23 12:15:17 UTC (rev 226) @@ -1,4 +1,5 @@ -# Man pages +# StdAir manual pages + man_MANS = stdair.3 stdair-config.1 EXTRA_DIST = $(man_MANS) Modified: trunk/stdair/man/stdair-config.1 =================================================================== --- trunk/stdair/man/stdair-config.1 2010-07-20 23:43:28 UTC (rev 225) +++ trunk/stdair/man/stdair-config.1 2010-07-23 12:15:17 UTC (rev 226) @@ -6,10 +6,10 @@ [\-\-prefix] [\-\-version] [\-\-libs] [\-\-cflags] .SH DESCRIPTION .PP -\fIstdair-config\fP is a tool that is used to configure to determine +\fIstdair-config\fP is a tool that is used by configure to determine the compiler and linker flags that should be used to compile and link programs that use \fIStdAir\fP. It is also used internally -to the .m4 macros for GNU autoconf that are included with \fIStdAir\fP. +by the .m4 macros, that are included with \fIStdAir\fP, for GNU autoconf. . .SH OPTIONS \fIstdair-config\fP accepts the following options: @@ -18,10 +18,11 @@ Print the currently installed version of \fIStdAir\fP on the standard output. .TP 8 .B \-\-libs -Print the linker flags that are necessary to link a \fIStdAir\fP program, with cblas +Print the linker flags that are necessary to link with the \fIStdAir\fP library .TP 8 .B \-\-cflags -Print the compiler flags that are necessary to compile a \fIStdAir\fP program. +Print the compiler flags that are necessary to compile with the +\fIStdAir\fP library .TP 8 .B \-\-prefix Show the StdAir installation prefix. @@ -30,8 +31,5 @@ .SH COPYRIGHT Copyright \(co 2010 Denis Arnaud -Permission to use, copy, modify, and distribute this software and its -documentation for any purpose and without fee is hereby granted, -provided that the above copyright notice appear in all copies and that -both that copyright notice and this permission notice appear in -supporting documentation. +See the COPYING file for more information on the (LGPLv2) license, or +directly on Internet: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html Modified: trunk/stdair/man/stdair.3 =================================================================== --- trunk/stdair/man/stdair.3 2010-07-20 23:43:28 UTC (rev 225) +++ trunk/stdair/man/stdair.3 2010-07-23 12:15:17 UTC (rev 226) @@ -4,11 +4,11 @@ .SH SYNOPSIS #include <stdair/...> .SH DESCRIPTION -The Standard Airline IT (STDAIR) library is a collection of -routines for travel market simulation. The routines are written from -scratch by the StdAir team in C++, and present a modern Applications -Programming Interface (API) for C/C++ programmers, allowing wrappers to be -written for very high level languages. +The Standard Airline IT (STDAIR) library is a collection of routines +for travel market simulation. The routines are written from scratch by +the StdAir team in C++, and present a modern Applications Programming +Interface (API) for C/C++ programmers, allowing wrappers to be written +for very high level languages. .PP The library covers the following areas, .TP @@ -18,5 +18,4 @@ .fi .PP Please report any bugs to -.B https://sourceforge.net/tracker/?group_id=267760&atid=1139455 - +.B https://sourceforge.net/apps/trac/stdair/report This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-20 23:43:35
|
Revision: 225 http://stdair.svn.sourceforge.net/stdair/?rev=225&view=rev Author: denis_arnaud Date: 2010-07-20 23:43:28 +0000 (Tue, 20 Jul 2010) Log Message: ----------- [Doc] Prefixed the source file variables with stdair. Modified Paths: -------------- trunk/stdair/doc/local/stdair_header.html Modified: trunk/stdair/doc/local/stdair_header.html =================================================================== --- trunk/stdair/doc/local/stdair_header.html 2010-07-20 23:03:54 UTC (rev 224) +++ trunk/stdair/doc/local/stdair_header.html 2010-07-20 23:43:28 UTC (rev 225) @@ -13,7 +13,7 @@ <a href="http://stdair.sourceforge.net"><img width="150" height="40" src="stdair_logo.png" alt="StdAir Logo" style="float: left; border: 0;"></a> - <a href="http://www.sourceforge.net/projects/stdair"><img width="150" + <a href="http://sourceforge.net/projects/stdair/"><img width="150" height="40" src="sfx_logo.png" alt="Sourceforge Logo" style="float: right; border: 0;"></a> </div> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-20 23:04:00
|
Revision: 224 http://stdair.svn.sourceforge.net/stdair/?rev=224&view=rev Author: denis_arnaud Date: 2010-07-20 23:03:54 +0000 (Tue, 20 Jul 2010) Log Message: ----------- [Doc] Prefixed the source file variables with stdair. Modified Paths: -------------- trunk/stdair/doc/Makefile.am trunk/stdair/stdair/core/Makefile.am trunk/stdair/stdair/core/sources.mk Modified: trunk/stdair/doc/Makefile.am =================================================================== --- trunk/stdair/doc/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) +++ trunk/stdair/doc/Makefile.am 2010-07-20 23:03:54 UTC (rev 224) @@ -27,6 +27,7 @@ html/index.html: doxygen_html.cfg \ $(doc_local_sources) $(html_local_sources) \ $(doc_tutorial_sources) $(cpp_tutorial_sources) \ + $(stdair_service_h_sources) $(stdair_service_cc_sources) \ $(stdair_bas_h_sources) $(stdair_bas_cc_sources) \ $(stdair_bom_h_sources) $(stdair_bom_cc_sources) \ $(stdair_fac_h_sources) $(stdair_fac_cc_sources) \ Modified: trunk/stdair/stdair/core/Makefile.am =================================================================== --- trunk/stdair/stdair/core/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) +++ trunk/stdair/stdair/core/Makefile.am 2010-07-20 23:03:54 UTC (rev 224) @@ -12,7 +12,7 @@ # Library lib_LTLIBRARIES = libstdair.la -libstdair_la_SOURCES = $(service_h_sources) $(service_cc_sources) +libstdair_la_SOURCES = $(stdair_service_h_sources) $(stdair_service_cc_sources) libstdair_la_LIBADD = \ $(top_builddir)/stdair/basic/libstdairbas.la \ $(top_builddir)/stdair/bom/libstdairbom.la \ Modified: trunk/stdair/stdair/core/sources.mk =================================================================== --- trunk/stdair/stdair/core/sources.mk 2010-07-20 22:51:33 UTC (rev 223) +++ trunk/stdair/stdair/core/sources.mk 2010-07-20 23:03:54 UTC (rev 224) @@ -1,3 +1,4 @@ -service_h_sources = $(top_srcdir)/stdair/STDAIR_Types.hpp \ +stdair_service_h_sources = $(top_srcdir)/stdair/STDAIR_Types.hpp \ $(top_srcdir)/stdair/STDAIR_Service.hpp -service_cc_sources = +stdair_service_cc_sources = + This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <den...@us...> - 2010-07-20 22:51:39
|
Revision: 223 http://stdair.svn.sourceforge.net/stdair/?rev=223&view=rev Author: denis_arnaud Date: 2010-07-20 22:51:33 +0000 (Tue, 20 Jul 2010) Log Message: ----------- [Doc] Prefixed the source file variables with stdair. Modified Paths: -------------- trunk/stdair/Makefile.am trunk/stdair/doc/Makefile.am trunk/stdair/stdair/basic/Makefile.am trunk/stdair/stdair/basic/sources.mk trunk/stdair/stdair/batches/Makefile.am trunk/stdair/stdair/batches/sources.mk trunk/stdair/stdair/bom/Makefile.am trunk/stdair/stdair/bom/sources.mk trunk/stdair/stdair/command/Makefile.am trunk/stdair/stdair/command/sources.mk trunk/stdair/stdair/core/Makefile.am trunk/stdair/stdair/dbadaptor/Makefile.am trunk/stdair/stdair/dbadaptor/sources.mk trunk/stdair/stdair/factory/Makefile.am trunk/stdair/stdair/factory/sources.mk trunk/stdair/stdair/service/Makefile.am trunk/stdair/stdair/service/sources.mk Modified: trunk/stdair/Makefile.am =================================================================== --- trunk/stdair/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,4 +1,4 @@ -## top directory +## stdair top directory include $(top_srcdir)/Makefile.common ACLOCAL_AMFLAGS = -I config @@ -52,7 +52,7 @@ $(MAKE) dist distdir=@PACKAGE_TARNAME@-`date +"%Y%m%d"` snapshot-html: - $(MAKE) -C doc dist-html html_tarname=@PACKAGE_TARNAME@-html-doc-`date +"%Y%m%d"` + $(MAKE) -C doc dist-html html_tarname=@PACKAGE_TARNAME@-doc-`date +"%Y%m%d"` upload: upload-src upload-html @@ -61,6 +61,6 @@ @PACKAGE_TARNAME@-@VERSION@.tar.bz2 upload-html: dist-html - @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-html-doc-@VERSION@.tar.gz \ - @PACKAGE_TARNAME@-html-doc-@VERSION@.tar.bz2 + @UPLOAD_COMMAND@ @PACKAGE_TARNAME@-doc-@VERSION@.tar.gz \ + @PACKAGE_TARNAME@-doc-@VERSION@.tar.bz2 Modified: trunk/stdair/doc/Makefile.am =================================================================== --- trunk/stdair/doc/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/doc/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,18 +1,20 @@ +# stdair doc directory include $(top_srcdir)/doc/local/sources.mk include $(top_srcdir)/doc/tutorial/sources.mk include $(top_srcdir)/doc/tutorial/src/sources.mk -include $(top_srcdir)/@PACKAGE@/basic/sources.mk -include $(top_srcdir)/@PACKAGE@/bom/sources.mk -include $(top_srcdir)/@PACKAGE@/factory/sources.mk -#include $(top_srcdir)/@PACKAGE@/command/sources.mk -#include $(top_srcdir)/@PACKAGE@/service/sources.mk -include $(top_srcdir)/@PACKAGE@/core/sources.mk +include $(top_srcdir)/stdair/basic/sources.mk +include $(top_srcdir)/stdair/bom/sources.mk +include $(top_srcdir)/stdair/factory/sources.mk +include $(top_srcdir)/stdair/dbadaptor/sources.mk +include $(top_srcdir)/stdair/command/sources.mk +include $(top_srcdir)/stdair/service/sources.mk +include $(top_srcdir)/stdair/core/sources.mk SUBDIRS = images tutorial local docdir = @docdir@ -html_tarname = @PACKAGE_TARNAME@-html-doc-@PACKAGE_VERSION@ +html_tarname = @PACKAGE_TARNAME@-doc-@PACKAGE_VERSION@ noinst_DATA = sourceforge/howto_release_stdair.html.in EXTRA_DIST = $(noinst_DATA) @@ -25,13 +27,12 @@ html/index.html: doxygen_html.cfg \ $(doc_local_sources) $(html_local_sources) \ $(doc_tutorial_sources) $(cpp_tutorial_sources) \ - $(service_h_sources) $(service_cc_sources) \ - $(bas_h_sources) $(bas_cc_sources) \ - $(bom_h_sources) $(bom_cc_sources) \ - $(fac_h_sources) $(fac_cc_sources) \ - $(dba_h_sources) $(dba_cc_sources) \ - $(cmd_h_sources) $(cmd_cc_sources) \ - $(svc_h_sources) $(svc_cc_sources) + $(stdair_bas_h_sources) $(stdair_bas_cc_sources) \ + $(stdair_bom_h_sources) $(stdair_bom_cc_sources) \ + $(stdair_fac_h_sources) $(stdair_fac_cc_sources) \ + $(stdair_dba_h_sources) $(stdair_dba_cc_sources) \ + $(stdair_cmd_h_sources) $(stdair_cmd_cc_sources) \ + $(stdair_svc_h_sources) $(stdair_svc_cc_sources) doxygen $<; \ if test -d html; then \ cp $(srcdir)/images/stdair_logo.png html; \ Modified: trunk/stdair/stdair/basic/Makefile.am =================================================================== --- trunk/stdair/stdair/basic/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/basic/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,13 +1,13 @@ -## basic sub-directory +## stdair/basic sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk # -noinst_LTLIBRARIES= libbas.la +noinst_LTLIBRARIES= libstdairbas.la -libbas_la_SOURCES = $(bas_h_sources) $(bas_cc_sources) -libbas_la_CXXFLAGS = $(BOOST_CFLAGS) -libbas_la_LDFLAGS = +libstdairbas_la_SOURCES = $(stdair_bas_h_sources) $(stdair_bas_cc_sources) +libstdairbas_la_CXXFLAGS = $(BOOST_CFLAGS) +libstdairbas_la_LDFLAGS = # Header files Modified: trunk/stdair/stdair/basic/sources.mk =================================================================== --- trunk/stdair/stdair/basic/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/basic/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,4 +1,4 @@ -bas_h_sources = \ +stdair_bas_h_sources = \ $(top_srcdir)/stdair/basic/BasTypes.hpp \ $(top_srcdir)/stdair/basic/BasConst_General.hpp \ $(top_srcdir)/stdair/basic/BasConst_Request.hpp \ @@ -24,7 +24,7 @@ $(top_srcdir)/stdair/basic/RandomGeneration.hpp \ $(top_srcdir)/stdair/basic/RandomGenerationContext.hpp \ $(top_srcdir)/stdair/basic/DictionaryManager.hpp -bas_cc_sources = \ +stdair_bas_cc_sources = \ $(top_srcdir)/stdair/basic/BasConst.cpp \ $(top_srcdir)/stdair/basic/BasChronometer.cpp \ $(top_srcdir)/stdair/basic/BasFileMgr.cpp \ Modified: trunk/stdair/stdair/batches/Makefile.am =================================================================== --- trunk/stdair/stdair/batches/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/batches/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,4 +1,4 @@ -# batches +# stdair/batches include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk @@ -10,9 +10,8 @@ # Binaries (batches) bin_PROGRAMS = stdair -stdair_SOURCES = $(batches_h_sources) $(batches_cc_sources) +stdair_SOURCES = $(stdair_batches_h_sources) $(stdair_batches_cc_sources) stdair_CXXFLAGS = $(BOOST_CFLAGS) stdair_LDADD = stdair_LDFLAGS = $(BOOST_PROGRAM_OPTIONS_LIB) \ - $(top_builddir)/stdair/core/libstdair.la \ $(top_builddir)/stdair/core/libstdair.la Modified: trunk/stdair/stdair/batches/sources.mk =================================================================== --- trunk/stdair/stdair/batches/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/batches/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,2 +1,3 @@ -batches_h_sources = -batches_cc_sources = $(top_srcdir)/stdair/batches/stdair.cpp +# +stdair_batches_h_sources = +stdair_batches_cc_sources = $(top_srcdir)/stdair/batches/stdair.cpp Modified: trunk/stdair/stdair/bom/Makefile.am =================================================================== --- trunk/stdair/stdair/bom/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/bom/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,12 +1,13 @@ -## bom sub-directory +## stdair/bom sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk -noinst_LTLIBRARIES= libbom.la +# +noinst_LTLIBRARIES= libstdairbom.la -libbom_la_SOURCES = $(bom_h_sources) $(bom_cc_sources) -libbom_la_CXXFLAGS = $(BOOST_CFLAGS) -libbom_la_LDFLAGS = +libstdairbom_la_SOURCES = $(stdair_bom_h_sources) $(stdair_bom_cc_sources) +libstdairbom_la_CXXFLAGS = $(BOOST_CFLAGS) +libstdairbom_la_LDFLAGS = # Header files Modified: trunk/stdair/stdair/bom/sources.mk =================================================================== --- trunk/stdair/stdair/bom/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/bom/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,4 +1,4 @@ -bom_h_sources = \ +stdair_bom_h_sources = \ $(top_srcdir)/stdair/bom/BomSource.hpp \ $(top_srcdir)/stdair/bom/BomTypes.hpp \ $(top_srcdir)/stdair/bom/BomStructure.hpp \ @@ -91,7 +91,7 @@ $(top_srcdir)/stdair/bom/AirlineStruct.hpp \ $(top_srcdir)/stdair/bom/EventStruct.hpp \ $(top_srcdir)/stdair/bom/EventQueue.hpp -bom_cc_sources = \ +stdair_bom_cc_sources = \ $(top_srcdir)/stdair/bom/BomManager.cpp \ $(top_srcdir)/stdair/bom/BomRootKey.cpp \ $(top_srcdir)/stdair/bom/YieldStoreKey.cpp \ Modified: trunk/stdair/stdair/command/Makefile.am =================================================================== --- trunk/stdair/stdair/command/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/command/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,14 +1,14 @@ -## command sub-directory +## stdair/command sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk # -noinst_LTLIBRARIES = libcmd.la +noinst_LTLIBRARIES = libstdaircmd.la -libcmd_la_SOURCES = $(cmd_h_sources) $(cmd_cc_sources) -libcmd_la_CXXFLAGS = $(BOOST_CFLAGS) $(SOCI_CFLAGS) -libcmd_la_LIBADD = -libcmd_la_LDFLAGS = $(BOOST_LIBS) $(SOCI_LIBS) +libstdaircmd_la_SOURCES = $(stdair_cmd_h_sources) $(stdair_cmd_cc_sources) +libstdaircmd_la_CXXFLAGS = $(BOOST_CFLAGS) $(SOCI_CFLAGS) +libstdaircmd_la_LIBADD = +libstdaircmd_la_LDFLAGS = $(BOOST_LIBS) $(SOCI_LIBS) # Header files Modified: trunk/stdair/stdair/command/sources.mk =================================================================== --- trunk/stdair/stdair/command/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/command/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,8 +1,8 @@ -cmd_h_sources = \ +stdair_cmd_h_sources = \ $(top_srcdir)/stdair/command/CmdAbstract.hpp \ $(top_srcdir)/stdair/command/CmdBomManager.hpp \ $(top_srcdir)/stdair/command/DBManagerForAirlines.hpp -cmd_cc_sources = \ +stdair_cmd_cc_sources = \ $(top_srcdir)/stdair/command/CmdAbstract.cpp \ $(top_srcdir)/stdair/command/CmdBomManager.cpp \ $(top_srcdir)/stdair/command/DBManagerForAirlines.cpp Modified: trunk/stdair/stdair/core/Makefile.am =================================================================== --- trunk/stdair/stdair/core/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/core/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,4 +1,4 @@ -# core +# stdair/core include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk @@ -14,12 +14,12 @@ libstdair_la_SOURCES = $(service_h_sources) $(service_cc_sources) libstdair_la_LIBADD = \ - $(top_builddir)/stdair/basic/libbas.la \ - $(top_builddir)/stdair/bom/libbom.la \ - $(top_builddir)/stdair/dbadaptor/libdba.la \ - $(top_builddir)/stdair/factory/libfac.la \ - $(top_builddir)/stdair/command/libcmd.la \ - $(top_builddir)/stdair/service/libsvc.la + $(top_builddir)/stdair/basic/libstdairbas.la \ + $(top_builddir)/stdair/bom/libstdairbom.la \ + $(top_builddir)/stdair/dbadaptor/libstdairdba.la \ + $(top_builddir)/stdair/factory/libstdairfac.la \ + $(top_builddir)/stdair/command/libstdaircmd.la \ + $(top_builddir)/stdair/service/libstdairsvc.la libstdair_la_LDFLAGS = \ $(BOOST_DATE_TIME_LIB) $(BOOST_PROGRAM_OPTIONS_LIB) \ $(BOOST_FILESYSTEM_LIB) $(SOCI_LIBS) \ Modified: trunk/stdair/stdair/dbadaptor/Makefile.am =================================================================== --- trunk/stdair/stdair/dbadaptor/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/dbadaptor/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,14 +1,14 @@ -## dbadaptor sub-directory +## stdair/dbadaptor sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk # -noinst_LTLIBRARIES= libdba.la +noinst_LTLIBRARIES= libstdairdba.la -libdba_la_SOURCES= $(dba_h_sources) $(dba_cc_sources) -libdba_la_CXXFLAGS = $(SOCI_CFLAGS) -libdba_la_LIBADD = -libdba_la_LDFLAGS = $(SOCI_LIBS) +libstdairdba_la_SOURCES= $(stdair_dba_h_sources) $(stdair_dba_cc_sources) +libstdairdba_la_CXXFLAGS = $(SOCI_CFLAGS) +libstdairdba_la_LIBADD = +libstdairdba_la_LDFLAGS = $(SOCI_LIBS) # Header files Modified: trunk/stdair/stdair/dbadaptor/sources.mk =================================================================== --- trunk/stdair/stdair/dbadaptor/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/dbadaptor/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,6 +1,6 @@ -dba_h_sources = \ +stdair_dba_h_sources = \ $(top_srcdir)/stdair/dbadaptor/DbaAbstract.hpp \ $(top_srcdir)/stdair/dbadaptor/DbaAirline.hpp -dba_cc_sources = \ +stdair_dba_cc_sources = \ $(top_srcdir)/stdair/dbadaptor/DbaAbstract.cpp \ $(top_srcdir)/stdair/dbadaptor/DbaAirline.cpp Modified: trunk/stdair/stdair/factory/Makefile.am =================================================================== --- trunk/stdair/stdair/factory/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/factory/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,11 +1,12 @@ -## factory sub-directory +## stdair/factory sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk -noinst_LTLIBRARIES= libfac.la +# +noinst_LTLIBRARIES = libstdairfac.la -libfac_la_SOURCES= $(fac_h_sources) $(fac_cc_sources) -libfac_la_CXXFLAGS = +libstdairfac_la_SOURCES = $(stdair_fac_h_sources) $(stdair_fac_cc_sources) +libstdairfac_la_CXXFLAGS = # Header files Modified: trunk/stdair/stdair/factory/sources.mk =================================================================== --- trunk/stdair/stdair/factory/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/factory/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,8 +1,8 @@ -fac_h_sources = \ +stdair_fac_h_sources = \ $(top_srcdir)/stdair/factory/FacSupervisor.hpp \ $(top_srcdir)/stdair/factory/FacBomStructure.hpp \ $(top_srcdir)/stdair/factory/FacBomContent.hpp -fac_cc_sources = \ +stdair_fac_cc_sources = \ $(top_srcdir)/stdair/factory/FacSupervisor.cpp \ $(top_srcdir)/stdair/factory/FacBomStructure.cpp \ $(top_srcdir)/stdair/factory/FacBomContent.cpp Modified: trunk/stdair/stdair/service/Makefile.am =================================================================== --- trunk/stdair/stdair/service/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/service/Makefile.am 2010-07-20 22:51:33 UTC (rev 223) @@ -1,14 +1,15 @@ -## service sub-directory +## stdair/service sub-directory include $(top_srcdir)/Makefile.common include $(srcdir)/sources.mk # -noinst_LTLIBRARIES= libsvc.la +noinst_LTLIBRARIES= libstdairsvc.la -libsvc_la_SOURCES= $(svc_h_sources) $(svc_cc_sources) -libsvc_la_CXXFLAGS = $(SOCI_CFLAGS) $(MYSQL_CFLAGS) -libsvc_la_LDFLAGS = $(SOCI_LIBS) $(MYSQL_LIBS) +libstdairsvc_la_SOURCES = $(stdair_svc_h_sources) $(stdair_svc_cc_sources) +libstdairsvc_la_CXXFLAGS = $(SOCI_CFLAGS) $(MYSQL_CFLAGS) +libstdairsvc_la_LDFLAGS = $(SOCI_LIBS) $(MYSQL_LIBS) + # Header files pkgincludedir = $(includedir)/stdair/service pkginclude_HEADERS = $(svc_h_sources) Modified: trunk/stdair/stdair/service/sources.mk =================================================================== --- trunk/stdair/stdair/service/sources.mk 2010-07-13 14:13:48 UTC (rev 222) +++ trunk/stdair/stdair/service/sources.mk 2010-07-20 22:51:33 UTC (rev 223) @@ -1,7 +1,7 @@ -svc_h_sources = \ +stdair_svc_h_sources = \ $(top_srcdir)/stdair/service/Logger.hpp \ $(top_srcdir)/stdair/service/DBSessionManager.hpp -svc_cc_sources = \ +stdair_svc_cc_sources = \ $(top_srcdir)/stdair/service/Logger.cpp \ $(top_srcdir)/stdair/service/DBSessionManager.cpp \ $(top_srcdir)/stdair/service/STDAIR_Service.cpp This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <sng...@us...> - 2010-07-13 14:13:55
|
Revision: 222 http://stdair.svn.sourceforge.net/stdair/?rev=222&view=rev Author: snguyenkim Date: 2010-07-13 14:13:48 +0000 (Tue, 13 Jul 2010) Log Message: ----------- [RPM Packaging] Generated first (rpmlint-) valid RPM. Modified Paths: -------------- trunk/stdair/ChangeLog trunk/stdair/Makefile.am trunk/stdair/NEWS trunk/stdair/configure.ac trunk/stdair/stdair/bom/sources.mk trunk/stdair/stdair.spec.in Added Paths: ----------- trunk/stdair/ABOUT-NLS trunk/stdair/TODO trunk/stdair/man/Makefile.am trunk/stdair/man/stdair-config.1 trunk/stdair/man/stdair.3 Property Changed: ---------------- trunk/stdair/man/ Added: trunk/stdair/ABOUT-NLS =================================================================== --- trunk/stdair/ABOUT-NLS (rev 0) +++ trunk/stdair/ABOUT-NLS 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,768 @@ +Notes on the Free Translation Project +************************************* + +Free software is going international! The Free Translation Project is +a way to get maintainers of free software, translators, and users all +together, so that will gradually become able to speak many languages. +A few packages already provide translations for their messages. + + If you found this `ABOUT-NLS' file inside a distribution, you may +assume that the distributed package does use GNU `gettext' internally, +itself available at your nearest GNU archive site. But you do _not_ +need to install GNU `gettext' prior to configuring, installing or using +this package with messages translated. + + Installers will find here some useful hints. These notes also +explain how users should proceed for getting the programs to use the +available translations. They tell how people wanting to contribute and +work at translations should contact the appropriate team. + + When reporting bugs in the `intl/' directory or bugs which may be +related to internationalization, you should tell about the version of +`gettext' which is used. The information can be found in the +`intl/VERSION' file, in internationalized packages. + +Quick configuration advice +========================== + +If you want to exploit the full power of internationalization, you +should configure it using + + ./configure --with-included-gettext + +to force usage of internationalizing routines provided within this +package, despite the existence of internationalizing capabilities in the +operating system where this package is being installed. So far, only +the `gettext' implementation in the GNU C library version 2 provides as +many features (such as locale alias, message inheritance, automatic +charset conversion or plural form handling) as the implementation here. +It is also not possible to offer this additional functionality on top +of a `catgets' implementation. Future versions of GNU `gettext' will +very likely convey even more functionality. So it might be a good idea +to change to GNU `gettext' as soon as possible. + + So you need _not_ provide this option if you are using GNU libc 2 or +you have installed a recent copy of the GNU gettext package with the +included `libintl'. + +INSTALL Matters +=============== + +Some packages are "localizable" when properly installed; the programs +they contain can be made to speak your own native language. Most such +packages use GNU `gettext'. Other packages have their own ways to +internationalization, predating GNU `gettext'. + + By default, this package will be installed to allow translation of +messages. It will automatically detect whether the system already +provides the GNU `gettext' functions. If not, the GNU `gettext' own +library will be used. This library is wholly contained within this +package, usually in the `intl/' subdirectory, so prior installation of +the GNU `gettext' package is _not_ required. Installers may use +special options at configuration time for changing the default +behaviour. The commands: + + ./configure --with-included-gettext + ./configure --disable-nls + +will respectively bypass any pre-existing `gettext' to use the +internationalizing routines provided within this package, or else, +_totally_ disable translation of messages. + + When you already have GNU `gettext' installed on your system and run +configure without an option for your new package, `configure' will +probably detect the previously built and installed `libintl.a' file and +will decide to use this. This might be not what is desirable. You +should use the more recent version of the GNU `gettext' library. I.e. +if the file `intl/VERSION' shows that the library which comes with this +package is more recent, you should use + + ./configure --with-included-gettext + +to prevent auto-detection. + + The configuration process will not test for the `catgets' function +and therefore it will not be used. The reason is that even an +emulation of `gettext' on top of `catgets' could not provide all the +extensions of the GNU `gettext' library. + + Internationalized packages have usually many `po/LL.po' files, where +LL gives an ISO 639 two-letter code identifying the language. Unless +translations have been forbidden at `configure' time by using the +`--disable-nls' switch, all available translations are installed +together with the package. However, the environment variable `LINGUAS' +may be set, prior to configuration, to limit the installed set. +`LINGUAS' should then contain a space separated list of two-letter +codes, stating which languages are allowed. + +Using This Package +================== + +As a user, if your language has been installed for this package, you +only have to set the `LANG' environment variable to the appropriate +`LL_CC' combination. Here `LL' is an ISO 639 two-letter language code, +and `CC' is an ISO 3166 two-letter country code. For example, let's +suppose that you speak German and live in Germany. At the shell +prompt, merely execute `setenv LANG de_DE' (in `csh'), +`export LANG; LANG=de_DE' (in `sh') or `export LANG=de_DE' (in `bash'). +This can be done from your `.login' or `.profile' file, once and for +all. + + You might think that the country code specification is redundant. +But in fact, some languages have dialects in different countries. For +example, `de_AT' is used for Austria, and `pt_BR' for Brazil. The +country code serves to distinguish the dialects. + + The locale naming convention of `LL_CC', with `LL' denoting the +language and `CC' denoting the country, is the one use on systems based +on GNU libc. On other systems, some variations of this scheme are +used, such as `LL' or `LL_CC.ENCODING'. You can get the list of +locales supported by your system for your country by running the command +`locale -a | grep '^LL''. + + Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +`LANGUAGE'. GNU `gettext' gives preference to `LANGUAGE' over `LANG' +for the purpose of message handling, but you still need to have `LANG' +set to the primary language; this is required by other parts of the +system libraries. For example, some Swedish users who would rather +read translations in German than English for when Swedish is not +available, set `LANGUAGE' to `sv:de' while leaving `LANG' to `sv_SE'. + + Special advice for Norwegian users: The language code for Norwegian +bokma*l changed from `no' to `nb' recently (in 2003). During the +transition period, while some message catalogs for this language are +installed under `nb' and some older ones under `no', it's recommended +for Norwegian users to set `LANGUAGE' to `nb:no' so that both newer and +older translations are used. + + In the `LANGUAGE' environment variable, but not in the `LANG' +environment variable, `LL_CC' combinations can be abbreviated as `LL' +to denote the language's main dialect. For example, `de' is equivalent +to `de_DE' (German as spoken in Germany), and `pt' to `pt_PT' +(Portuguese as spoken in Portugal) in this context. + +Translating Teams +================= + +For the Free Translation Project to be a success, we need interested +people who like their own language and write it well, and who are also +able to synergize with other translators speaking the same language. +Each translation team has its own mailing list. The up-to-date list of +teams can be found at the Free Translation Project's homepage, +`http://www.iro.umontreal.ca/contrib/po/HTML/', in the "National teams" +area. + + If you'd like to volunteer to _work_ at translating messages, you +should become a member of the translating team for your own language. +The subscribing address is _not_ the same as the list itself, it has +`-request' appended. For example, speakers of Swedish can send a +message to `sv-...@li...', having this message body: + + subscribe + + Keep in mind that team members are expected to participate +_actively_ in translations, or at solving translational difficulties, +rather than merely lurking around. If your team does not exist yet and +you want to start one, or if you are unsure about what to do or how to +get started, please write to `tra...@ir...' to reach the +coordinator for all translator teams. + + The English team is special. It works at improving and uniformizing +the terminology in use. Proven linguistic skill are praised more than +programming skill, here. + +Available Packages +================== + +Languages are not equally supported in all packages. The following +matrix shows the current state of internationalization, as of January +2004. The matrix shows, in regard of each package, for which languages +PO files have been submitted to translation coordination, with a +translation percentage of at least 50%. + + Ready PO files af am ar az be bg bs ca cs da de el en en_GB eo es + +----------------------------------------------------+ + a2ps | [] [] [] [] | + aegis | () | + ant-phone | () | + anubis | | + ap-utils | | + aspell | [] | + bash | [] [] [] [] | + batchelor | | + bfd | [] [] | + binutils | [] [] | + bison | [] [] [] | + bluez-pin | [] [] [] | + clisp | | + clisp | [] [] [] | + console-tools | [] [] | + coreutils | [] [] [] [] | + cpio | [] [] [] | + darkstat | [] () [] | + diffutils | [] [] [] [] [] [] [] | + e2fsprogs | [] [] [] | + enscript | [] [] [] [] | + error | [] [] [] [] [] | + fetchmail | [] () [] [] [] [] | + fileutils | [] [] [] | + findutils | [] [] [] [] [] [] [] | + flex | [] [] [] [] | + fslint | | + gas | [] | + gawk | [] [] [] [] | + gbiff | [] | + gcal | [] | + gcc | [] [] | + gettext | [] [] [] [] [] | + gettext-examples | [] [] [] [] | + gettext-runtime | [] [] [] [] [] | + gettext-tools | [] [] [] | + gimp-print | [] [] [] [] [] | + gliv | | + glunarclock | [] [] | + gnubiff | [] | + gnucash | [] () [] [] | + gnucash-glossary | [] () [] | + gnupg | [] () [] [] [] [] | + gpe-aerial | [] | + gpe-beam | [] [] | + gpe-calendar | [] [] | + gpe-clock | [] [] | + gpe-conf | [] [] | + gpe-contacts | [] [] | + gpe-edit | [] | + gpe-go | [] | + gpe-login | [] [] | + gpe-ownerinfo | [] [] | + gpe-sketchbook | [] [] | + gpe-su | [] [] | + gpe-taskmanager | [] [] | + gpe-timesheet | [] | + gpe-today | [] [] | + gpe-todo | [] [] | + gphoto2 | [] [] [] [] | + gprof | [] [] [] | + gpsdrive | () () () | + gramadoir | [] | + grep | [] [] [] [] [] [] | + gretl | [] | + gtick | [] () | + hello | [] [] [] [] [] [] | + id-utils | [] [] | + indent | [] [] [] [] | + iso_3166 | [] [] [] [] [] [] [] [] [] [] | + iso_3166_1 | [] [] [] [] [] [] | + iso_3166_2 | | + iso_3166_3 | [] | + iso_4217 | [] [] [] [] | + iso_639 | | + jpilot | [] [] [] | + jtag | | + jwhois | [] | + kbd | [] [] [] [] [] | + latrine | () | + ld | [] [] | + libc | [] [] [] [] [] [] | + libgpewidget | [] [] | + libiconv | [] [] [] [] [] | + lifelines | [] () | + lilypond | [] | + lingoteach | | + lingoteach_lessons | () () | + lynx | [] [] [] [] | + m4 | [] [] [] [] | + mailutils | [] [] | + make | [] [] [] | + man-db | [] () [] [] () | + minicom | [] [] [] | + mysecretdiary | [] [] [] | + nano | [] () [] [] [] | + nano_1_0 | [] () [] [] [] | + opcodes | [] | + parted | [] [] [] [] [] | + ptx | [] [] [] [] [] | + python | | + radius | [] | + recode | [] [] [] [] [] [] [] | + rpm | [] [] | + screem | | + scrollkeeper | [] [] [] [] [] [] | + sed | [] [] [] [] [] [] | + sh-utils | [] [] [] | + shared-mime-info | | + sharutils | [] [] [] [] [] [] | + silky | () | + skencil | [] () [] | + sketch | [] () [] | + soundtracker | [] [] [] | + sp | [] | + tar | [] [] [] [] | + texinfo | [] [] [] | + textutils | [] [] [] [] | + tin | () () | + tp-robot | | + tuxpaint | [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | | + util-linux | [] [] [] [] [] | + vorbis-tools | [] [] [] [] | + wastesedge | () | + wdiff | [] [] [] [] | + wget | [] [] [] [] [] [] | + xchat | [] [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] | + +----------------------------------------------------+ + af am ar az be bg bs ca cs da de el en en_GB eo es + 4 0 0 1 9 4 1 40 41 60 78 17 1 5 13 68 + + et eu fa fi fr ga gl he hr hu id is it ja ko lg + +-------------------------------------------------+ + a2ps | [] [] [] () () | + aegis | | + ant-phone | [] | + anubis | [] | + ap-utils | [] | + aspell | [] [] | + bash | [] [] | + batchelor | [] [] | + bfd | [] | + binutils | [] [] | + bison | [] [] [] [] | + bluez-pin | [] [] [] [] [] | + clisp | | + clisp | [] | + console-tools | | + coreutils | [] [] [] [] [] [] | + cpio | [] [] [] [] | + darkstat | () [] [] [] | + diffutils | [] [] [] [] [] [] [] | + e2fsprogs | | + enscript | [] [] | + error | [] [] [] [] | + fetchmail | [] | + fileutils | [] [] [] [] [] [] | + findutils | [] [] [] [] [] [] [] [] [] [] [] | + flex | [] [] [] | + fslint | [] | + gas | [] | + gawk | [] [] [] | + gbiff | [] | + gcal | [] | + gcc | [] | + gettext | [] [] [] | + gettext-examples | [] [] | + gettext-runtime | [] [] [] [] [] | + gettext-tools | [] [] [] | + gimp-print | [] [] | + gliv | () | + glunarclock | [] [] [] [] | + gnubiff | [] | + gnucash | () [] | + gnucash-glossary | [] | + gnupg | [] [] [] [] [] [] [] | + gpe-aerial | [] | + gpe-beam | [] | + gpe-calendar | [] [] [] | + gpe-clock | [] | + gpe-conf | [] | + gpe-contacts | [] [] | + gpe-edit | [] [] | + gpe-go | [] | + gpe-login | [] [] | + gpe-ownerinfo | [] [] [] | + gpe-sketchbook | [] | + gpe-su | [] | + gpe-taskmanager | [] | + gpe-timesheet | [] [] [] | + gpe-today | [] [] | + gpe-todo | [] [] | + gphoto2 | [] [] [] | + gprof | [] [] | + gpsdrive | () () () | + gramadoir | [] [] | + grep | [] [] [] [] [] [] [] [] [] [] [] | + gretl | [] [] | + gtick | [] [] [] | + hello | [] [] [] [] [] [] [] [] [] [] [] [] [] | + id-utils | [] [] [] [] | + indent | [] [] [] [] [] [] [] [] [] | + iso_3166 | [] [] [] [] [] [] [] | + iso_3166_1 | [] [] [] [] [] | + iso_3166_2 | | + iso_3166_3 | | + iso_4217 | [] [] [] [] [] [] | + iso_639 | | + jpilot | [] () | + jtag | [] | + jwhois | [] [] [] [] | + kbd | [] | + latrine | [] | + ld | [] | + libc | [] [] [] [] [] [] | + libgpewidget | [] [] [] [] | + libiconv | [] [] [] [] [] [] [] [] [] | + lifelines | () | + lilypond | [] | + lingoteach | [] [] | + lingoteach_lessons | | + lynx | [] [] [] [] | + m4 | [] [] [] [] | + mailutils | | + make | [] [] [] [] [] [] | + man-db | () () | + minicom | [] [] [] [] | + mysecretdiary | [] [] | + nano | [] [] [] [] | + nano_1_0 | [] [] [] [] | + opcodes | [] | + parted | [] [] [] | + ptx | [] [] [] [] [] [] [] | + python | | + radius | [] | + recode | [] [] [] [] [] [] | + rpm | [] [] | + screem | | + scrollkeeper | [] | + sed | [] [] [] [] [] [] [] [] [] | + sh-utils | [] [] [] [] [] [] [] | + shared-mime-info | [] [] [] | + sharutils | [] [] [] [] [] | + silky | () [] () () | + skencil | [] | + sketch | [] | + soundtracker | [] [] | + sp | [] () | + tar | [] [] [] [] [] [] [] [] [] | + texinfo | [] [] [] [] | + textutils | [] [] [] [] [] [] | + tin | [] () | + tp-robot | [] | + tuxpaint | [] [] [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | [] [] | + util-linux | [] [] [] [] () [] | + vorbis-tools | [] | + wastesedge | () | + wdiff | [] [] [] [] [] [] | + wget | [] [] [] [] [] [] [] | + xchat | [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] [] | + +-------------------------------------------------+ + et eu fa fi fr ga gl he hr hu id is it ja ko lg + 22 2 1 26 106 28 24 8 10 41 33 1 26 33 12 0 + + lt lv mk mn ms mt nb nl nn no nso pl pt pt_BR ro ru + +-----------------------------------------------------+ + a2ps | [] [] () () [] [] [] | + aegis | () () () | + ant-phone | [] [] | + anubis | [] [] [] [] [] [] | + ap-utils | [] () [] | + aspell | [] | + bash | [] [] [] | + batchelor | [] | + bfd | [] | + binutils | [] | + bison | [] [] [] [] [] | + bluez-pin | [] [] [] | + clisp | | + clisp | [] | + console-tools | [] | + coreutils | [] [] | + cpio | [] [] [] [] [] | + darkstat | [] [] [] [] | + diffutils | [] [] [] [] [] [] | + e2fsprogs | [] | + enscript | [] [] [] [] | + error | [] [] [] | + fetchmail | [] [] () [] | + fileutils | [] [] [] | + findutils | [] [] [] [] [] | + flex | [] [] [] [] | + fslint | [] [] | + gas | | + gawk | [] [] [] | + gbiff | [] [] | + gcal | | + gcc | | + gettext | [] [] [] | + gettext-examples | [] [] [] | + gettext-runtime | [] [] [] [] | + gettext-tools | [] [] | + gimp-print | [] | + gliv | [] [] [] | + glunarclock | [] [] [] [] | + gnubiff | [] | + gnucash | [] [] () [] | + gnucash-glossary | [] [] | + gnupg | [] | + gpe-aerial | [] [] [] [] | + gpe-beam | [] [] [] [] | + gpe-calendar | [] [] [] [] | + gpe-clock | [] [] [] [] | + gpe-conf | [] [] [] [] | + gpe-contacts | [] [] [] [] | + gpe-edit | [] [] [] [] | + gpe-go | [] [] [] | + gpe-login | [] [] [] [] | + gpe-ownerinfo | [] [] [] [] | + gpe-sketchbook | [] [] [] [] | + gpe-su | [] [] [] [] | + gpe-taskmanager | [] [] [] [] | + gpe-timesheet | [] [] [] [] | + gpe-today | [] [] [] [] | + gpe-todo | [] [] [] [] | + gphoto2 | [] | + gprof | [] [] | + gpsdrive | () () [] | + gramadoir | () [] | + grep | [] [] [] [] [] | + gretl | | + gtick | [] [] [] | + hello | [] [] [] [] [] [] [] [] [] [] | + id-utils | [] [] [] [] | + indent | [] [] [] [] | + iso_3166 | [] [] [] | + iso_3166_1 | [] [] | + iso_3166_2 | | + iso_3166_3 | [] | + iso_4217 | [] [] [] [] [] [] [] [] | + iso_639 | [] | + jpilot | () () | + jtag | | + jwhois | [] [] [] [] () | + kbd | [] [] [] | + latrine | [] | + ld | | + libc | [] [] [] [] | + libgpewidget | [] [] [] | + libiconv | [] [] [] [] [] | + lifelines | | + lilypond | | + lingoteach | | + lingoteach_lessons | | + lynx | [] [] [] | + m4 | [] [] [] [] [] | + mailutils | [] [] [] | + make | [] [] [] [] | + man-db | [] | + minicom | [] [] [] [] | + mysecretdiary | [] [] [] | + nano | [] [] [] [] [] | + nano_1_0 | [] [] [] [] [] [] | + opcodes | [] [] | + parted | [] [] [] [] | + ptx | [] [] [] [] [] [] [] [] | + python | | + radius | [] [] | + recode | [] [] [] [] | + rpm | [] [] [] | + screem | | + scrollkeeper | [] [] [] [] [] | + sed | [] [] [] | + sh-utils | [] [] | + shared-mime-info | [] [] | + sharutils | [] [] | + silky | () | + skencil | [] [] | + sketch | [] [] | + soundtracker | | + sp | | + tar | [] [] [] [] [] [] | + texinfo | [] [] [] [] | + textutils | [] [] | + tin | | + tp-robot | [] | + tuxpaint | [] [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | | + util-linux | [] [] [] | + vorbis-tools | [] [] [] | + wastesedge | | + wdiff | [] [] [] [] [] | + wget | [] [] [] | + xchat | [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] [] | + +-----------------------------------------------------+ + lt lv mk mn ms mt nb nl nn no nso pl pt pt_BR ro ru + 1 2 0 3 12 0 10 69 6 7 1 40 26 36 76 63 + + sk sl sr sv ta th tr uk ven vi wa xh zh_CN zh_TW zu + +-----------------------------------------------------+ + a2ps | [] [] [] [] | 16 + aegis | | 0 + ant-phone | | 3 + anubis | [] [] | 9 + ap-utils | () | 3 + aspell | | 4 + bash | | 9 + batchelor | | 3 + bfd | [] [] | 6 + binutils | [] [] [] | 8 + bison | [] [] | 14 + bluez-pin | [] [] [] | 14 + clisp | | 0 + clisp | | 5 + console-tools | | 3 + coreutils | [] [] [] [] | 16 + cpio | [] [] | 14 + darkstat | [] [] [] () () | 12 + diffutils | [] [] [] | 23 + e2fsprogs | [] [] | 6 + enscript | [] [] | 12 + error | [] [] [] | 15 + fetchmail | [] [] | 11 + fileutils | [] [] [] [] [] | 17 + findutils | [] [] [] [] [] [] | 29 + flex | [] [] | 13 + fslint | | 3 + gas | [] | 3 + gawk | [] [] | 12 + gbiff | | 4 + gcal | [] [] | 4 + gcc | [] | 4 + gettext | [] [] [] [] [] | 16 + gettext-examples | [] [] [] [] [] | 14 + gettext-runtime | [] [] [] [] [] [] [] [] | 22 + gettext-tools | [] [] [] [] [] [] | 14 + gimp-print | [] [] | 10 + gliv | | 3 + glunarclock | [] [] [] | 13 + gnubiff | | 3 + gnucash | [] [] | 9 + gnucash-glossary | [] [] [] | 8 + gnupg | [] [] [] [] | 17 + gpe-aerial | [] | 7 + gpe-beam | [] | 8 + gpe-calendar | [] [] [] [] | 13 + gpe-clock | [] [] [] | 10 + gpe-conf | [] [] | 9 + gpe-contacts | [] [] [] | 11 + gpe-edit | [] [] [] [] [] | 12 + gpe-go | | 5 + gpe-login | [] [] [] [] [] | 13 + gpe-ownerinfo | [] [] [] [] | 13 + gpe-sketchbook | [] [] | 9 + gpe-su | [] [] [] | 10 + gpe-taskmanager | [] [] [] | 10 + gpe-timesheet | [] [] [] [] | 12 + gpe-today | [] [] [] [] [] | 13 + gpe-todo | [] [] [] [] | 12 + gphoto2 | [] [] [] | 11 + gprof | [] [] | 9 + gpsdrive | [] [] | 3 + gramadoir | [] | 5 + grep | [] [] [] [] | 26 + gretl | | 3 + gtick | | 7 + hello | [] [] [] [] [] | 34 + id-utils | [] [] | 12 + indent | [] [] [] [] | 21 + iso_3166 | [] [] [] [] [] [] [] | 27 + iso_3166_1 | [] [] [] | 16 + iso_3166_2 | | 0 + iso_3166_3 | | 2 + iso_4217 | [] [] [] [] [] [] | 24 + iso_639 | | 1 + jpilot | [] [] [] [] [] | 9 + jtag | [] | 2 + jwhois | () [] [] | 11 + kbd | [] [] | 11 + latrine | | 2 + ld | [] [] | 5 + libc | [] [] [] [] | 20 + libgpewidget | [] [] [] [] | 13 + libiconv | [] [] [] [] [] [] [] [] | 27 + lifelines | [] | 2 + lilypond | [] | 3 + lingoteach | | 2 + lingoteach_lessons | () | 0 + lynx | [] [] [] | 14 + m4 | [] [] | 15 + mailutils | | 5 + make | [] [] [] | 16 + man-db | [] | 5 + minicom | | 11 + mysecretdiary | [] [] | 10 + nano | [] [] [] [] | 17 + nano_1_0 | [] [] [] | 17 + opcodes | [] [] | 6 + parted | [] [] [] | 15 + ptx | [] [] | 22 + python | | 0 + radius | | 4 + recode | [] [] [] | 20 + rpm | [] [] | 9 + screem | [] [] | 2 + scrollkeeper | [] [] [] | 15 + sed | [] [] [] [] [] [] | 24 + sh-utils | [] [] | 14 + shared-mime-info | [] [] | 7 + sharutils | [] [] [] [] | 17 + silky | () | 3 + skencil | [] | 6 + sketch | [] | 6 + soundtracker | [] [] | 7 + sp | [] | 3 + tar | [] [] [] [] [] | 24 + texinfo | [] [] [] | 14 + textutils | [] [] [] [] | 16 + tin | | 1 + tp-robot | | 2 + tuxpaint | [] [] [] [] [] | 29 + unicode-han-tra... | | 0 + unicode-transla... | | 2 + util-linux | [] [] | 15 + vorbis-tools | | 8 + wastesedge | | 0 + wdiff | [] [] [] | 18 + wget | [] [] [] [] [] [] [] [] | 24 + xchat | [] [] [] [] [] | 15 + xfree86_xkb_xml | [] [] [] [] [] | 11 + xpad | | 5 + +-----------------------------------------------------+ + 63 teams sk sl sr sv ta th tr uk ven vi wa xh zh_CN zh_TW zu + 131 domains 47 19 28 83 0 0 59 13 1 1 11 0 22 22 0 1373 + + Some counters in the preceding matrix are higher than the number of +visible blocks let us expect. This is because a few extra PO files are +used for implementing regional variants of languages, or language +dialects. + + For a PO file in the matrix above to be effective, the package to +which it applies should also have been internationalized and +distributed as such by its maintainer. There might be an observable +lag between the mere existence a PO file and its wide availability in a +distribution. + + If January 2004 seems to be old, you may fetch a more recent copy of +this `ABOUT-NLS' file on most GNU archive sites. The most up-to-date +matrix with full percentage details can be found at +`http://www.iro.umontreal.ca/contrib/po/HTML/matrix.html'. + +Using `gettext' in new packages +=============================== + +If you are writing a freely available program and want to +internationalize it you are welcome to use GNU `gettext' in your +package. Of course you have to respect the GNU Library General Public +License which covers the use of the GNU `gettext' library. This means +in particular that even non-free programs can use `libintl' as a shared +library, whereas only free software can use `libintl' as a static +library or use modified versions of `libintl'. + + Once the sources are changed appropriately and the setup can handle +the use of `gettext' the only thing missing are the translations. The +Free Translation Project is also available for packages which are not +developed inside the GNU project. Therefore the information given above +applies also for every other Free Software Project. Contact +`tra...@ir...' to make the `.pot' files available to +the translation teams. + Modified: trunk/stdair/ChangeLog =================================================================== --- trunk/stdair/ChangeLog 2010-07-13 14:13:09 UTC (rev 221) +++ trunk/stdair/ChangeLog 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,3 @@ +* Fri Jul 9 2010 Anh Quan Nguyen <quannaus at users dot sourceforge dot net> 0.1.0 +- First release. Air-Sched and AirInv are both working on top of it. + Modified: trunk/stdair/Makefile.am =================================================================== --- trunk/stdair/Makefile.am 2010-07-13 14:13:09 UTC (rev 221) +++ trunk/stdair/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) @@ -25,7 +25,7 @@ EXTRA_DIST = # Build in these directories: -SUBDIRS = stdair @PACKAGE@ $(HTML_DOC_DIR) extracppunit $(TEST_DIR) +SUBDIRS = stdair @PACKAGE@ man $(HTML_DOC_DIR) extracppunit $(TEST_DIR) # Configuration helpers Modified: trunk/stdair/NEWS =================================================================== --- trunk/stdair/NEWS 2010-07-13 14:13:09 UTC (rev 221) +++ trunk/stdair/NEWS 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,3 @@ + +2010-07-13: Release of RPMs for Fedora 13. + Added: trunk/stdair/TODO =================================================================== Modified: trunk/stdair/configure.ac =================================================================== --- trunk/stdair/configure.ac 2010-07-13 14:13:09 UTC (rev 221) +++ trunk/stdair/configure.ac 2010-07-13 14:13:48 UTC (rev 222) @@ -222,6 +222,7 @@ stdair/service/Makefile stdair/core/Makefile stdair/batches/Makefile + man/Makefile doc/Makefile doc/images/Makefile doc/tutorial/Makefile Property changes on: trunk/stdair/man ___________________________________________________________________ Added: svn:ignore + .deps .libs Makefile.in Makefile Added: trunk/stdair/man/Makefile.am =================================================================== --- trunk/stdair/man/Makefile.am (rev 0) +++ trunk/stdair/man/Makefile.am 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,4 @@ +# Man pages +man_MANS = stdair.3 stdair-config.1 + +EXTRA_DIST = $(man_MANS) Added: trunk/stdair/man/stdair-config.1 =================================================================== --- trunk/stdair/man/stdair-config.1 (rev 0) +++ trunk/stdair/man/stdair-config.1 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,37 @@ +.TH StdAir 1 "13 July 2010" +.SH NAME +stdair-config - script to get version number and compiler flags of the installed StdAir library +.SH SYNOPSIS +.B stdair-config +[\-\-prefix] [\-\-version] [\-\-libs] [\-\-cflags] +.SH DESCRIPTION +.PP +\fIstdair-config\fP is a tool that is used to configure to determine +the compiler and linker flags that should be used to compile +and link programs that use \fIStdAir\fP. It is also used internally +to the .m4 macros for GNU autoconf that are included with \fIStdAir\fP. +. +.SH OPTIONS +\fIstdair-config\fP accepts the following options: +.TP 8 +.B \-\-version +Print the currently installed version of \fIStdAir\fP on the standard output. +.TP 8 +.B \-\-libs +Print the linker flags that are necessary to link a \fIStdAir\fP program, with cblas +.TP 8 +.B \-\-cflags +Print the compiler flags that are necessary to compile a \fIStdAir\fP program. +.TP 8 +.B \-\-prefix +Show the StdAir installation prefix. +.SH SEE ALSO +.BR boost-config (1) +.SH COPYRIGHT +Copyright \(co 2010 Denis Arnaud + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation. Added: trunk/stdair/man/stdair.3 =================================================================== --- trunk/stdair/man/stdair.3 (rev 0) +++ trunk/stdair/man/stdair.3 2010-07-13 14:13:48 UTC (rev 222) @@ -0,0 +1,22 @@ +.TH StdAir 3 "C++ Standard Airline IT Object Library" "StdAir Team" \" -*- nroff -*- +.SH NAME +stdair - C++ Standard Airline IT Object Library +.SH SYNOPSIS +#include <stdair/...> +.SH DESCRIPTION +The Standard Airline IT (STDAIR) library is a collection of +routines for travel market simulation. The routines are written from +scratch by the StdAir team in C++, and present a modern Applications +Programming Interface (API) for C/C++ programmers, allowing wrappers to be +written for very high level languages. +.PP +The library covers the following areas, +.TP +.nf +.BR +Architecture +.fi +.PP +Please report any bugs to +.B https://sourceforge.net/tracker/?group_id=267760&atid=1139455 + Modified: trunk/stdair/stdair/bom/sources.mk =================================================================== --- trunk/stdair/stdair/bom/sources.mk 2010-07-13 14:13:09 UTC (rev 221) +++ trunk/stdair/stdair/bom/sources.mk 2010-07-13 14:13:48 UTC (rev 222) @@ -45,6 +45,7 @@ $(top_srcdir)/stdair/bom/SegmentPathPeriodTypes.hpp \ $(top_srcdir)/stdair/bom/AirlineFeatureTypes.hpp \ $(top_srcdir)/stdair/bom/TravelSolutionTypes.hpp \ + $(top_srcdir)/stdair/bom/BookingRequestTypes.hpp \ $... [truncated message content] |
From: <sng...@us...> - 2010-07-13 14:13:18
|
Revision: 221 http://stdair.svn.sourceforge.net/stdair/?rev=221&view=rev Author: snguyenkim Date: 2010-07-13 14:13:09 +0000 (Tue, 13 Jul 2010) Log Message: ----------- [RPM Packaging] Generated first (rpmlint-) valid RPM. Modified Paths: -------------- branches/stdair/0.1.0/main/ChangeLog branches/stdair/0.1.0/main/Makefile.am branches/stdair/0.1.0/main/NEWS branches/stdair/0.1.0/main/configure.ac branches/stdair/0.1.0/main/stdair/bom/sources.mk branches/stdair/0.1.0/main/stdair.spec.in Added Paths: ----------- branches/stdair/0.1.0/main/ABOUT-NLS branches/stdair/0.1.0/main/TODO branches/stdair/0.1.0/main/man/Makefile.am branches/stdair/0.1.0/main/man/stdair-config.1 branches/stdair/0.1.0/main/man/stdair.3 Property Changed: ---------------- branches/stdair/0.1.0/main/man/ Added: branches/stdair/0.1.0/main/ABOUT-NLS =================================================================== --- branches/stdair/0.1.0/main/ABOUT-NLS (rev 0) +++ branches/stdair/0.1.0/main/ABOUT-NLS 2010-07-13 14:13:09 UTC (rev 221) @@ -0,0 +1,768 @@ +Notes on the Free Translation Project +************************************* + +Free software is going international! The Free Translation Project is +a way to get maintainers of free software, translators, and users all +together, so that will gradually become able to speak many languages. +A few packages already provide translations for their messages. + + If you found this `ABOUT-NLS' file inside a distribution, you may +assume that the distributed package does use GNU `gettext' internally, +itself available at your nearest GNU archive site. But you do _not_ +need to install GNU `gettext' prior to configuring, installing or using +this package with messages translated. + + Installers will find here some useful hints. These notes also +explain how users should proceed for getting the programs to use the +available translations. They tell how people wanting to contribute and +work at translations should contact the appropriate team. + + When reporting bugs in the `intl/' directory or bugs which may be +related to internationalization, you should tell about the version of +`gettext' which is used. The information can be found in the +`intl/VERSION' file, in internationalized packages. + +Quick configuration advice +========================== + +If you want to exploit the full power of internationalization, you +should configure it using + + ./configure --with-included-gettext + +to force usage of internationalizing routines provided within this +package, despite the existence of internationalizing capabilities in the +operating system where this package is being installed. So far, only +the `gettext' implementation in the GNU C library version 2 provides as +many features (such as locale alias, message inheritance, automatic +charset conversion or plural form handling) as the implementation here. +It is also not possible to offer this additional functionality on top +of a `catgets' implementation. Future versions of GNU `gettext' will +very likely convey even more functionality. So it might be a good idea +to change to GNU `gettext' as soon as possible. + + So you need _not_ provide this option if you are using GNU libc 2 or +you have installed a recent copy of the GNU gettext package with the +included `libintl'. + +INSTALL Matters +=============== + +Some packages are "localizable" when properly installed; the programs +they contain can be made to speak your own native language. Most such +packages use GNU `gettext'. Other packages have their own ways to +internationalization, predating GNU `gettext'. + + By default, this package will be installed to allow translation of +messages. It will automatically detect whether the system already +provides the GNU `gettext' functions. If not, the GNU `gettext' own +library will be used. This library is wholly contained within this +package, usually in the `intl/' subdirectory, so prior installation of +the GNU `gettext' package is _not_ required. Installers may use +special options at configuration time for changing the default +behaviour. The commands: + + ./configure --with-included-gettext + ./configure --disable-nls + +will respectively bypass any pre-existing `gettext' to use the +internationalizing routines provided within this package, or else, +_totally_ disable translation of messages. + + When you already have GNU `gettext' installed on your system and run +configure without an option for your new package, `configure' will +probably detect the previously built and installed `libintl.a' file and +will decide to use this. This might be not what is desirable. You +should use the more recent version of the GNU `gettext' library. I.e. +if the file `intl/VERSION' shows that the library which comes with this +package is more recent, you should use + + ./configure --with-included-gettext + +to prevent auto-detection. + + The configuration process will not test for the `catgets' function +and therefore it will not be used. The reason is that even an +emulation of `gettext' on top of `catgets' could not provide all the +extensions of the GNU `gettext' library. + + Internationalized packages have usually many `po/LL.po' files, where +LL gives an ISO 639 two-letter code identifying the language. Unless +translations have been forbidden at `configure' time by using the +`--disable-nls' switch, all available translations are installed +together with the package. However, the environment variable `LINGUAS' +may be set, prior to configuration, to limit the installed set. +`LINGUAS' should then contain a space separated list of two-letter +codes, stating which languages are allowed. + +Using This Package +================== + +As a user, if your language has been installed for this package, you +only have to set the `LANG' environment variable to the appropriate +`LL_CC' combination. Here `LL' is an ISO 639 two-letter language code, +and `CC' is an ISO 3166 two-letter country code. For example, let's +suppose that you speak German and live in Germany. At the shell +prompt, merely execute `setenv LANG de_DE' (in `csh'), +`export LANG; LANG=de_DE' (in `sh') or `export LANG=de_DE' (in `bash'). +This can be done from your `.login' or `.profile' file, once and for +all. + + You might think that the country code specification is redundant. +But in fact, some languages have dialects in different countries. For +example, `de_AT' is used for Austria, and `pt_BR' for Brazil. The +country code serves to distinguish the dialects. + + The locale naming convention of `LL_CC', with `LL' denoting the +language and `CC' denoting the country, is the one use on systems based +on GNU libc. On other systems, some variations of this scheme are +used, such as `LL' or `LL_CC.ENCODING'. You can get the list of +locales supported by your system for your country by running the command +`locale -a | grep '^LL''. + + Not all programs have translations for all languages. By default, an +English message is shown in place of a nonexistent translation. If you +understand other languages, you can set up a priority list of languages. +This is done through a different environment variable, called +`LANGUAGE'. GNU `gettext' gives preference to `LANGUAGE' over `LANG' +for the purpose of message handling, but you still need to have `LANG' +set to the primary language; this is required by other parts of the +system libraries. For example, some Swedish users who would rather +read translations in German than English for when Swedish is not +available, set `LANGUAGE' to `sv:de' while leaving `LANG' to `sv_SE'. + + Special advice for Norwegian users: The language code for Norwegian +bokma*l changed from `no' to `nb' recently (in 2003). During the +transition period, while some message catalogs for this language are +installed under `nb' and some older ones under `no', it's recommended +for Norwegian users to set `LANGUAGE' to `nb:no' so that both newer and +older translations are used. + + In the `LANGUAGE' environment variable, but not in the `LANG' +environment variable, `LL_CC' combinations can be abbreviated as `LL' +to denote the language's main dialect. For example, `de' is equivalent +to `de_DE' (German as spoken in Germany), and `pt' to `pt_PT' +(Portuguese as spoken in Portugal) in this context. + +Translating Teams +================= + +For the Free Translation Project to be a success, we need interested +people who like their own language and write it well, and who are also +able to synergize with other translators speaking the same language. +Each translation team has its own mailing list. The up-to-date list of +teams can be found at the Free Translation Project's homepage, +`http://www.iro.umontreal.ca/contrib/po/HTML/', in the "National teams" +area. + + If you'd like to volunteer to _work_ at translating messages, you +should become a member of the translating team for your own language. +The subscribing address is _not_ the same as the list itself, it has +`-request' appended. For example, speakers of Swedish can send a +message to `sv-...@li...', having this message body: + + subscribe + + Keep in mind that team members are expected to participate +_actively_ in translations, or at solving translational difficulties, +rather than merely lurking around. If your team does not exist yet and +you want to start one, or if you are unsure about what to do or how to +get started, please write to `tra...@ir...' to reach the +coordinator for all translator teams. + + The English team is special. It works at improving and uniformizing +the terminology in use. Proven linguistic skill are praised more than +programming skill, here. + +Available Packages +================== + +Languages are not equally supported in all packages. The following +matrix shows the current state of internationalization, as of January +2004. The matrix shows, in regard of each package, for which languages +PO files have been submitted to translation coordination, with a +translation percentage of at least 50%. + + Ready PO files af am ar az be bg bs ca cs da de el en en_GB eo es + +----------------------------------------------------+ + a2ps | [] [] [] [] | + aegis | () | + ant-phone | () | + anubis | | + ap-utils | | + aspell | [] | + bash | [] [] [] [] | + batchelor | | + bfd | [] [] | + binutils | [] [] | + bison | [] [] [] | + bluez-pin | [] [] [] | + clisp | | + clisp | [] [] [] | + console-tools | [] [] | + coreutils | [] [] [] [] | + cpio | [] [] [] | + darkstat | [] () [] | + diffutils | [] [] [] [] [] [] [] | + e2fsprogs | [] [] [] | + enscript | [] [] [] [] | + error | [] [] [] [] [] | + fetchmail | [] () [] [] [] [] | + fileutils | [] [] [] | + findutils | [] [] [] [] [] [] [] | + flex | [] [] [] [] | + fslint | | + gas | [] | + gawk | [] [] [] [] | + gbiff | [] | + gcal | [] | + gcc | [] [] | + gettext | [] [] [] [] [] | + gettext-examples | [] [] [] [] | + gettext-runtime | [] [] [] [] [] | + gettext-tools | [] [] [] | + gimp-print | [] [] [] [] [] | + gliv | | + glunarclock | [] [] | + gnubiff | [] | + gnucash | [] () [] [] | + gnucash-glossary | [] () [] | + gnupg | [] () [] [] [] [] | + gpe-aerial | [] | + gpe-beam | [] [] | + gpe-calendar | [] [] | + gpe-clock | [] [] | + gpe-conf | [] [] | + gpe-contacts | [] [] | + gpe-edit | [] | + gpe-go | [] | + gpe-login | [] [] | + gpe-ownerinfo | [] [] | + gpe-sketchbook | [] [] | + gpe-su | [] [] | + gpe-taskmanager | [] [] | + gpe-timesheet | [] | + gpe-today | [] [] | + gpe-todo | [] [] | + gphoto2 | [] [] [] [] | + gprof | [] [] [] | + gpsdrive | () () () | + gramadoir | [] | + grep | [] [] [] [] [] [] | + gretl | [] | + gtick | [] () | + hello | [] [] [] [] [] [] | + id-utils | [] [] | + indent | [] [] [] [] | + iso_3166 | [] [] [] [] [] [] [] [] [] [] | + iso_3166_1 | [] [] [] [] [] [] | + iso_3166_2 | | + iso_3166_3 | [] | + iso_4217 | [] [] [] [] | + iso_639 | | + jpilot | [] [] [] | + jtag | | + jwhois | [] | + kbd | [] [] [] [] [] | + latrine | () | + ld | [] [] | + libc | [] [] [] [] [] [] | + libgpewidget | [] [] | + libiconv | [] [] [] [] [] | + lifelines | [] () | + lilypond | [] | + lingoteach | | + lingoteach_lessons | () () | + lynx | [] [] [] [] | + m4 | [] [] [] [] | + mailutils | [] [] | + make | [] [] [] | + man-db | [] () [] [] () | + minicom | [] [] [] | + mysecretdiary | [] [] [] | + nano | [] () [] [] [] | + nano_1_0 | [] () [] [] [] | + opcodes | [] | + parted | [] [] [] [] [] | + ptx | [] [] [] [] [] | + python | | + radius | [] | + recode | [] [] [] [] [] [] [] | + rpm | [] [] | + screem | | + scrollkeeper | [] [] [] [] [] [] | + sed | [] [] [] [] [] [] | + sh-utils | [] [] [] | + shared-mime-info | | + sharutils | [] [] [] [] [] [] | + silky | () | + skencil | [] () [] | + sketch | [] () [] | + soundtracker | [] [] [] | + sp | [] | + tar | [] [] [] [] | + texinfo | [] [] [] | + textutils | [] [] [] [] | + tin | () () | + tp-robot | | + tuxpaint | [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | | + util-linux | [] [] [] [] [] | + vorbis-tools | [] [] [] [] | + wastesedge | () | + wdiff | [] [] [] [] | + wget | [] [] [] [] [] [] | + xchat | [] [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] | + +----------------------------------------------------+ + af am ar az be bg bs ca cs da de el en en_GB eo es + 4 0 0 1 9 4 1 40 41 60 78 17 1 5 13 68 + + et eu fa fi fr ga gl he hr hu id is it ja ko lg + +-------------------------------------------------+ + a2ps | [] [] [] () () | + aegis | | + ant-phone | [] | + anubis | [] | + ap-utils | [] | + aspell | [] [] | + bash | [] [] | + batchelor | [] [] | + bfd | [] | + binutils | [] [] | + bison | [] [] [] [] | + bluez-pin | [] [] [] [] [] | + clisp | | + clisp | [] | + console-tools | | + coreutils | [] [] [] [] [] [] | + cpio | [] [] [] [] | + darkstat | () [] [] [] | + diffutils | [] [] [] [] [] [] [] | + e2fsprogs | | + enscript | [] [] | + error | [] [] [] [] | + fetchmail | [] | + fileutils | [] [] [] [] [] [] | + findutils | [] [] [] [] [] [] [] [] [] [] [] | + flex | [] [] [] | + fslint | [] | + gas | [] | + gawk | [] [] [] | + gbiff | [] | + gcal | [] | + gcc | [] | + gettext | [] [] [] | + gettext-examples | [] [] | + gettext-runtime | [] [] [] [] [] | + gettext-tools | [] [] [] | + gimp-print | [] [] | + gliv | () | + glunarclock | [] [] [] [] | + gnubiff | [] | + gnucash | () [] | + gnucash-glossary | [] | + gnupg | [] [] [] [] [] [] [] | + gpe-aerial | [] | + gpe-beam | [] | + gpe-calendar | [] [] [] | + gpe-clock | [] | + gpe-conf | [] | + gpe-contacts | [] [] | + gpe-edit | [] [] | + gpe-go | [] | + gpe-login | [] [] | + gpe-ownerinfo | [] [] [] | + gpe-sketchbook | [] | + gpe-su | [] | + gpe-taskmanager | [] | + gpe-timesheet | [] [] [] | + gpe-today | [] [] | + gpe-todo | [] [] | + gphoto2 | [] [] [] | + gprof | [] [] | + gpsdrive | () () () | + gramadoir | [] [] | + grep | [] [] [] [] [] [] [] [] [] [] [] | + gretl | [] [] | + gtick | [] [] [] | + hello | [] [] [] [] [] [] [] [] [] [] [] [] [] | + id-utils | [] [] [] [] | + indent | [] [] [] [] [] [] [] [] [] | + iso_3166 | [] [] [] [] [] [] [] | + iso_3166_1 | [] [] [] [] [] | + iso_3166_2 | | + iso_3166_3 | | + iso_4217 | [] [] [] [] [] [] | + iso_639 | | + jpilot | [] () | + jtag | [] | + jwhois | [] [] [] [] | + kbd | [] | + latrine | [] | + ld | [] | + libc | [] [] [] [] [] [] | + libgpewidget | [] [] [] [] | + libiconv | [] [] [] [] [] [] [] [] [] | + lifelines | () | + lilypond | [] | + lingoteach | [] [] | + lingoteach_lessons | | + lynx | [] [] [] [] | + m4 | [] [] [] [] | + mailutils | | + make | [] [] [] [] [] [] | + man-db | () () | + minicom | [] [] [] [] | + mysecretdiary | [] [] | + nano | [] [] [] [] | + nano_1_0 | [] [] [] [] | + opcodes | [] | + parted | [] [] [] | + ptx | [] [] [] [] [] [] [] | + python | | + radius | [] | + recode | [] [] [] [] [] [] | + rpm | [] [] | + screem | | + scrollkeeper | [] | + sed | [] [] [] [] [] [] [] [] [] | + sh-utils | [] [] [] [] [] [] [] | + shared-mime-info | [] [] [] | + sharutils | [] [] [] [] [] | + silky | () [] () () | + skencil | [] | + sketch | [] | + soundtracker | [] [] | + sp | [] () | + tar | [] [] [] [] [] [] [] [] [] | + texinfo | [] [] [] [] | + textutils | [] [] [] [] [] [] | + tin | [] () | + tp-robot | [] | + tuxpaint | [] [] [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | [] [] | + util-linux | [] [] [] [] () [] | + vorbis-tools | [] | + wastesedge | () | + wdiff | [] [] [] [] [] [] | + wget | [] [] [] [] [] [] [] | + xchat | [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] [] | + +-------------------------------------------------+ + et eu fa fi fr ga gl he hr hu id is it ja ko lg + 22 2 1 26 106 28 24 8 10 41 33 1 26 33 12 0 + + lt lv mk mn ms mt nb nl nn no nso pl pt pt_BR ro ru + +-----------------------------------------------------+ + a2ps | [] [] () () [] [] [] | + aegis | () () () | + ant-phone | [] [] | + anubis | [] [] [] [] [] [] | + ap-utils | [] () [] | + aspell | [] | + bash | [] [] [] | + batchelor | [] | + bfd | [] | + binutils | [] | + bison | [] [] [] [] [] | + bluez-pin | [] [] [] | + clisp | | + clisp | [] | + console-tools | [] | + coreutils | [] [] | + cpio | [] [] [] [] [] | + darkstat | [] [] [] [] | + diffutils | [] [] [] [] [] [] | + e2fsprogs | [] | + enscript | [] [] [] [] | + error | [] [] [] | + fetchmail | [] [] () [] | + fileutils | [] [] [] | + findutils | [] [] [] [] [] | + flex | [] [] [] [] | + fslint | [] [] | + gas | | + gawk | [] [] [] | + gbiff | [] [] | + gcal | | + gcc | | + gettext | [] [] [] | + gettext-examples | [] [] [] | + gettext-runtime | [] [] [] [] | + gettext-tools | [] [] | + gimp-print | [] | + gliv | [] [] [] | + glunarclock | [] [] [] [] | + gnubiff | [] | + gnucash | [] [] () [] | + gnucash-glossary | [] [] | + gnupg | [] | + gpe-aerial | [] [] [] [] | + gpe-beam | [] [] [] [] | + gpe-calendar | [] [] [] [] | + gpe-clock | [] [] [] [] | + gpe-conf | [] [] [] [] | + gpe-contacts | [] [] [] [] | + gpe-edit | [] [] [] [] | + gpe-go | [] [] [] | + gpe-login | [] [] [] [] | + gpe-ownerinfo | [] [] [] [] | + gpe-sketchbook | [] [] [] [] | + gpe-su | [] [] [] [] | + gpe-taskmanager | [] [] [] [] | + gpe-timesheet | [] [] [] [] | + gpe-today | [] [] [] [] | + gpe-todo | [] [] [] [] | + gphoto2 | [] | + gprof | [] [] | + gpsdrive | () () [] | + gramadoir | () [] | + grep | [] [] [] [] [] | + gretl | | + gtick | [] [] [] | + hello | [] [] [] [] [] [] [] [] [] [] | + id-utils | [] [] [] [] | + indent | [] [] [] [] | + iso_3166 | [] [] [] | + iso_3166_1 | [] [] | + iso_3166_2 | | + iso_3166_3 | [] | + iso_4217 | [] [] [] [] [] [] [] [] | + iso_639 | [] | + jpilot | () () | + jtag | | + jwhois | [] [] [] [] () | + kbd | [] [] [] | + latrine | [] | + ld | | + libc | [] [] [] [] | + libgpewidget | [] [] [] | + libiconv | [] [] [] [] [] | + lifelines | | + lilypond | | + lingoteach | | + lingoteach_lessons | | + lynx | [] [] [] | + m4 | [] [] [] [] [] | + mailutils | [] [] [] | + make | [] [] [] [] | + man-db | [] | + minicom | [] [] [] [] | + mysecretdiary | [] [] [] | + nano | [] [] [] [] [] | + nano_1_0 | [] [] [] [] [] [] | + opcodes | [] [] | + parted | [] [] [] [] | + ptx | [] [] [] [] [] [] [] [] | + python | | + radius | [] [] | + recode | [] [] [] [] | + rpm | [] [] [] | + screem | | + scrollkeeper | [] [] [] [] [] | + sed | [] [] [] | + sh-utils | [] [] | + shared-mime-info | [] [] | + sharutils | [] [] | + silky | () | + skencil | [] [] | + sketch | [] [] | + soundtracker | | + sp | | + tar | [] [] [] [] [] [] | + texinfo | [] [] [] [] | + textutils | [] [] | + tin | | + tp-robot | [] | + tuxpaint | [] [] [] [] [] [] [] [] | + unicode-han-tra... | | + unicode-transla... | | + util-linux | [] [] [] | + vorbis-tools | [] [] [] | + wastesedge | | + wdiff | [] [] [] [] [] | + wget | [] [] [] | + xchat | [] [] [] | + xfree86_xkb_xml | [] [] | + xpad | [] [] | + +-----------------------------------------------------+ + lt lv mk mn ms mt nb nl nn no nso pl pt pt_BR ro ru + 1 2 0 3 12 0 10 69 6 7 1 40 26 36 76 63 + + sk sl sr sv ta th tr uk ven vi wa xh zh_CN zh_TW zu + +-----------------------------------------------------+ + a2ps | [] [] [] [] | 16 + aegis | | 0 + ant-phone | | 3 + anubis | [] [] | 9 + ap-utils | () | 3 + aspell | | 4 + bash | | 9 + batchelor | | 3 + bfd | [] [] | 6 + binutils | [] [] [] | 8 + bison | [] [] | 14 + bluez-pin | [] [] [] | 14 + clisp | | 0 + clisp | | 5 + console-tools | | 3 + coreutils | [] [] [] [] | 16 + cpio | [] [] | 14 + darkstat | [] [] [] () () | 12 + diffutils | [] [] [] | 23 + e2fsprogs | [] [] | 6 + enscript | [] [] | 12 + error | [] [] [] | 15 + fetchmail | [] [] | 11 + fileutils | [] [] [] [] [] | 17 + findutils | [] [] [] [] [] [] | 29 + flex | [] [] | 13 + fslint | | 3 + gas | [] | 3 + gawk | [] [] | 12 + gbiff | | 4 + gcal | [] [] | 4 + gcc | [] | 4 + gettext | [] [] [] [] [] | 16 + gettext-examples | [] [] [] [] [] | 14 + gettext-runtime | [] [] [] [] [] [] [] [] | 22 + gettext-tools | [] [] [] [] [] [] | 14 + gimp-print | [] [] | 10 + gliv | | 3 + glunarclock | [] [] [] | 13 + gnubiff | | 3 + gnucash | [] [] | 9 + gnucash-glossary | [] [] [] | 8 + gnupg | [] [] [] [] | 17 + gpe-aerial | [] | 7 + gpe-beam | [] | 8 + gpe-calendar | [] [] [] [] | 13 + gpe-clock | [] [] [] | 10 + gpe-conf | [] [] | 9 + gpe-contacts | [] [] [] | 11 + gpe-edit | [] [] [] [] [] | 12 + gpe-go | | 5 + gpe-login | [] [] [] [] [] | 13 + gpe-ownerinfo | [] [] [] [] | 13 + gpe-sketchbook | [] [] | 9 + gpe-su | [] [] [] | 10 + gpe-taskmanager | [] [] [] | 10 + gpe-timesheet | [] [] [] [] | 12 + gpe-today | [] [] [] [] [] | 13 + gpe-todo | [] [] [] [] | 12 + gphoto2 | [] [] [] | 11 + gprof | [] [] | 9 + gpsdrive | [] [] | 3 + gramadoir | [] | 5 + grep | [] [] [] [] | 26 + gretl | | 3 + gtick | | 7 + hello | [] [] [] [] [] | 34 + id-utils | [] [] | 12 + indent | [] [] [] [] | 21 + iso_3166 | [] [] [] [] [] [] [] | 27 + iso_3166_1 | [] [] [] | 16 + iso_3166_2 | | 0 + iso_3166_3 | | 2 + iso_4217 | [] [] [] [] [] [] | 24 + iso_639 | | 1 + jpilot | [] [] [] [] [] | 9 + jtag | [] | 2 + jwhois | () [] [] | 11 + kbd | [] [] | 11 + latrine | | 2 + ld | [] [] | 5 + libc | [] [] [] [] | 20 + libgpewidget | [] [] [] [] | 13 + libiconv | [] [] [] [] [] [] [] [] | 27 + lifelines | [] | 2 + lilypond | [] | 3 + lingoteach | | 2 + lingoteach_lessons | () | 0 + lynx | [] [] [] | 14 + m4 | [] [] | 15 + mailutils | | 5 + make | [] [] [] | 16 + man-db | [] | 5 + minicom | | 11 + mysecretdiary | [] [] | 10 + nano | [] [] [] [] | 17 + nano_1_0 | [] [] [] | 17 + opcodes | [] [] | 6 + parted | [] [] [] | 15 + ptx | [] [] | 22 + python | | 0 + radius | | 4 + recode | [] [] [] | 20 + rpm | [] [] | 9 + screem | [] [] | 2 + scrollkeeper | [] [] [] | 15 + sed | [] [] [] [] [] [] | 24 + sh-utils | [] [] | 14 + shared-mime-info | [] [] | 7 + sharutils | [] [] [] [] | 17 + silky | () | 3 + skencil | [] | 6 + sketch | [] | 6 + soundtracker | [] [] | 7 + sp | [] | 3 + tar | [] [] [] [] [] | 24 + texinfo | [] [] [] | 14 + textutils | [] [] [] [] | 16 + tin | | 1 + tp-robot | | 2 + tuxpaint | [] [] [] [] [] | 29 + unicode-han-tra... | | 0 + unicode-transla... | | 2 + util-linux | [] [] | 15 + vorbis-tools | | 8 + wastesedge | | 0 + wdiff | [] [] [] | 18 + wget | [] [] [] [] [] [] [] [] | 24 + xchat | [] [] [] [] [] | 15 + xfree86_xkb_xml | [] [] [] [] [] | 11 + xpad | | 5 + +-----------------------------------------------------+ + 63 teams sk sl sr sv ta th tr uk ven vi wa xh zh_CN zh_TW zu + 131 domains 47 19 28 83 0 0 59 13 1 1 11 0 22 22 0 1373 + + Some counters in the preceding matrix are higher than the number of +visible blocks let us expect. This is because a few extra PO files are +used for implementing regional variants of languages, or language +dialects. + + For a PO file in the matrix above to be effective, the package to +which it applies should also have been internationalized and +distributed as such by its maintainer. There might be an observable +lag between the mere existence a PO file and its wide availability in a +distribution. + + If January 2004 seems to be old, you may fetch a more recent copy of +this `ABOUT-NLS' file on most GNU archive sites. The most up-to-date +matrix with full percentage details can be found at +`http://www.iro.umontreal.ca/contrib/po/HTML/matrix.html'. + +Using `gettext' in new packages +=============================== + +If you are writing a freely available program and want to +internationalize it you are welcome to use GNU `gettext' in your +package. Of course you have to respect the GNU Library General Public +License which covers the use of the GNU `gettext' library. This means +in particular that even non-free programs can use `libintl' as a shared +library, whereas only free software can use `libintl' as a static +library or use modified versions of `libintl'. + + Once the sources are changed appropriately and the setup can handle +the use of `gettext' the only thing missing are the translations. The +Free Translation Project is also available for packages which are not +developed inside the GNU project. Therefore the information given above +applies also for every other Free Software Project. Contact +`tra...@ir...' to make the `.pot' files available to +the translation teams. + Modified: branches/stdair/0.1.0/main/ChangeLog =================================================================== --- branches/stdair/0.1.0/main/ChangeLog 2010-07-13 12:01:56 UTC (rev 220) +++ branches/stdair/0.1.0/main/ChangeLog 2010-07-13 14:13:09 UTC (rev 221) @@ -0,0 +1,3 @@ +* Fri Jul 9 2010 Anh Quan Nguyen <quannaus at users dot sourceforge dot net> 0.1.0 +- First release. Air-Sched and AirInv are both working on top of it. + Modified: branches/stdair/0.1.0/main/Makefile.am =================================================================== --- branches/stdair/0.1.0/main/Makefile.am 2010-07-13 12:01:56 UTC (rev 220) +++ branches/stdair/0.1.0/main/Makefile.am 2010-07-13 14:13:09 UTC (rev 221) @@ -25,7 +25,7 @@ EXTRA_DIST = # Build in these directories: -SUBDIRS = stdair @PACKAGE@ $(HTML_DOC_DIR) extracppunit $(TEST_DIR) +SUBDIRS = stdair @PACKAGE@ man $(HTML_DOC_DIR) extracppunit $(TEST_DIR) # Configuration helpers Modified: branches/stdair/0.1.0/main/NEWS =================================================================== --- branches/stdair/0.1.0/main/NEWS 2010-07-13 12:01:56 UTC (rev 220) +++ branches/stdair/0.1.0/main/NEWS 2010-07-13 14:13:09 UTC (rev 221) @@ -0,0 +1,3 @@ + +2010-07-13: Release of RPMs for Fedora 13. + Added: branches/stdair/0.1.0/main/TODO =================================================================== Modified: branches/stdair/0.1.0/main/configure.ac =================================================================== --- branches/stdair/0.1.0/main/configure.ac 2010-07-13 12:01:56 UTC (rev 220) +++ branches/stdair/0.1.0/main/configure.ac 2010-07-13 14:13:09 UTC (rev 221) @@ -2,7 +2,7 @@ #------------------------------------------------------------------- AC_PREREQ(2.59) AC_COPYRIGHT([Copyright (C) 2007-2010 Denis Arnaud <den...@us...>]) -AC_INIT([STDAIR],[99.99.99],[den...@us...],[stdair]) +AC_INIT([STDAIR],[0.1.0],[den...@us...],[stdair]) AC_CONFIG_HEADER([stdair/config.h]) AC_CONFIG_SRCDIR([stdair/bom/BomKey.hpp]) AC_CONFIG_AUX_DIR([config]) @@ -15,7 +15,7 @@ AC_SUBST(RPM_RELEASE) # Shared library versioning -GENERIC_LIBRARY_VERSION="99:99:99" +GENERIC_LIBRARY_VERSION="0:1:0" # | | | # +------+ | +---+ # | | | @@ -222,6 +222,7 @@ stdair/service/Makefile stdair/core/Makefile stdair/batches/Makefile + man/Makefile doc/Makefile doc/images/Makefile doc/tutorial/Makefile Property changes on: branches/stdair/0.1.0/main/man ___________________________________________________________________ Added: svn:ignore + .deps .libs Makefile Makefile.in Added: branches/stdair/0.1.0/main/man/Makefile.am =================================================================== --- branches/stdair/0.1.0/main/man/Makefile.am (rev 0) +++ branches/stdair/0.1.0/main/man/Makefile.am 2010-07-13 14:13:09 UTC (rev 221) @@ -0,0 +1,4 @@ +# Man pages +man_MANS = stdair.3 stdair-config.1 + +EXTRA_DIST = $(man_MANS) Added: branches/stdair/0.1.0/main/man/stdair-config.1 =================================================================== --- branches/stdair/0.1.0/main/man/stdair-config.1 (rev 0) +++ branches/stdair/0.1.0/main/man/stdair-config.1 2010-07-13 14:13:09 UTC (rev 221) @@ -0,0 +1,37 @@ +.TH StdAir 1 "13 July 2010" +.SH NAME +stdair-config - script to get version number and compiler flags of the installed StdAir library +.SH SYNOPSIS +.B stdair-config +[\-\-prefix] [\-\-version] [\-\-libs] [\-\-cflags] +.SH DESCRIPTION +.PP +\fIstdair-config\fP is a tool that is used to configure to determine +the compiler and linker flags that should be used to compile +and link programs that use \fIStdAir\fP. It is also used internally +to the .m4 macros for GNU autoconf that are included with \fIStdAir\fP. +. +.SH OPTIONS +\fIstdair-config\fP accepts the following options: +.TP 8 +.B \-\-version +Print the currently installed version of \fIStdAir\fP on the standard output. +.TP 8 +.B \-\-libs +Print the linker flags that are necessary to link a \fIStdAir\fP program, with cblas +.TP 8 +.B \-\-cflags +Print the compiler flags that are necessary to compile a \fIStdAir\fP program. +.TP 8 +.B \-\-prefix +Show the StdAir installation prefix. +.SH SEE ALSO +.BR boost-config (1) +.SH COPYRIGHT +Copyright \(co 2010 Denis Arnaud + +Permission to use, copy, modify, and distribute this software and its +documentation for any purpose and without fee is hereby granted, +provided that the above copyright notice appear in all copies and that +both that copyright notice and this permission notice appear in +supporting documentation. Added: branches/stdair/0.1.0/main/man/stdair.3 =================================================================== --- branches/stdair/0.1.0/main/man/stdair.3 (rev 0) +++ branches/stdair/0.1.0/main/man/stdair.3 2010-07-13 14:13:09... [truncated message content] |