On 18. 5. 26 20:57, Timofei Zhakov wrote:
On Sat, May 16, 2026 at 9:16 PM Ivan Zhakov <[email protected]> wrote:On Sat, 16 May 2026 at 20:19, Nathan Hartman <[email protected]> wrote: r1934265 (improving the CMake text in INSTALL) reminded me that CMake is not yet mentioned in the 1.15.x Release Notes. I'd like to add it there--after all, it is a new major (and long- requested!) feature in 1.15.x! +1! 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.Tiny note: autotools does have support for clang (or any other compiler. Somebody should try using CCC but it's so unnecessary). This is done by changing the 'CC' environment variable before running configure. For some reason it still thinks it's gcc but it doesn't matter as long as it's a GNU style compiler.
Autotools are quite happy with non-GNU-style compilers. I've used autoconf on HP-UX and Irix and AIX and SunOS with their native compilers, where the only flags they have in common with gcc are -g and -O and -c and -o and a few other basic ones — because those were present in the original Unix cc.
Soon I will try to tackle pkgconfig modules, sasl, libmagic, and SVN_DISABLE_PLAINTEXT_PASSWORD_STORAGE from that list. They all should be pretty straightforward to do.
Handling pkg-config modules implies generating a libsvn_*.pc file for each of our libraries with the appropriate pkg-config dependencies declared. It's about as straightforward as a corkscrew. :) We don't do it in configure.
-- Brane
