In archive “FeResPost_win64_5.2.0_*.7z” the binaries contain ruby wrappers, COM component and C++ library:
“OUTPUTS/lib” directory contains the file “libFeResPost_5.2.0.dll” that corresponds to the FeResPost C++ library without any wrapper. If you intend to work with this shared library, this file should be located in a directory that appears in the “Path” environment variable. (The FeResPost extension shared libraries are linked to this C++ library so that it must be accessible.)
“OUTPUTS/include” directory and its subdirectories contain FeResPost C++ headers. You have no use of these files unless you wish to develop your own wrapper for FeResPost (for use with Python, Perl, Java...), or use FeResPost C++ library in one of your C++ applications. So most of you can forget this directory.
“OUTPUTS/RUBY/” directory contains RUBY extensions for ruby (in different sub-directories).
“OUTPUTS/PYTHON/” directory contains Python extensions for Python (in different sub-directories).
“OUTPUTS/COM” contains the directories and files for the COM component (dll and tlb files). Information on the installation of the COM component on Windows is given in section X.A.4.5.
The ruby and python libraries must be used with the appropriate 64-bit distribution of ruby or python. There is no issue related to random access to large XDB or FAC files with 64-bit versions of FeResPost binaries. The “*” in archive name can be “w10” or “w11”, depending on the computer on which the libraries have been compiled (Windows 10 or Windows 11).