GEOS
GEOS copied to clipboard
GEOS-DEV
add flags to enable fesapi
created branch to add flags to enable fesapi from the third parties (related to #2109)
@bmhan12 @wrtobin There needs to be some spack/uberenv work in conjunction with this?
@rrsettgast I think Fesapi would need some spack work. Fesapi has zlib, minizip and boost (only headers) as dependencies. I checked that boost is already in spack and available as a header only dependency. It is exactly what fesapi needs. It would even be easier than with CMake's ExternalProject_Add function.
@rrsettgast I think Fesapi would need some spack work. Fesapi has zlib, minizip and boost (only headers) as dependencies. I checked that boost is already in spack and available as a header only dependency. It is exactly what fesapi needs. It would even be easier than with CMake's ExternalProject_Add function.
But on the long term, what would be your exact requirements? Do you have a clear picture on this?
We'll need to implement a spack package recipe for fesapi, but it can be done after the initial integration into GEOSX is complete IMO. For now, to avoid breaking spack build, I propose we modify it to explicitly disable fesapi (spit out ENABLE_FESAPI=OFF into the generated host-config).
have
But on the long term, what would be your exact requirements? Do you have a clear picture on this?
In a first step for file based access:
- hdf5 (default numerical values storage for RESQML)
- minizip (in order to deal with zip files)
- boost (only headers for having uuid support).
In a long-term view with connection to OSDU, it will be necessary to add:
- FETPAPI
- AVRO (for serialization and deserialization of message)
- Boost (libraries, not only headers, mainly Beast sublibrary for websocket support)
- OpenSSL (TLS support).
You are second in line https://github.com/GEOSX/GEOSX/projects/18
ok, do you have any idea when it will happen ?
ok, do you have any idea when it will happen ?
@rrsettgast is going to give https://github.com/GEOSX/GEOSX/pull/2149 a last view.