notcurses_core(3)

πŸ’… notcurses_core(3) β€” minimal Notcurses linkage

okay so this is the manual page notcurses_core, section 3, and it’s all about linking the tiny-core version without dragging the whole multimedia party into your binary. bestie, it’s giving minimal.

🌸 NAME 🌸

notcurses_core β€” minimal Notcurses linkage


✨ SYNOPSIS ✨

#include <notcurses/notcurses.h>

-lnotcurses-core

struct notcurses* notcurses_core_init(const notcurses_options* opts,
FILE* fp);

struct ncdirect* ncdirect_core_init(const char* termtype, FILE* fp,
uint64_t flags);

πŸ¦‹ DESCRIPTION πŸ¦‹

If your binary has no use for the multimedia capabilities of Notcurses, consider linking directly to libnotcurses-core rather than libnotcurses. This ought greatly reduce the dependency burden of Notcurses. slay for smaller dependency trees, honestly.

If using libnotcurses-core, notcurses_core_init must be used in the place of notcurses_init, and ncdirect_core_init must be used in the place of ncdirect_init. Failure to do will usually result in an error during linking. At worst, you’ll end up with the unnecessary dependencies in your binary after all. 😭 not the linker jumpscare.


πŸ’€ BUGS πŸ’€

This all ought be handled by the toolchain. It’s stupid for users to have to think about this. periodt.


🧚 NOTES 🧚

If Notcurses was built with USE_MULTIMEDIA=none, libnotcurses will have no multimedia dependencies, and thus this won’t save anything. It’s still best to explicitly use libnotcurses-core when appropriate, to avoid picking up the dependency chain on systems where it is being used. iykyk β€” be intentional with your linkage.


πŸ‘‘ RETURN VALUES πŸ‘‘

The same as notcurses_init and ncdirect_init.


🌈 SEE ALSO 🌈


πŸŽ€ AUTHORS πŸŽ€

nick black nickblack@linux.com


source/version check: this page is from Notcurses v3.0.17, and the footer’s date slot is literally empty β€” no date listed, bestie. iconic minimalism fr fr. bye πŸ’–πŸ«Άβœ¨

πŸ“¦ where this page comes from