Bug#904688: qttools-opensource-src: FTBFS: please drop the libclang-dev B-D on some architectures
On 07/29/2018 09:12 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> 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 have actually never seen anyone compile them into the binary, not even
on Windows. I'm surprised people still do that. Anyway.
>> 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"
Qt applications normally will just find these files if you put them into
/usr/share/$APPNAME. My own Qt application "qhimdtransfer" from the linux-
minidisc project does that.
> 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 :-/
Porting LLVM to a new target isn't something that is done over night, it's
a bit of an effort. But there are already out-of-tree ports for Alpha, IA64
and m68k. All of them are not in a usable state though, but we will be getting
there. I want to make LLVM available on more architectures in order to get
Rust support there. Once LLVM support is there, adding support in Rust is
rather simple.
But that's a different story.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: