libinotify is not a typical example because it installs to a non-standard 
dir to try to avoid being picked up without explicit configuration in other 
ports

I've just looked through a bunch of libraries and struggling to find 
something I'd suggest as a good starting point, many have something a bit 
atypical - I'd start from ports/infrastructure/Makefile.template

generally for a library we'd like to have some other software intended for 
adding to ports that uses it, rather than just adding it standalone


-- 
  Sent from a phone, apologies for poor formatting.


On 26 January 2026 18:47:12 "Sergey A. Osokin" <osa@freebsd.org> wrote:

> Hi Paul,
> hope you're doing well.
>
> On Mon, Jan 26, 2026 at 09:47:19AM -0500, Paul Wisehart wrote:
>> Hi!,
>>
>> I am wanting to make a port for a C lib.
>> (specifically mtemplate in this case.)
>>
>> I am new to porting.  Can someone recommend
>> a similar existing port to copy off of?
>> Something that is just basic no dependency
>> C code, that is turned into a system lib.
>
> There're many libraries ported into OpenBSD available in
> the devel subdirectory of OpenBSD ports tree,
> https://cvsweb.openbsd.org/ports/devel/, and one of
> those is libinotify, so you may want to take a look on
> that here:
> - https://cvsweb.openbsd.org/ports/devel/libinotify/, or
> - https://github.com/openbsd/ports/tree/master/devel/libinotify/
>
> It's also recommended to read OpenBSD Porter's Handbook,
> https://www.openbsd.org/faq/ports/index.html, describes
> porting, build, cleaning and other related staff for a port.
>
> Hope that helps.
>
> Thank you.
>
> --
> Sergey A. Osokin
> tipi.work