nut_debug_level does not propagate to libnutscan from nut-scanner

[Bi11]

This issue was introduced by f82e78e.

Currently there are two instances of nut_debug_level, one in nut-scanner, another in libnutscan.
-DDD can not raise debug level of libnutscan.

[jimklimov]

Thanks! I wonder if I added to confusion, or just overlooked, with recent fixes for symbol visibility (static for file-private scope as lint suggested). Maybe an extra copy should be deleted and an extern declared in header.

…

On Tue, Dec 15, 2020, 15:20 Bi11 ***@***.***> wrote: This issue was introduced by f82e78e <f82e78e> . Currently there are two instances of nut_debug_level, one in nut-scanner, another in libnutscan. -DDD can not raise debug level of libnutscan. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#935>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMPTFFAKABOUMAVGTX326LSU5WDBANCNFSM4U4NB2HQ> .

[jimklimov]

Should be fixed by #1160