Re: [brlcad-devel] Compiling and using BRL-CAD in situ

2011-01-23 Thread Christopher Sean Morrison
On Jan 23, 2011, at 1:57 PM, Tom Browder wrote: > On Sun, Jan 23, 2011 at 09:13, Christopher Sean Morrison > wrote: >> On Jan 21, 2011, at 8:19 AM, Tom Browder wrote: >>> BTW, I have to add the configure option: >>> >>> --with-cxxflags='-Wno-ignored-qualifiers' >>> >>> to get past openNURBS

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Christopher Sean Morrison
On Jan 23, 2011, at 1:39 PM, Tom Browder wrote: > Don't forget also that docbook is very modular. in my current > documentation system I use a Perl script to generate the text from > running programs with various options, capture the output to a text > file, and xi:include it into my docbook xml

Re: [brlcad-devel] Compiling and using BRL-CAD in situ

2011-01-23 Thread Tom Browder
On Sun, Jan 23, 2011 at 09:13, Christopher Sean Morrison wrote: > On Jan 21, 2011, at 8:19 AM, Tom Browder wrote: >> BTW, I have to add the configure option: >> >>  --with-cxxflags='-Wno-ignored-qualifiers' >> >> to get past openNURBS on a trunk build.  Am I [d]oing something wrong? > That is biza

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Tom Browder
On Sun, Jan 23, 2011 at 12:04, Christopher Sean Morrison wrote: > > On Jan 23, 2011, at 12:51 PM, Tom Browder wrote: > >>> The gist I'm going for is to make each command a self-contained plugin >>> similar to how primitives are implemented with various callbacks.  One of >>> those would be the usa

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Christopher Sean Morrison
On Jan 23, 2011, at 12:51 PM, Tom Browder wrote: >> The gist I'm going for is to make each command a self-contained plugin >> similar to how primitives are implemented with various callbacks. One of >> those would be the usage function like you can presently find in the header, >> #3, #4, and #5

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Tom Browder
On Sun, Jan 23, 2011 at 11:37, Christopher Sean Morrison wrote: ... > The gist I'm going for is to make each command a self-contained plugin > similar to how primitives are implemented with various callbacks.  One of > those would be the usage function like you can presently find in the header, >

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Christopher Sean Morrison
On Jan 23, 2011, at 10:44 AM, John Anderson wrote: > After modifying the "concat" command, I began updating the related > documentation. After a little searching, I found these files containing > documentation for the "concat" command: Yeah, it's a mess and you missed one of them. LIBGED

Re: [brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread Clifford Yapp
My first instinct would be to reply that if it's an MGED command it should get a docbook man page in doc/docbook/system/mann/en for user level docs and in-code documentation for the source code level stuff. The MGED help system... not sure about that one. Ideally it could extract some subset of th

[brlcad-devel] Multiple Documentations of the Same Command

2011-01-23 Thread John Anderson
After modifying the "concat" command, I began updating the related documentation. After a little searching, I found these files containing documentation for the "concat" command: 1. The "in code" documentation (concat.c) 2. The mged html manual (mged_cmd_index.html) 3. The mged comm

Re: [brlcad-devel] Compiling and using BRL-CAD in situ

2011-01-23 Thread Christopher Sean Morrison
On Jan 21, 2011, at 8:19 AM, Tom Browder wrote: > BTW, I have to add the configure option: > > --with-cxxflags='-Wno-ignored-qualifiers' > > to get past openNURBS on a trunk build. Am I foing something wrong? That is bizarre. Can you provide a build snippet showing the failure and compile

Re: [brlcad-devel] Bug in or around sh_billboard.c

2011-01-23 Thread Christopher Sean Morrison
On Jan 21, 2011, at 8:27 AM, Tom Browder wrote: > cc1: warnings being treated as errors > sh_billboard.c:125:12: error: pointer of type 'void *' used in subtraction > /bin/bash ../../libtool --tag=CC --mode=compile gcc-4.5.1 > -DHAVE_CONFIG_H -I. -I../../include -pedantic -W -Wall -Wundef > -W