On Tuesday, July 31, 2018 8:48:42 PM CEST John Paul Adrian Glaubitz wrote: > It's still a bad practice, in my personal opinion, because it adds > redundancy.
It is kind of - from an upstream POV - what kind of situation you optimize for. - embedding the resources in the executable or library might add redundancy if someone distributes several versions, but disk space is cheap in these sizes. - not embedding the resources on some platforms gives different code paths. Code paths are quite expensive from a testing POV. - not embedding the resources on all platforms gives quite bigger deployment issues on some platforms. (windows, mac, some mobile targets) - embedding resources make the resources harder to hack/modify on disk. Some think it is an advantage. Others a disadvantage. - on some platforms, embedding resources gives faster startup and resource access. (Especially windows) 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. 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? /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
