Hi, Zitat von Marcel Holtmann <mar...@holtmann.org>: >> TODOs tagged not-me: >> * Someone needs to integrate building the manpages into the autotools >> files. The >> CMake code supports xsltproc, saxon-6.5.x and xalan2 but using >> xsltproc may be >> sufficient for autotools support. Else, no manpages will be created when >> using ./configure to build openobex. > > It is acceptable for me since manpages are for the testing tools anyway. > The main focus is on the library and not the tools. So that would not > stop me from doing the release.
The policy in Debian is to provide manpage for all programs. But I do build using CMake so it's also not a show-stopper for me. >> * Maybe someone can make autotools use the doc/Doxyfile.in file >> instead of the >> hardcoded doc/Doxyfile. The variables are already autotools-compatible. > > Isn't it enough to just have autoconf generate Doxyfile from Doxyfile.in > and that just works then? Exactly. In CMake I create doc/Doxyfile_HTML and doc/Doxyfile_LATEX from doc/Doxyfile.in when cmake is run (which is equivalent of running ./configure). Using the doc/Doxyfile.in is one file less to change the version number in (@DOC_VERSION@) and allows out-of-source builds with both, autotools and cmake (@DOC_BINARY_DIR@ and @DOC_SOURCE_FILES@). Additional, it allows to choose what types of documentation to build (@DOC_HTML_OUTPUT@ and @DOC_LATEX_OUTPUT@). >> I can also add a patch that changes the version in all places or maybe >> a small release checklist file, so nothing gets left out. >> >> I still don't thing that 6:0:0 is the right library version. Libtool's >> way of versioning libraries is.... ugly :-( >> Is there a way to trick it into creating files like >> libopenobexs.so -> libopenobex.so.1.6.0 >> libopenobex.so.2 -> libopenobex.so.1.6.0 >> ? >> Currently, that will rename libopenobex.so.1.5.0 (old) to >> libopenobex.so.6.0.0 (new) which looks like a marketing versioning. > > Sine the USB changes break the API compatibility, -version-info 2:0:0 > should be the right thing to do. Or not? Not according to libtool documentation. But Christian doesn't seem to have a problem with the strange numbering... HS ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
