This is the closest relevant line from the latest CHANGELOG file:
- asdf:make-build accepts ~:init-name~ argument for libraries
this allows specifying human-memorable initialization function name to call
in C code
Also it seems all their latest documentation seems still to be specifying `(asdf:make-build)` as the way to build libraries from .asd systems. If I use the make-build function on the 3.3.4 asdf, besides complaining about using a deprecated interface, I get an unuseable .a that seems to have ignored my :init-name arg and generated a .a with the random init func name. At least the bundled asdf 3.1.8.8 included in this new April 2020 ecl honors the :init-name.
This is the closest relevant line from the latest CHANGELOG file:
- asdf:make-build accepts ~:init-name~ argument for libraries
this allows specifying human-memorable initialization function name to call
in C code
Also it seems all their latest documentation seems still to be specifying `(asdf:make-build)` as the way to build libraries from .asd systems. If I use the make-build function on the 3.3.4 asdf, besides complaining about using a deprecated interface, I get an unuseable .a that seems to have ignored my :init-name arg and generated a .a with the random init func name. At least the bundled asdf 3.1.8.8 included in this new April 2020 ecl honors the :init-name.
I did just post this issue also to ecl too: /gitlab. com/embeddable- common- lisp/ecl/ -/issues/ 603
https:/
I'm using the single asdf.lisp bundling of asdf 3.3.4 and not sure how to run tests from that.