"Default" CMake Usage

[tcanabrava]

Is there an existing proposal for this?

• [X] I have searched the existing proposals

Is your feature request related to a problem?

The code is using internal bloomberg tools to find and build using the .mem and .dep definitions that means that common tools that relies in cmake find_package to show and visualize cmake information will not be able to run with this project.

would it be ok to use the (documented) way to develop with bde, and add the find_package(bsl) int he places that are needed? This way we can package blazingmq together with the packaged version of bde-tools and bde.

Describe the solution you'd like

Use standard cmake for opensource builds

Alternatives you considered

No response

[hallfox]

Hi @tcanabrava, thanks for the report. BlazingMQ's CMake modules should work with the BdeBuildSystem provided by bde-tools in the CMAKE_PREFIX_PATH (here's an example from the docker build).

We are working on making this a bit more normal by using find_package for bde and ntf-core libraries for certain workflows that use package management though.

[hallfox]

We now have the build-ubuntu.sh and build-darwin.sh scripts which should provide a fairly out of the box build for BlazingMQ, and if you're curious how the CMake commands work I recommend looking there.

Build scripts: https://github.com/bloomberg/blazingmq/tree/main/bin