forked from blue/lmdbal
some fixes in README
This commit is contained in:
parent
c83369f347
commit
f39d44890a
21
README.md
21
README.md
@ -20,13 +20,30 @@ If you're using LMDBAL as a system library you probably have no control over it'
|
||||
```
|
||||
find_package(lmdbal)
|
||||
if (LMDBAL_FOUND)
|
||||
target_include_directories(yourTarget PRIVATE {LMDBAL_INCLUDE_DIRS})
|
||||
target_include_directories(yourTarget PRIVATE ${LMDBAL_INCLUDE_DIRS})
|
||||
target_link_libraries(yourTarget PRIVATE LMDBAL::LMDBAL)
|
||||
endif()
|
||||
```
|
||||
|
||||
#### As an embeded subproject
|
||||
//TODO
|
||||
|
||||
If you're using LMDBAL as a embeded library you might want to control it's build options, for example you can run
|
||||
```
|
||||
set(BUILD_STATIC ON)
|
||||
```
|
||||
|
||||
before including the library in your project. This will set the library to be build in a static mode.
|
||||
|
||||
Then you want to run something like this
|
||||
```
|
||||
add_subdirectory(pathTo/yourEmbedded/libraries/lmdbal)
|
||||
add_library(LMDBAL::LMDBAL ALIAS LMDBAL)
|
||||
...
|
||||
|
||||
target_link_libraries(yourTarget PRIVATE LMDBAL::LMDBAL)
|
||||
```
|
||||
|
||||
The headers are added as `PUBLIC` so you might not even need to `target_link_libraries` them
|
||||
|
||||
### Building
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user