github/ocf
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Slightly reword README.md

Browse Source 
Signed-off-by: Robert Baldyga <robert.baldyga@intel.com>
This commit is contained in:
Robert Baldyga 2018-12-28 09:44:21 +01:00
parent 1b0b2597d3
commit 1ba0955ebc
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -34,17 +34,17 @@ cd ocf
## Deployment ## Deployment
OCF doesn't compile as separate library. It's designed to be included into another OCF doesn't compile as separate library. It's designed to be included into another
software. For this purpose OCF Makefile provides two useful targets for deploying software stack. For this purpose OCF provides Makefile with two useful targets for
OCF source into target directories. Assuming OCFDIR is ocf directory, and SRCDIR and deploying its source into target directories. Assuming OCFDIR is OCF directory, and
INCDIR are your source and include directories, you can use following commands to SRCDIR and INCDIR are respectively your source and include directories, use following
deploy OCF into your project: commands to deploy OCF into your project:
~~~{.sh} ~~~{.sh}
make -C $OCFDIF src O=$SRCDIR make -C $OCFDIF src O=$SRCDIR
make -C $OCFDIF inc O=$INCDIR make -C $OCFDIF inc O=$INCDIR
~~~ ~~~
This by default will not copy OCF source files but create symbolic links to them, By default this will not copy OCF source files but create symbolic links to them,
to avoid source duplication and allow for easy OCF code modification. If you prefer to avoid source duplication and allow for easy OCF code modification. If you prefer
to copy OCF source files (e.g. you don't want to distribute whole OCF repository to copy OCF source files (e.g. you don't want to distribute whole OCF repository
as your submodule) you can use following commands: as your submodule) you can use following commands: