A distinction is made below between the installation of the ruby extension, the COM server and the .NET assembly. In practice, depending on what you want to do, only some parts of the binaries must be installed/configured. Table X.A.2 summarizes what you need to do. Before configuring FeResPost, always make sure that you are selecting the right version of the binaries. In particular:
For ruby and python extensions:
Make sure that you are using the FeResPost extension library that matches your ruby version.
Choose the right version among LINUX and Windows binaries.
Choose the appropriate version among 32-bit and 64-bit libraries (for ruby wrapper library as well as FeResPost C++ library).
For COM component (on Windows), choose the Windows 32 or 64-bit C++ libraries for Windows.
There is no significant risk of mistake for the .NET assembly, but you have to chose between CLR2 and CLR4, and between 32-bit and 64-bit versions (for CLR4). Actually, CLR2 is rather old, so that CLR4 should work on most computers.
If you want to... | You must... |
Use FeResPost in ruby scripts | Install the corresponding FeResPost C++ ruby extension (section X.A.4.3) |
Use FeResPost as COM component (Windows only) | Install and register the COM component (section X.A.4.5) |
Use the .NET assembly | Install the assembly in GAC (global assembly cache) as explained in section X.A.4.6. An installation of the redistributable Microsoft Visual C++ libraries may also be necessary. |
Develop you own wrapper around FeResPost C++ library, or write a program that directly uses the C++ library | Install the C++ library and corresponding header files (section X.A.4.2) |
Modify and/or recompile the sources | Copy the sources and try to find inspiration in the information provided in section X.A.2 |