On Tue, Jul 14, 2020 at 11:00 AM Christopher Sean Morrison via brlcad-devel
wrote:
> Sorry, I may need some background — what problem is being solved? We
> require Tcl now to build the samples, always have, and I’ve not exactly
> seen that as a problem. I would leave well enough alone there. C
Sorry, I may need some background — what problem is being solved? We require
Tcl now to build the samples, always have, and I’ve not exactly seen that as a
problem. I would leave well enough alone there. Cmake’s done a great job with
the dependency tracking. I wasn’t really envisioning Tcl g
Unfortunately, that would mean we would require Tcl to build the db sample
models (unless we just convert them to .g files in the repository, rather
than running asc2g on them during the build... that would be my own
preference.)
Cliff
On Tue, Jul 14, 2020 at 9:42 AM Christopher Sean Morrison via
Or option4, just let asc2g/g2asc be v4’s graveyard as-is? It would be nice if
libgcv could read v4 asc from a historical perspective, but not a big deal to
me. All for fixing any bugs of course.
Cheers!
Sean
> On Jul 13, 2020, at 7:21 PM, Clifford Yapp wrote:
>
> I hit that because I was
I hit that because I was trying to use lcov to build up a .g file that
would hit most of the g2asc v4 code paths to get set for testing the libgcv
translation of the asc logic (or at least more than moss.g).
Even without the rhc I can't round trip the file, unfortunately... Not sure
whether to try
