[subversion] sandbox template
Hi, There was a mention earlier of adding a template for boost projects in the sandbox - I have just started making such a template after getting somewhat acquainted with the boost build process. It basically consists of * a basic directory/file structure with a simple include-only library, test, example, doc built from doxygen and boostbook, as well as vc8 and xcode IDE projects which invoke bjam to build. * a (currently, windows .bat) script which (given a library id) copies the directory/file structure, renames where appropriate, and find/replaces the contents using sed. When I am (reasonably) done, should I add this to the sandbox (or, would someone like to review it before it is added?)? I'm sure that it will need a lot of improvement because my knowledge of the build system is pretty bleak (I basically got things to a point where it somehow works), but it might serve as an OK starting point for an expert to flesh things out. Stjepan
Stjepan Rajko wrote:
There was a mention earlier of adding a template for boost projects in the sandbox - I have just started making such a template after getting somewhat acquainted with the boost build process.
And you beat me to it by a few hours :-) (Still posting the BoostCon07 pictures for the last day)
It basically consists of * a basic directory/file structure with a simple include-only library, test, example, doc built from doxygen and boostbook, as well as vc8 and xcode IDE projects which invoke bjam to build.
Hm, not sure I would have included project files.
* a (currently, windows .bat) script which (given a library id) copies the directory/file structure, renames where appropriate, and find/replaces the contents using sed.
Nice... But sed isn't exactly a standard tool for Windows. Or are you using it only in MacOSX?
When I am (reasonably) done, should I add this to the sandbox (or, would someone like to review it before it is added?)? I'm sure that it will need a lot of improvement because my knowledge of the build system is pretty bleak (I basically got things to a point where it somehow works), but it might serve as an OK starting point for an expert to flesh things out.
Adding it is likely a good idea, since I could then fill in any missing pieces. But perhaps picking a name that clearly marks it as in-progress would be good. Then it can be renamed to a final name when it's ready. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On 5/20/07, Rene Rivera <grafikrobot@gmail.com> wrote:
Stjepan Rajko wrote:
It basically consists of * a basic directory/file structure with a simple include-only library, test, example, doc built from doxygen and boostbook, as well as vc8 and xcode IDE projects which invoke bjam to build.
Hm, not sure I would have included project files.
I hope it doesn't hurt to have them in there... in learning how to do all this I found myself losing hours over the dumbest mistakes, so hopefully a working example saves people time in the future. Seems like many people are using various IDEs, and if not I guess it's always easy to remove things from the created template.
* a (currently, windows .bat) script which (given a library id) copies the directory/file structure, renames where appropriate, and find/replaces the contents using sed.
Nice... But sed isn't exactly a standard tool for Windows. Or are you using it only in MacOSX?
It was a random choice. If you have a different suggestion, I'd be happy to use it instead.
When I am (reasonably) done, should I add this to the sandbox
Adding it is likely a good idea, since I could then fill in any missing pieces. But perhaps picking a name that clearly marks it as in-progress would be good. Then it can be renamed to a final name when it's ready.
Good idea! I'll add something tomorrow (monday). Stjepan
Stjepan Rajko wrote:
On 5/20/07, Rene Rivera <grafikrobot@gmail.com> wrote:
Stjepan Rajko wrote:
* a (currently, windows .bat) script which (given a library id) copies the directory/file structure, renames where appropriate, and find/replaces the contents using sed. Nice... But sed isn't exactly a standard tool for Windows. Or are you using it only in MacOSX?
It was a random choice. If you have a different suggestion, I'd be happy to use it instead.
If you really want a script to work for just about everyone around here, use Python. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
On 5/20/07, Rene Rivera <grafikrobot@gmail.com> wrote:
If you really want a script to work for just about everyone around here, use Python.
Good call! Using Python completely circumvented about a dozen other problems I was anticipating :-) Like how to generate UUIDs for new MSVC projects. Anyway, I threw something together and commited it to the sandbox under /template_under_construction/. Docs are at: http://dancinghacker.com/code/template/ Feel free to make any changes, or let me know what should be changed. I'm expecting most of the setup will need to be revised in some way or another, since getting the boost process figured out was somewhat of a blind trial-and-error process for me. In its current state, maybe it doesn't even build except on my machine... Also, just to forewarn you of what the doc build is doing with doxygen - it is both including the xml generated by doxygen into the reference section of the main documentation, and having doxygen build its own HTML directly which is then linked from the main documentation. I know it's ridiculous to do both, but the current script doesn't implement any functionality related to options (which is what might be a good thing regarding the docs - allowing the choice of quickbook only vs. quickbook with doxygen reference vs. quickbook with link to doxygen pages vs. doxygen only). Or whatever... Thanks, Stjepan
participants (2)
-
Rene Rivera -
Stjepan Rajko