3 ms·

Importing binary packages is a terrible idea, and a source of huge problems. I don't understand how conan managed to get so much traction, it is so very bad, m

Importing binary packages is a terrible idea, and a source of huge problems. I don't understand how conan managed to get so much traction, it is so very bad, most of its recipes have billions of options most of which don't work. The only sensible way to work with C++ is to always build from source, and let the build system transparently cache and reuse binary artifacts as an optimization.

pjmlp 4y ago
Not when one's business depends on shipping binaries, and selling components. Then again, it isn't something that is relevant in GNU/Linux world, only in other platforms.
- mgaunard 4y ago
  There is nothing special about GNU/Linux is that respect. You would still build your code from source, and be very careful handling any dependencies you don't have the source for. The worst kind of undefined behaviour you can have in C++ is ODR violations, and importing binaries is more likely than not to trigger them, unless you closely manage their ABI.
  - pjmlp 4y ago
    Yes, there is, the culture towards shipping binaries, or selling component libraries.
    - vegerot 4y ago
      I think you two are talking past each other. He’s talking about hypotheticals, and you’re talking about what’s more common
strager 4y ago
> Importing binary packages is a terrible idea, and a source of huge problems. Importing binary packages is a tradeoff.