Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
D
dlib
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
钟尚武
dlib
Commits
940d104a
Commit
940d104a
authored
Sep 27, 2015
by
Davis King
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Cleaned up docs
parent
ed644551
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
28 deletions
+0
-28
howto_contribute.xml
docs/docs/howto_contribute.xml
+0
-28
No files found.
docs/docs/howto_contribute.xml
View file @
940d104a
...
...
@@ -465,34 +465,6 @@ for (int i = 0; i < my_std_vector.size(); ++i)
of the dlib supported platforms and have their project build without
needing to mess with anything.
</p>
<p>
It is also important to know that dlib is mostly a header-only library.
This is primarily a result of the heavy use of C++ templates. Because of this,
in many cases, all that is needed to use the library is to
add dlib into a compiler's include search path. However, the most important
reason you need to know this is so you don't hassle me about providing a
"shared library" version of dlib. :)
</p>
<p>
This point deserves some explaining. When you write a piece of
software that links against a shared library you need two things. First,
you need the shared library object files and second you need the header files
for the library itself so you can #include them in your application. However,
since nearly all the code in dlib is
<i>
in the header files
</i>
there isn't
any point in distributing it as a shared library.
</p>
<p>
There are also a lot of technical problems with C++ shared libraries in general.
You can read about shared libraries on
<a
href=
"http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html"
>
this page
</a>
for more details. If you still think C++ template libraries like dlib should be built as
shared libraries then you should refer yourself to the following documents which
have been submitted to the C++ standards committee:
<a
href=
"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2316.pdf"
>
N2316: Modules in C++
</a>
,
<a
href=
"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1496.html"
>
N1496: Draft Proposal for
Dynamic Libraries in C++
</a>
, and
<a
href=
"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2425.html"
>
N2425: Minimal Dynamic Library Support
</a>
.
</p>
</ul></li>
<li>
<b>
Don't make assumptions about how objects are laid out in memory.
</b>
<ul>
<p>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment