It may take several hours, a day or a week for a response on some mailing lists. If it's a slow mailing list, someone with the project may respond in a week or two.
You can make a Makefile for your own computer that will build it. On FreeBSD, the Makefile is for both building it for yourself, and that is refined and used to make a port. When it builds on your computer or after some effort, someone may help you or give you better advice. You can post your attempt of the Makefile here, then on the FreeBSD ports mailing list, which is the one where it would needed to be, so someone can take up your porting attempt. The Porter's Handbook gives instructions for that. You'll have to read it all.
Here's an example of a Makefile changed from the Porter's Handbook
Code:
# $FreeBSD$
PORTNAME= iup
PORTVERSION= 3.29
CATEGORIES= x11-toolkits
MASTER_SITES= SF/projects/iup/files/3.29/Docs%20and%20Sources/
MAINTAINER= youremail@example.com
COMMENT= Cat chasing a mouse all over the screen
.include <bsd.port.mk>
Put this in a custom directory, perhaps in a folder in your home directory.
You can tinker with that, while you're waiting for a response on a mailing list. I'm not good with it, so parts of that may be wrong. SF is short for sourceforge. To get the checksum when it's needed, use
make makesum (not checksum) from that directory. There's more entries you'll need, like perhaps, USES= gtk2 zlib. Build this Makefile up from here.
Get further and further in compiling it, as the more you get, the more of the program that will compile, then ask here, then on the FreeBSD ports mailing list, show your progress, and you'll get a few responses in a day or two. Mailing lists take patience.
I don't know if you're familiar with the portstree. Use the
portsnap fetch command, with either extract or update options. Here's details about how to update your
/usr/ports/:
https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/ports-using.html. The Porter's Handbook and the FreeBSD Handbook are two different ones.
