Often any kind of “./configure” step will allow you to simply name “arm64” or “aarch64” architecture and it will “just work” (or when compiled natively, then this will be auto detected and not even require a special config). There are cases where code is architecture dependent though, e.g., it uses assembler, and you’ll need significant knowledge. More likely the “./configure” step will allow you a chance to change features, and after any build error you’ll just adjust the “./configure” and get past that error…and keep going that way until it builds. You’ll probably need specific issues to quote from the actual build before more can be answered (e.g., it might use cmake instead of configure scripts).
Above all, I would suggest looking at what provides the package on another Linux system using its package tool. It isn’t unusual for people to get caught up trying to build from the manufacturer’s site when it turns out the tool or lib already exists by some other name…in which case a single command could have taken care of everything. If you do run into trouble with this library give specific details of what library it is and where it came from originally (if you can’t just add a package, then someone else will need to reproduce your build to get the error and give advice).