El domingo, 29 de julio de 2018 15:39:51 -03 John Paul Adrian Glaubitz escribió: > On 07/29/2018 07:11 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > > Adrian: I have just remembered that there is actually a case in which > > building documentation can be rightfully in a binary build: when it's > > embedded in the application itself by using Qt's resources system. That's > > definitely not a bug, and those apps will surely FTBFS. > > From what I remember from my times of professional Qt development, I'm > pretty sure that even those resource files are generated as separate files. > I don't remember anything actually compiled into the resulting binary. All > those resource files were always separate.
Interesting, I have always used them inside the binary itself[1]. [1] <http://doc.qt.io/qt-5/resources.html#compiled-in-resources> But thanks to your comment I noted that indeed one can keep the resource file out of the main binary. > > I don't have the least idea of the number of apps that might be using that > > mechanism though. > > Do you have a link on that? I have my doubts that it's actually not possible > to separate the QDoc building from compiling the actual C++ code. Well, I am thinking in this workflow: - Generate QDoc documentation using qdoc. - Add the resulting files to a resource. - Access the documentation with QFile as usual, but using the name of the resource to start the URL. like ":/images/cut.png" Now I don't think many packages will go this route, as it's not straightforward to set up. But it should be doable. And still better than nothing. Of course having LLVM/clang available in all archs would be just better :-/ -- If little green men land in your back yard, hide any little green women you've got in the house. Mike Harding, "The Armchair Anarchist's Almanac" Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
