Changes between Version 4 and Version 5 of StartModDev

Timestamp:

Nov 29, 2012, 12:46:58 AM (10 years ago)

Author:

Beman Dawes

Comment:

Tweak wording and add Creating the foo library

StartModDev

@@ -1 +1 @@
 = Getting Started with Modularized Boost Library Development =
 
-|| This is a work in process ||
+|| This is a work in progress ||
 
 == Prerequisites ==
@@ -14 +14 @@
 == Overview ==
 
- * The Boost repository itself treats your library as a sub-module, i.e. a link to a particular release in your library's public GitHub repository.
- * Your library has a "master" branch for development work, and a "release" branch for your releases, which occur asynchronously from Boost releases. You may also have other branches, but that's up to you.
- * You (and the rest of your team) do day-to-day development using private repositories on your local machines. You push changes from these local private repos up to the public repo whenever you want. The local repos may have private branches that are never pushed to the public repo.
+ * Your library has its own public repository that has a "develop" branch for development work, and a "master" branch for your releases, which occur asynchronously from Boost releases. You may also have other branches, but that's up to you.
+ * The Boost super project has its own public repository. It treats your library as a sub-module, i.e. a link to a particular release in your library's public GitHub repository.
+ * You (and the rest of your team) do day-to-day development using private repositories on your local machines. You push changes from these local private repos up to your library's public repo whenever you want. The local repos may also have private branches that are never pushed to the public repo.
  * Your library's directory structure conforms to [http://www.boost.org/development/requirements.html#Directory_structure Boost directory structure conventions], so both users and automatic processes can find header files, test files, build configurations, and the like. Beyond the conventions, your library's directory structure is up to you. 
  
-== Header Directories ==
+== Directory Structure ==
 
-For Modularized Boost, header files are placed in a {{{include/boost}}} header hierarchy within your main directory. Here is what a very simple library named foo would look like:
+For Modularized Boost, header files are placed in a {{{include/boost}}} header hierarchy within your main directory. Here is what a very simple header-only library named {{{simple}}} would look like:
 
 
 {{{
-     foo
+     simple
        include
          boost
-           foo
-             foo.hpp
+           simple
+             twice.hpp
        test
-         foo_test.cpp
+         twice_test.cpp
          Jamfile.v2
        index.html   
 }}}
 
+== Creating the {{{simple}}} library ==
+