.\" Automatically generated by Pandoc 2.9.2.1
.\"
.TH "notcurses_core" "3" "v2.2.3" "" ""
.hy
.SH NAME
.PP
notcurses_core - minimal Notcurses linkage
.SH SYNOPSIS
.PP
\f[B]#include <notcurses/notcurses.h>\f[R]
.PP
\f[B]-lnotcurses-core\f[R]
.PP
\f[B]struct notcurses* notcurses_core_init(const notcurses_options*
\f[R]\f[I]opts\f[R]\f[B], FILE* \f[R]\f[I]fp\f[R]\f[B]);\f[R]
.PP
\f[B]struct ncdirect* ncdirect_core_init(const char*
\f[R]\f[I]termtype\f[R]\f[B], FILE* \f[R]\f[I]fp\f[R]\f[B], uint64_t
\f[R]\f[I]flags\f[R]\f[B]);\f[R]
.SH DESCRIPTION
.PP
If your binary has no use for the multimedia capabilities of Notcurses,
consider linking directly to \f[B]libnotcurses-core\f[R] rather than
\f[B]libnotcurses\f[R].
This ought greatly reduce the dependency burden of Notcurses.
.PP
If using \f[B]libnotcurses-core\f[R], \f[B]notcurses_core_init\f[R] must
be used in the place of \f[B]notcurses_init\f[R], and
\f[B]ncdirect_core_init\f[R] must be used in the place of
\f[B]ncdirect_init\f[R].
Failure to do will usually result in an error during linking.
At worst, you\[aq]ll end up with the unnecessary dependencies in your
binary after all.
.SH BUGS
.PP
This all ought be handled by the toolchain.
It\[aq]s stupid for users to have to think about this.
.SH NOTES
.PP
If Notcurses was built with \f[B]USE_MULTIMEDIA=none\f[R],
\f[B]libnotcurses\f[R] will have no multimedia dependencies, and thus
this won\[aq]t save anything.
It\[aq]s still best to explicitly use \f[B]libnotcurses-core\f[R] when
appropriate, to avoid picking up the dependency chain on systems where
it \f[I]is\f[R] being used.
.SH RETURN VALUES
.PP
The same as \f[B]notcurses_init\f[R] and \f[B]ncdirect_init\f[R].
.SH SEE ALSO
.PP
\f[B]notcurses(3)\f[R], \f[B]notcurses_direct(3)\f[R],
\f[B]notcurses_init(3)\f[R], \f[B]utf8(7)\f[R]
.SH AUTHORS
nick black <nickblack@linux.com>.