[question] Unable to find the video to the slides presented at cppcon2024

[maitrey]

What is your question?

Dear Conan Folks,

I would like to watch the video to : https://github.com/CppCon/CppCon2024/blob/main/Presentations/Common_Package_Specification_In_Practice.pdf
But I am unable to find it, perhaps not yet uploaded.
Could you please help me by providing the link to it?

Thanks!
Br,
Maitrey

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

[AbrilRBS]

Hi @maitrey thanks a lot for your interest in our CPS presentation, we appreciate it.

Unfortunately most CppCon 2024 videos are yet to be released. They have now started the process as of a few weeks ago, but it will still take some time to get all of them out, so my only suggestion is to keep an eye out on https://www.youtube.com/@CppCon/videos :)

[maitrey]

Thank you for your answer. Will keep an eye every now and then in that case.

[AbrilRBS]

Will make sure to post it here once it's released, closing for now as solved :)

[AbrilRBS]

The video has now been released at https://www.youtube.com/watch?v=pFQHQEm98Ho, if you have any feedback/questions, feel free to create new issues :)

[maitrey]

Hi @AbrilRBS ,

I have some questions:

• I want to try the CPSDeps but could not find anything in the changelog: https://docs.conan.io/2/changelog.html
• With which version of cmake is cps available?
• Where are the examples from Diego's presentation in the video?
• Is it true that package_info method is replaced by generated cps if enabled?
• Could you please elaborate what is executables model ? How different it is from library modules?
• What are the advantages of using conan and cps(Please help me if I understood it correctly):
  • Support Multi build systems
  • Generate cps for multi build systems
  • Storage is not available for cps even though the definition of a library/binary/module is provided

[memsharded]

• CPSDeps is not documented yet. It will be in the new "incubating" section when possible, but we are now prioritizing the new CMakeDeps generator that is more "CPS-conformant/ready". If you want to try it, just use generators = "CPSDeps" in your recipe or command line -g CPSDeps. In any case, things have already changed in CPS and we have also learned some new things, so it is already a bit outdated
• CMake 3.31 contained that CPS generation, under a feature-flag, check https://cmake.org/cmake/help/latest/command/install.html
• Repo: https://github.com/memsharded/cppcon24
• Yes, when things work and everything integrates, the full package_info() implementation can be dropped. In the experiments, it can be reduced to just 2 lines reading the cps file inside the package
• The executables model is the new cpp_info.exe and cpp_info.components["myapp"].exe that can create IMPORTED EXECUTABLE targets in the new CMakeDeps generator

What are the advantages of using conan and cps(Please help me if I understood it correctly):

The main advantages will be:

• Way simpler to consume package and create packages.
• The package_info() can dissapear
• Less issues, patches, adaptations necessary to use some third party package dependencies

Conan already manages multi build-systems, natively via the cpp_info model. You can see the CPS as an standardized version of the cpp_info model.

[memsharded]

The video is now public in https://www.youtube.com/watch?v=pFQHQEm98Ho

I am moving this ticket to the docs repo, where we will probably add these features to the "incubating" section when possible. Thanks for the feedback.