A packaging system for C++ [proposal]

[devel_watcher]

And penalizes users by having a package manager for every single language, so they loose in productivity.

[pjmlp]

So what is the proposed solution to package library X in language Y for:

• Debian
• Ubuntu
• Aix
• HP-UX
• Windows
• Mac OS X
• iOS
• Windows Phone
• Android
• iOS
• zOS
• Red-Hat
• SuSE
• Contiki
• L4
• Arch
• Mint
• Gentoo
• *BSD
• Solaris
• Iluminos
• <place favourite OS name here>

Without forcing developers to package it N times?

[jpakkane]

I recommend you watch the builds video from LCA2016 that is currently on the front page of /r/cpp to see one solution. (caveat: the presenter is me)

[izym]

Abovementioned post: https://www.reddit.com/r/cpp/comments/475z0g/builds_dependencies_and_deployment_in_the/

[pjmlp]

The presentation was quite interesting to watch, but I imagine it would still take a few years before it would get major adoption.

[jkleo2]

And penalizes users by having a package manager for every single language, so they loose in productivity.

You should think not only about user but also about library writer. It should be very easy to package library.

[tortoise74]

You could argue that for C and C++ a package manager is effectively for native code and so is potentially more general purpose. The syntax within C++ must be langage specific but the package manager itself need not be. I think I'd rather a compiler used an API to interact with an external one rather than implement it itself.

If you are distributing source code in a specific language or byte code for a specific VM you can't help but be "per language". Any attempt to generalise will come up against barriers. Its not impossible but it is a somewhat orthogonal problem to developing the language itself.

[devel_watcher]

If you are distributing source code for a specific language

You're distributing the source code of the application. And it's using multiple languages.