Skip to content
Allow access in reading and writing to Energistics standards data (mainly RESQML2.0, ETP1.2, some of WITSML2.0 and PRODML2.1)
C++ SWIG Java CMake C C#
Branch: master
Clone or download

Latest commit

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update bug_report.md Aug 31, 2018
cmake Fix HdfProxyFactory dll export (#217) Feb 28, 2020
cs Fix #215 : min and max value of slab properties (#216) Feb 17, 2020
doc Allow partial object creation in SWIG and in win DLL (#193) Oct 23, 2019
example Fix HdfProxyFactory dll export (#217) Feb 28, 2020
gsoap Move to Apache 2.0 license. Fix #35 Feb 2, 2018
java Fix Java build on Linux (#219) Mar 6, 2020
resources Move SVN repo to Git Repo (#1) Nov 13, 2017
src Fix HdfProxyFactory dll export (#217) Feb 28, 2020
swig Fix #215 : min and max value of slab properties (#216) Feb 17, 2020
test Fix #215 : min and max value of slab properties (#216) Feb 17, 2020
.gitignore Graphical Informations update (#163) Jul 23, 2019
.travis.yml Fix Java build on Linux (#219) Mar 6, 2020
.whitesource Migrate WhiteSource configuration file to json format May 17, 2019
CMakeLists.txt Fix Java build on Linux (#219) Mar 6, 2020
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md Nov 22, 2017
CONTRIBUTING.md Support for reading RESQML 2.0 sealed surface framework (#106) Mar 7, 2019
LICENSE Move to Apache 2.0 license. Fix #35 Feb 2, 2018
NOTICE Move to Apache 2.0 license. Fix #35 Feb 2, 2018
PULL_REQUEST_TEMPLATE.md Fix #215 : min and max value of slab properties (#216) Feb 17, 2020
README.md Allow BOOST UUID to manage uuids (#204) Dec 5, 2019
azure-pipelines.yml Replace AppVeyor CI by Azure Pipeline (#196) Nov 6, 2019

README.md

Prepare your build environment

  • Create a folder called fesapiEnv.
  • In this folder create the three following folders
    • build
    • fesapi (Git clone this repository into this folder "fesapi". You should then have a path fesapiEnv/fesapi/src)
    • dependencies
  • The following compilers are known to work
    • gcc from version 4.4
    • visual studio from version 2015
    • clang from version 5.0

Prepare the dependencies

Download (build and install if necessary) third party libraries:

  • HDF5: All versions of 1.8.* starting from 1.8.18 and all versions of 1.10.* starting from 1.10.2 should be ok. https://support.hdfgroup.org/ftp/HDF5/releases/
  • MINIZIP : Version 1.1 is needed : it is the official version included in current zlib distribution https://www.zlib.net/ (look into "contrib" folder). You can directly install minizip development package on most of Linux distributions (https://packages.ubuntu.com/xenial/libminizip-dev). On Windows (or older Linux distributions), you can copy the CMakeLists.txt file from fesapi/cmake/minizip to the zlib minizip directory to help you to build minizip (we also provide a copy of minizip 1.1 with cmake files on github : https://github.com/F2I-Consulting/Minizip). It is also highly recommended to link minizip to the same zlib library than the one associated to your HDF5 library.
  • BOOST (only uuid library, ONLY if FESAPI_USE_BOOST_UUID cmake variable is set) : Starting from version 1.44.0. FYI, on windows, boost uuid depends on bcrypt library.
  • UUID-DEV package (ONLY FOR LINUX AND ONLY IF FESAPI_USE_BOOST_UUID cmake variable is not set) : Source code can be found in https://www.kernel.org/pub/linux/utils/util-linux/

We advise you to install these third party libraries respectively into

  • fesapiEnv/dependencies/hdf5-particularVersion
  • fesapiEnv/dependencies/minizip-particularVersion
  • fesapiEnv/dependencies/uuid-particularVersion (or in system directory using : sudo apt-get install uuid-dev)

Configure the build

Fesapi uses cmake as its build tool. A 3.12 version or later of cmake is required https://cmake.org/download/. We also recommend using cmake-gui (already included in the bin folder of the binary releases of cmake) which provides a graphical user interface on top of cmake. Follow the below instructions :

  • yourPath/fesapiEnv/fesapi defines where is the source code folder
  • yourPath/fesapiEnv/build/theNameYouWant defines where to build the binaries
  • Click on "Configure" button and select your favorite compiler : it will raise several errors.
  • give real values, path and files to the following cmake variables:
    • HDF5
      • HDF5_1_10 : true if you link to a HDF5 library version 1.10. false (default) if you link to a HDF5 library version 1.8
      • (ONLY FOR WINDOWS) HD5_BUILT_AS_DYNAMIC_LIB : true if you link to a shared HDF5 library else false
      • HDF5_C_INCLUDE_DIR : where the HDF5 headers are located
      • (ONLY FOR WINDOWS) HDF5_C_LIBRARY_DEBUG : Optional, only used by Visual studio Debug configuration, the HDF5 debug library you want to link to .
      • HDF5_C_LIBRARY_RELEASE : the HDF5 library you want to link to. On Visual studio, it is used on Release configuration. With other compilers, it is the default HDF5 library to link to.
    • MINIZIP
      • MINIZIP_INCLUDE_DIR : where the HDF5 headers are located
      • (ONLY FOR WINDOWS) MINIZIP_LIBRARY_DEBUG : Optional, only used by Visual studio Debug configuration, the MINIZIP debug library you want to link to
      • MINIZIP_LIBRARY_RELEASE : the MINIZIP library you want to link to. On Visual studio, it is used on Release configuration. With other compilers, it is the default HDF5 library to link to.
    • ZLIB
      • ZLIB_INCLUDE_DIR : where the zlib headers (commonly zlib.h only) are located. If you use the HDF5 binaries downloaded from HDF Group website, then it should be the same as HDF5_C_INCLUDE_DIR.
      • (ONLY FOR WINDOWS) ZLIB_LIBRARY_DEBUG : Optional, only used by Visual studio Debug configuration, the ZLIB debug library you want to link to
      • ZLIB_LIBRARY_RELEASE : the ZLIB library you want to link to. It must be the same as the one which is linked to HDF5 library and MINIZIP library otherwise you will get a warning from CMake. If you use the HDF5 binaries downloaded from HDF Group website, use the zlib library which lies in the same directory as HDF5_C_LIBRARY_RELEASE. On Visual studio, it is used on Release configuration. With other compilers, it is the default ZLIB library to link to.
    • SZIP (it is only required when you statically link to HDF5 AND when HDF5 has been built using SZIP)
      • SZIP_LIBRARY_RELEASE : the SZIP library you want to link to. This warning can be ignored most of time but it can really create unpredictable bugs in some circumstances (static linking to HDF5 with HDF5 making use of szip).
    • UUID (ONLY FOR LINUX AND ONLY IF FESAPI_USE_BOOST_UUID cmake variable is not set)
      • UUID_INCLUDE_DIR : where the UUID headers are located
      • UUID_LIBRARY_RELEASE : the UUID library you want to link to
    • Boost (ONLY if FESAPI_USE_BOOST_UUID cmake variable is set)
      • Boost_INCLUDE_DIR : where the Boost headers are located (generally the boost install folder)
  • Click again on "Configure" button. You should no more have errors so you can now click on "Generate" button. alt text
  • You can now build your solution with your favorite compiler (and linker) using the generated solution in yourPath/fesapiEnv/build/theNameYouWant
  • OPTIONALLY, you can also set the variables WITH_DOTNET_WRAPPING or WITH_JAVA_WRAPPING to true if you want to also generate wrappers on top of fesapi for these two other programming languages. Don't forget to click again on "Configure" button once you changed the value of these two variables.
    • You will then have to also provide the path to the SWIG executable http://swig.org/download.html in the SWIG_EXECUTABLE variable (and click again on "Configure" button)
    • FOR Java and only for JAVA, you'll also have to provide various path to some java executables. Still only for Java, it is highly recommended to lower the optimization level of the C++ compilation by setting O1 instead of O2 in the variables called CMAKE_CXX_FLAGS_RELEASE and CMAKE_CXX_FLAGS_RELWITHDEBINFO
    • you will find the wrappers in fesapi/java/src or fesapi/cs/src (fesapi/cs also contains a VS2013 project for the wrappers)

Remark : you can choose where fesapi will be installed (using "make install" on Linux or by generating the "INSTALL" project on Visual Studio) by setting the cmake variable called CMAKE_INSTALL_PREFIX

Credits

This software was developed with the gSOAP toolkit from Genivia Inc

You can’t perform that action at this time.