As WiringPi was never meant to support other boards nor does the author like to support other boards and it is officially depreciated now (http://wiringpi.com/wiringpi-deprecated/).
I want to ask why not put some efforts into libmraa https://github.com/intel-iot-devkit/mraa and put it into the Armbian repository.
I have already a fork which fixes Rock Pi 4 on recent mainline 5.3 kernels with updated debian build scripts here: https://github.com/bootsy52/mraa, so debian packages could be simple built using dpgk-buildpackage.
Why I think it is a good idea to supply libmraa with the Armbian repository
Supporting multiple boards is a desired goal of the project
Supporting a board is really easy, for Rock Pi for example this is just the files src/arm/rockpi4.c include/arm/rockpi4.h and an entry in src/arm/arm.c, that's it
Instead of multiple forks of wiringPi and different sources of different versions (or even different gpio implementations) just have one common implementation for all boards
with wiringPi you need additional bridges if you want to code in other languages like Java or Python for example, with MRAA you have out of the box bindings for Python, Java, Javascript, C/C++ and NodeJS support
What do you think? @Igor
I can confirm latest 5.3.11 buster server Image working fine on RockPI 4A with EMMC.
Further more I used CP2102 successfully to connect via putty on serial console of RockPI at 1500000
Personally as I'm using SoC for industrial purposes I'm glad that there is not coming anything new all the time, because we need stable, good software support and
I have to test everything and support everything. I'm using RockPI 4A and I really hope, that I'll get longterm access to this product as it's fits perfect my needs.