You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -142,15 +165,15 @@ In the "Owner" column, "S" means that the configuration key behavior is handled
142
165
* 2 : TLS with HTTP Basic Authentication
143
166
* 3 : TLS with Client Side Certificates
144
167
145
-
In Charge Point role, the stack will automatically disconnect and then reconnect using the new parameters to the Central System after one of the following parameters has been modified :
168
+
In Charge Point role, the stack will automatically disconnect and then reconnect using the new parameters to the Central System after one of the following parameters has been modified :
146
169
***AuthorizationKey**
147
170
***Security Profile**
148
171
149
172
**Restriction** : The automatic fallback to old connection parameters if the connection fails after switching to a new security is not implemented yet.
150
173
151
174
#### Security events
152
175
153
-
**Open OCPP** support the whole use cases of security events and logging.
176
+
**Open OCPP** support the whole use cases of security events and logging.
154
177
155
178
In Charge Point role, it can optionnaly handle the storage of the security event log and the generation of the security log export when the Central System asks it. To enable/disable this feature, you have to modify the **SecurityLogMaxEntriesCount** charge point configuration key :
156
179
@@ -167,7 +190,7 @@ In Charge Point role, the notification of security events can be enabled or disa
167
190
168
191
#### Certificate management
169
192
170
-
**Open OCPP** support this feature for both Charge Point and Central System roles.
193
+
**Open OCPP** support this feature for both Charge Point and Central System roles.
171
194
172
195
The behavior of this feature is controlled by the **InternalCertificateManagementEnabled** configuration key.
173
196
@@ -302,6 +325,45 @@ And to run the unit tests :
302
325
303
326
```make tests-gcc-native``` or ```make tests-clang-native```
304
327
328
+
The build generates 2 flavors of the **Open OCPP** librairies depending on the needs of your project :
329
+
* Shared : libopen-ocpp.so
330
+
* Static : libopen-ocpp_static.a
331
+
332
+
**Note**: When using **Open OCPP** in a non GNU LGPL project, the shared library must be used in order to not contaminate your project with the LGPL licence.
333
+
334
+
## Install and use
335
+
### Installation
336
+
337
+
**Open OCPP** generated libraries and their includes can be installed in the standard system directories using the CMake command :
338
+
339
+
```cmake --install [build_dir] --strip```
340
+
341
+
The makefile contains helper targets which can be called if the installation needs to be done in a non standard directory using the variable INSTALL_PREFIX :
342
+
343
+
```make install-gcc-native INSTALL_PREFIX=/your/directory``` or ```make install-clang-native INSTALL_PREFIX=/your/directory```
344
+
345
+
If run without the INSTALL_PREFIX variable, it will install in the standard system directories.
346
+
347
+
**Note**: If INSTALL_PREFIX is used, it must also be defined when building the project with the makefile helper targets.
348
+
349
+
### Use with CMake
350
+
351
+
**Open OCPP** installs 2 pkg-config configurations files to ease the use of the library when compiling a CMake project.
352
+
353
+
To import the library in a CMake project, use the following commands in your CMakeLists.txt file :
Then you wil be able to use the following targets as dependencies for your project :
362
+
363
+
```target_link_libraries(my_proj PRIVATE PkgConfig::PKG_OPEN_OCPP)``` or ```target_link_libraries(my_proj PRIVATE PkgConfig::PKG_OPEN_OCPP_STATIC)```
364
+
365
+
**Note**: If **Open OCPP** has been installed in a non standard directory, the search path for the ```pkg_search_module``` command must be specified using the following command => ```set(ENV{PKG_CONFIG_PATH} "/your/directory/containing/the/.pc/files")```
366
+
305
367
## Quick start
306
368
307
369
The best way to start is to take a look at the [examples](./examples/README.md) and more specifically at the [quick start Charge Point example](./examples/quick_start_chargepoint/README.md) and the [quick start Central System example](./examples/quick_start_centralsystem/README.md).
0 commit comments