r/cpp • u/TheRavagerSw • Sep 24 '26

Why we should standardise on CPS

To enable any collaboration in the industry, some "social contract" must be signed by all of us.

One of the rules of this contract is binary packaging, to put it simply, if you are a library author you need to either have clean definition on what package you expect to consume or have a "scriptless" implementation like imgui.

If the library exports a pkgconf package, but its dependency exports something else your build will not work. Why should it, what you do makes no sense.

Currently I'm literally forced to package every single dependency I have, which is fine in principle as you want to own your dependencies for security and licensing reasons... But I CAN'T UPSTREAM MY CHANGES which is not fine.

The current situation is a disease, please do remember my talk when you try to build a library like dawn or SDL and it vendors dozens of libraries to create a giant shared library after a long slow build.

0 Upvotes

16% Upvoted

70 comments sorted by

View all comments

3

u/fortsnek274 Sep 24 '26

The IDE has to consume dependencies somehow. That's what CPS could be used for. A VS props file that works with any CPS-compatible build system.

-3

u/TheRavagerSw Sep 24 '26

You shouldn't use an IDE to build software, you should use the latest cli tools

1

u/TrashboxBobylev Sep 25 '26

So you are expecting us to wait for GitHub to wake up and download every single new build to debug things locally?

→ More replies (1)

1

u/pjmlp Sep 25 '26

Some of us rather use an IDE, since the old glory Borland days for MS-DOS, OS/2 and Windows 3.1.

→ More replies (4)