docbook cannot be compiled because FindDocBookXML.cmake is missing
Locked
docbook cannot be compiled because FindDocBookXML.cmake is missing
 
|
Hey everyone!
To compile the manuals digikam requires FindDocBookXML.cmake which is part of kdelibs. However, the CMakeLists.txt inside kdelibs4/cmake/modules... does not "publish" that cmake file, i.e. it is not packaged into any devel package if one follows that default. Hence digikam will not find that file on user's systems and docbooks cannot be compiled. So either digikam must not use that file or kdelibs has to make it public in order for it to be installed + packaged. Sven _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
Why the cmake script is not public ? There is a specific reason ?
Gilles Caulier Le 28 mars 2012 11:27, Sven Burmeister <[hidden email]> a écrit : > Hey everyone! > > To compile the manuals digikam requires FindDocBookXML.cmake which is part of > kdelibs. > > However, the CMakeLists.txt inside kdelibs4/cmake/modules... does not > "publish" that cmake file, i.e. it is not packaged into any devel package if > one follows that default. Hence digikam will not find that file on user's > systems and docbooks cannot be compiled. > > So either digikam must not use that file or kdelibs has to make it public in > order for it to be installed + packaged. > > Sven > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
Is there a reason that FindDocBookXML.cmake and FindDocBookXSL.cmake are not installed by kdelibs? I am told that anything not installed is used internally by kdelibs during build, but I am curious why these need to be internal only.
-Ananta On Wed, Mar 28, 2012 at 11:30 AM, Gilles Caulier <[hidden email]> wrote: Why the cmake script is not public ? There is a specific reason ? _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
Sven,
With this commit, this must solve the problem : http://commits.kde.org/scratch/mwiesweg/digikam-sc/2f8027dc5af33e61f66337e7db0135bec5344b4e But, i check in cmake install script from KDELibs (git/master) about cmake extensions, and these files are missing in the list. Why? I don't know... Perhaps it's just a miss from developers ? Both files are written by Luigi Toscano, <[hidden email]>. I recommend you to contact him about this problem. Gilles Caulier Le 28 mars 2012 12:42, Ananta Palani <[hidden email]> a écrit : > Is there a reason that FindDocBookXML.cmake and FindDocBookXSL.cmake are not > installed by kdelibs? I am told that anything not installed is used > internally by kdelibs during build, but I am curious why these need to be > internal only. > > -Ananta > > > On Wed, Mar 28, 2012 at 11:30 AM, Gilles Caulier <[hidden email]> > wrote: >> >> Why the cmake script is not public ? There is a specific reason ? >> >> Gilles Caulier >> >> Le 28 mars 2012 11:27, Sven Burmeister <[hidden email]> a écrit : >> > Hey everyone! >> > >> > To compile the manuals digikam requires FindDocBookXML.cmake which is >> > part of >> > kdelibs. >> > >> > However, the CMakeLists.txt inside kdelibs4/cmake/modules... does not >> > "publish" that cmake file, i.e. it is not packaged into any devel >> > package if >> > one follows that default. Hence digikam will not find that file on >> > user's >> > systems and docbooks cannot be compiled. >> > >> > So either digikam must not use that file or kdelibs has to make it >> > public in >> > order for it to be installed + packaged. >> > >> > Sven >> > _______________________________________________ >> > Digikam-devel mailing list >> > [hidden email] >> > https://mail.kde.org/mailman/listinfo/digikam-devel >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
Gilles,
After a talk on #kde-devel it seems that meinproc4 is supposed to handle docbook generation and that is why those Find*.cmake files are not installed. They are only used when kdelibs is built in order to build meinproc4. Apparently the way you are already building docs: KDE4_CREATE_HANDBOOK(index.docbook INSTALL_DESTINATION ${HTML_INSTALL_DIR}/en SUBDIR digikam) uses meinproc4 automatically. Was there another reason you added the check to see if docbook was installed? -Ananta On Wed, Mar 28, 2012 at 1:35 PM, Gilles Caulier <[hidden email]> wrote: Sven, _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
Le 28 mars 2012 16:36, Ananta Palani <[hidden email]> a écrit :
> Gilles, > > After a talk on #kde-devel it seems that meinproc4 is supposed to handle > docbook generation and that is why those Find*.cmake files are not > installed. They are only used when kdelibs is built in order to build > meinproc4. Apparently the way you are already building docs: > > KDE4_CREATE_HANDBOOK(index.docbook INSTALL_DESTINATION > ${HTML_INSTALL_DIR}/en SUBDIR digikam) > > uses meinproc4 automatically. Was there another reason you added the check > to see if docbook was installed? yes, because under windows, meinproc4 do not find XML files from kdelibs to generated handbook. It try to compile, but report a lots of worse in the console. Something is missing in KDE installer for windows. I tried to use this cmake scripts to check if all is present in computer. Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: docbook cannot be compiled because FindDocBookXML.cmake is missing
|
|
In reply to this post by Ananta Palani
On Wed, 28 Mar 2012 11:42:02 +0100, Ananta Palani <[hidden email]>
wrote: > Is there a reason that FindDocBookXML.cmake and FindDocBookXSL.cmake are > not installed by kdelibs? I am told that anything not installed is used > internally by kdelibs during build, but I am curious why these need to be > internal only. Because they are not meant to be public. They are only needed to build meinproc4, the executable responsible for generating the documentation. meinproc4 is part of kdelibs, so this shouldn't be needed at all (in fact, they are not). See below for other comments. > On Wed, Mar 28, 2012 at 11:30 AM, Gilles Caulier > <[hidden email]>wrote: > >> Why the cmake script is not public ? There is a specific reason ? >> >> Gilles Caulier >> >> Le 28 mars 2012 11:27, Sven Burmeister <[hidden email]> a >> écrit: >> > Hey everyone! >> > >> > To compile the manuals digikam requires FindDocBookXML.cmake which is >> part of >> > kdelibs. >> > >> > However, the CMakeLists.txt inside kdelibs4/cmake/modules... does not >> > "publish" that cmake file, i.e. it is not packaged into any devel >> > package if >> > one follows that default. Hence digikam will not find that file on >> > user's >> > systems and docbooks cannot be compiled. >> > >> > So either digikam must not use that file or kdelibs has to make it >> > public in >> > order for it to be installed + packaged. Yesterday there was a discussion about this on #digikam, the situation can be summarized as follow (please correct me if I'm wrong): - the build problem comes out on windows _only_; Gilles reported that using the KDE windows dev environment with MSVC2010 the documentation is not generated unless the above mentioned FindDocbok* are included, which is strange. - another users (notedible, sorry, I don't know your name :) reported that he was able to compile digikam using emerge, with some tweaks (but without using the two FindDocBook*). I know that there were some changes in the kde-4.8 branch of emerge by Patrick Spendrin, but iirc they were more related to runtime usage of documentation, not generation). To summarize: - copying the two FindDocBook* is just a workaround in a special case; - this special case must be probably fixed, but it needs help from the the KDE Windows team (hence the CC) Ciao -- Luigi _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |