premiere
/
premiere-libtorrent
2
2
Fork 1
Code Issues Pull Requests Releases Wiki Activity

added warning about the buggy strip option on Mac OS X to the build docs

This commit is contained in:
Arvid Norberg 2008-03-21 05:59:34 +00:00
parent c8416cc79e
commit f6a3e42ae7
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/building.html
View File

@ -166,6 +166,14 @@ as a shared library (DLL), since you will get separate heaps in the library
and in the client application. It will result in crashes and possibly link
errors.</p>
</div>
<div class="warning">
<p class="first admonition-title">Warning</p>
<p class="last">With boost-build V2 (Milestone 11), the darwin toolset uses the <tt class="docutils literal"><span class="pre">-s</span></tt> linker
option to strip debug symbols. This option is buggy in Apple's GCC, and
will make the executable crash on startup. On Mac OS X, instead build
your release executables with the <tt class="docutils literal"><span class="pre">debug-symbols=on</span></tt> option, and
later strip your executable with <tt class="docutils literal"><span class="pre">strip</span></tt>.</p>
</div>
<p>The build targets are put in a directory called bin, and under it they are
sorted in directories depending on the toolset and build variant used.</p>
<p>To build the examples, just change directory to the examples directory and

8
docs/building.rst
View File

@ -180,6 +180,14 @@ the runtime, but on windows you can do both. Example::
and in the client application. It will result in crashes and possibly link
errors.
.. warning::
With boost-build V2 (Milestone 11), the darwin toolset uses the ``-s`` linker
option to strip debug symbols. This option is buggy in Apple's GCC, and
will make the executable crash on startup. On Mac OS X, instead build
your release executables with the ``debug-symbols=on`` option, and
later strip your executable with ``strip``.
The build targets are put in a directory called bin, and under it they are
sorted in directories depending on the toolset and build variant used.