Excluding libzen requirement

From what I can see libzen is only really needed for zen media devices. Is there any way in the configure to exclude this dependency?

Currenly looking at making mediainfo 0.7.83 available to MacPorts, but trying to see the best way to deal with this dependency.

libzen is a library I created for making my life easier with stuff like strings, strings lists, cross-platform support (file access and so on), and is intensively used as the base of all in MediaInfo(Lib).
Removing this dependancy is impossible (replacing home mane strings by std::string is doable with some work, but I am not really motivated for putting "#ifdef WIN32" or "#ifdef MINGW" in MediaInfo(Lib) code, I still prefer to have a dedicated library for cross-platform support).
this is the only one mandatory library.

Currenly looking at making mediainfo 0.7.83 available to MacPorts, but trying to see the best way to deal with this dependency.

Using the "all in one" package, with libzen in it, is from my point of view the easier and safer way to have MediaInfo like the official Mac version, so with better support from upstream.
You can check the homebrew formula for MediaInfo, I like the way they did it.

I'll take a look at the homebew formula.

BTW Looking at the instruction in 'Project/Mac/HowToBuild.txt' I don't see CLI_Compile.sh or SO_Compile.sh . Did I miss something?

Edit: noticed there is difference between the source distribution and the GitHub project contents. Is there a recipe to create the source distribution based on GitHub source?

BTW Looking at the instruction in 'Project/Mac/HowToBuild.txt' I don't see CLI_Compile.sh or SO_Compile.sh . Did I miss something?

'Project/Mac/HowToBuild.txt' is the start of some documentation for the Mac App Store GUI compilation, not for the CLI (as well as not for the GUI based on Wx, the one currently use for Linux and non Mac App Store version of Mac GUI)
I am fully aware that it is a bit messy, having something less messy is on the ToDo-list.

noticed there is difference between the source distribution and the GitHub project contents. Is there a recipe to create the source distribution based on GitHub source?

Ugly scripts.
But if you just want to put it on MacPort, please just use the "all in one" .tar.gz, it will make my life easir in case I have to do some support on third party releases like MacPorts.

Note that if you prefer to have split packages (libzen, libmediainfo, mediainfo), I would prefer that you follow the compilation process used e.g. by MediaInfo in Debian (you need to sownload the .debian.tar.xz, and script is in /debian/rules file).