diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2018-10-18 12:21:10 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2018-10-18 12:21:10 +0200 |
| commit | 4a0568b8b884d954944c89b3c52b756a3d6c7dc9 (patch) | |
| tree | 60805fdfcabab680fc13416fba136844ac10cfae /doc | |
| parent | 6feaa13453d5071f340f405075c3ea880dc23ac1 (diff) | |
Add note to manual on creating binless libraries with bdep-new
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.cli | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/doc/manual.cli b/doc/manual.cli index 32c441e..6ea4208 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -2598,7 +2598,17 @@ rather a binary-less, or \i{binless} for short, static or shared library. So, theoretically, it is possible to have a library that has a binless static and a binary-full (\i{binfull}) shared variants. Note also that binless libraries can depend on binfull libraries and are fully supported where the -\c{pkg-config(1)} functionality is concerned.| +\c{pkg-config(1)} functionality is concerned. + +If you are creating a new library with \l{bdep-new(1)} and are certain that it +will always be binless and in all configurations, then you can produce a +simplified \c{buildfile} by specifying the \c{binless} option, for example: + +\ +$ bdep new -t lib -l c++,binless libheader-only +\ + +| Let's now turn to the second subject of this section and the last unexplained bit in our \c{buildfile}: shared library versioning. Here is the relevant |