going by the manual's snippets on `importcpp` and the `link` pragma, is `link`
expected to work for statically linking `.a` libs? the examples have `.so` and
`.o`.

i'm getting a wall of errors [trying to repro this tiny mini prog in
nim](https://github.com/metaleap/mo25/blob/main/mo_app/mo_app.cpp) except all
the nim side does so far is open SDL2 window (works) and `{.link.}` (errors
badly). that tiny c++ proj's [build
setup](https://github.com/metaleap/mo25/blob/main/meson.build) needs NO special
or lib-specific compiler/linker args whatsoever (the 2 I have are optional, not
needed), just the info "link this statically". and my wip nim version doesnt
even use that lib yet, just trying a lone `{.link:
"/usr/local/lib/WickedEngine/libWickedEngine_Linux.a".}` in the main (and only)
`.nim` file

the 1000s of errors are all of the pattern "/usr/bin/ld:
<filename>.cpp:(<internalNoise>): undefined reference to `<someIdentifier>`".
what ld is even trying to do with an already-fully-built-and-also-fully-unused
lib there, I dunno..