On Sat, 16 May 2026 at 22:23, Daniel Sahlberg <[email protected]>
wrote:

> Den lör 16 maj 2026 kl 21:18 skrev Ivan Zhakov <[email protected]>:
> >

[...]


> >> But I've lost track of where it is
> >> currently. Has it reached parity with the autotools build, e.g., being
> >> able to build all the bindings? Any current limitations I should
> >> document?
> >>
> >
> > A week ago I created document to summarize features supported by
> different Subversion build systems.
> >
> > Google Sheet document:
> >
> https://docs.google.com/spreadsheets/d/1goa9mrX75RhqQLSsNAr9z6G6cqDvUMDe5xWDJYG99cg/edit?gid=0#gid=0
> >
> > PDF is also attached.
> >
> > I didn't all features: in many cases I just have checked relevant source
> code.
> >
> > Any comments and fixes will be much appreciated.
>
> Very good document - is something we should bring to the website?
>
> I am not sure. I have created this document for internal (Subversion
developers) use. Just to have general overview. Also to make it's easier
for someone to improve CMake support.

May be we can put it in notes/ ? But the question what format to use:
plain-text, markdown or html?


> One question: Under Package Managers - are the "no" for the cmake
> column correct? I suppose this is pkg_search_module vs find_package?
>
> There are two features related to Package Managers in build systems:
a) Consuming dependencies from Package Manager.
b) Providing package to Package Manager.

In my document "Package Managers" supports means (b). But speaking of (a),
Subversion CMake build can consume packages from pkg-config.

-- 
Ivan Zhakov

Reply via email to