commit | c9da83ab5aed349930cf7c4221a84b729e978dd6 | [log] [tgz] |
---|---|---|
author | Mario Salazar de Torres <mario.salazar.de.torres@est.tech> | Tue Jan 26 16:43:11 2021 +0100 |
committer | GitHub <noreply@github.com> | Tue Jan 26 07:43:11 2021 -0800 |
tree | 87c12ed8e2e4bc5122a9faeee312965becf3c39b | |
parent | 9a46e7d89918c192c3edd5ff57dbfee078419883 [diff] |
GEODE-8735: Change factory logic for symbols lookup (#700) * GEODE-8735: Change factory logic for symbols lookup - In order to allow that factory logic looks into the application space for symbols, `library-name` field has been made optional. - This removes the need to create shared library for in order to define custom factories like cache loaders, cache writers, cache listeners, partition resolvers or persistance managers whenever the cache is instantiated declaratively. - Whenever library-name is not specified a handle to the executable is obtained. - Take into account that for OS like Linux, Mac... in addition to exporting the symbols in the application, you would need to specify `-rdynamic` option while compiling. - Documentation has been updated. * GEODE-8735: Revision 2 - Fixed application space factory functions. It seemed that loading factory functions from the application was not actually working. - Added an IT to verify that application space partition resolver factories are working. - Consequently an IT for shared library factories have been added to verify that the functionality was not working. - Added test factories to the testobject shared library. - Given GenerateExportHeader CMake module does not support executables and we need to set visibility attributes for the test factory functions inside cpp-integration-test, a new cmake module 'ExecutableExportHeader' has been added to support this. - In order to export symbols in a executable ENABLE_EXPORTS property needs to be specified for the target in CMake. Therefore, this property has been added for cpp-integration-test target. * GEODE-8735: Revision 3 - Changed client cache XML schema and namespace to the right ones.
Overview
Building from Source
Application Development
Native Client is a client implementation for Apache Geode that does not require the Java server JARs.
Directions to build Native Client from source can be found in the source distribution in BUILDING.md.
Native Client applications can be written in these client technologies:
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software: