Internally drgn uses Autoconf and Automake (from GNU Autotools) to configure and build (with the help of make) the C code. Autotools are very old, difficult to develop, and usually a bit slower (bunch of useless configure check, use of libtool, no Ninja support) compare to more modern build systems like CMake or Meson. Autotools had their time and place. For legacy software it might still worth relying on it. For actively developed software I would expect the use of an alternative.
Is there any interest to switch to CMake or Meson?
Internally drgn uses Autoconf and Automake (from GNU Autotools) to configure and build (with the help of make) the C code. Autotools are very old, difficult to develop, and usually a bit slower (bunch of useless configure check, use of libtool, no Ninja support) compare to more modern build systems like CMake or Meson. Autotools had their time and place. For legacy software it might still worth relying on it. For actively developed software I would expect the use of an alternative.
Is there any interest to switch to CMake or Meson?