On 07/31/2018 09:16 PM, Sune Vuorela wrote: > - not embedding the resources on all platforms gives quite bigger deployment > issues on some platforms. (windows, mac, some mobile targets)
macOS always puts the resource files into separate folders inside the app bundle (which is just a folder). At least when I did professional Qt development. > - on some platforms, embedding resources gives faster startup and resource > access. (Especially windows) I think that difference is negligible. Plus, we're also not talking about Windows or macOS here, so the situation is not comparable. On Debian, we do have multiple versions of the same binary and storing the resource files is explicitly desired as it makes a difference in disk space when we're talking about hundreds or thousands of packages. > So embedding resources if you target cross platformness, and your resources > aren't too big and not actually shared with others often the easiest and > cheapest way forward. It costs mirroring linux distributions a slight disk > overhead, but I don't think that is too big of a problem. You're basically using the arguments for the Windows and macOS versions on Debian. In Debian, saving disk space through redundancy does defnitely make a difference. > But, more and more are going to need libclang. Given libclang is mostly a c++ > parser, I don't see why it shouldn't be buildable on most platforms ? Can't > the compiler bits be stripped from the llvm source package on some archs? That has to be seen. As I said, we're working on it. But it takes some time. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
