2
0
mirror of https://github.com/boostorg/website.git synced 2026-01-22 05:42:52 +00:00
Files
website/community/sandbox.html
2020-04-10 17:37:30 -04:00

134 lines
4.7 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Boost Sandbox</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="icon" href="/favicon.ico" type="image/ico" />
<link rel="stylesheet" type="text/css" href=
"/style-v2/section-community.css" />
<!--[if IE 7]> <style type="text/css"> body { behavior: url(/style-v2/csshover3.htc); } </style> <![endif]-->
</head><!--
Note: Editing website content is documented at:
https://www.boost.org/development/website_updating.html
-->
<body>
<div id="heading">
<!--#include virtual="/common/heading.html" -->
</div>
<div id="body">
<div id="body-inner">
<div id="content">
<div class="section" id="intro">
<div class="section-0">
<div class="section-title">
<h1>Boost Sandbox</h1>
</div>
<div class="section-body">
<p>When boost was developed using subversion, the Boost Sandbox
contained unreviewed code that is intended to eventually become
a part of the Boost libraries. New libraries should be
developed separately as <a href=
"https://svn.boost.org/trac/boost/wiki/ModularBoost">git
modules</a>, and existing projects should be <a href=
"https://svn.boost.org/trac/boost/wiki/ExtractSandbox">moved to
GitHub</a>. The sandbox remains as a historical record.</p>
<h2>Accessing the Boost Sandbox</h2>
<p>The Boost Sandbox lives at <a href=
"https://svn.boost.org/svn/boost/sandbox">https://svn.boost.org/svn/boost/sandbox</a>
within the old Boost Subversion repository.</p>
<h2>Organization</h2>
<p>Because there were typically many projects in the sandbox at
any one time (in various stages of development), the sandbox
should have been organized by project. Each project should have
had its own subdirectory inside <tt>sandbox</tt>. For example,
an XML library would reside in <tt>sandbox/xml</tt>. Inside
that project-specific subdirectory, the project would be
organized like any other Boost library, with a <tt>boost</tt>
subdirectory (for headers) and <tt>libs</tt> subdirectory (for
source code, build files, and documentation). Our hypothetical
XML project would likely have had the following structure:</p>
<ul class="tree">
<li>
<tt>sandbox/xml/</tt>
<ul>
<li>
<tt>boost/</tt> - Contains <tt>xml.hpp</tt>, which
includes all of the headers from <tt>xml/</tt>
<ul>
<li><tt>xml/</tt> - Contains Boost.XML headers</li>
</ul>
</li>
<li>
<tt>libs/</tt>
<ul>
<li>
<tt>xml/</tt>
<ul>
<li><tt>build/</tt> - Contains <tt>Jamfiles</tt>
to build Boost.XML</li>
<li><tt>doc/</tt> - Contains documentation for
Boost.XML</li>
<li><tt>src/</tt> - Contains Boost.XML compiled
source files</li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<p>Many existing projects in the sandbox didn't follow this
structure, opting to place headers in <tt>sandbox/boost</tt>
and supporting files in <tt>sandbox/libs</tt>.</p>
</div>
</div>
</div>
</div>
<div id="sidebar">
<!--#include virtual="/common/sidebar-common.html" -->
<!--#include virtual="/common/sidebar-community.html" -->
</div>
<div class="clear"></div>
</div>
</div>
<div id="footer">
<div id="footer-left">
<div id="revised">
<p>Revised $Date$</p>
</div>
<div id="copyright">
<p>Copyright Rene Rivera 2007.</p>
</div><!--#include virtual="/common/footer-license.html" -->
</div>
<div id="footer-right">
<!--#include virtual="/common/footer-banners.html" -->
</div>
<div class="clear"></div>
</div>
</body>
</html>