Re: [brlcad-devel] basic problems.

[Christopher S. M. <br...@ma...>]

On Apr 7, 2012, at 7:30 AM, Karl Edler wrote:

> 1) There seems to be a difference in operation between the tools provided by brlcad-7.20.4-0_i386.deb and brlcad-7.20.4-0_amd64.deb.

>From a development standpoint (since you are e-mailing brlcad-devel and not brlcad-users), those release builds are several months old.  Would you retry with a more recent SVN checkout to see if it's perhaps an issue that's already been fixed?

There have been hundreds of changes including some to the NMG code being used for tessellation during g-stl, even with that being our last posted distribution.

>           In each case the file /src/librt/primatives/nmg/nmg_tri.c gave warnings that were treated as errors and the build stopped.

That is undoubtedly already fixed, but you can disable strict build behavior to get past those build warnings.  Pass -DBRLCAD_ENABLE_STRICT=OFF during cmake and it will no longer treat warnings as errors.

>           I suggest that the brlcad source be put in a state that it can be compiled right out of the box by a somewhat competent programmer. I am will to help with this but I am not sure where to start. What do you usually do to compile this code???

That is the intent already.  The nature of strict flags, however, makes that a rather complex proposition since warnings will vary greatly depending on compilation settings, compiler versions, platform type, and more.  It obviously "worked for us" when it was posted, compiling cleanly, or it would not have been posted... :)

If you get an SVN checkout and make any changes that help the build succeed, running "svn diff > my_changes.patch" will save your changes to a file that can be posted to our patched tracker: https://sourceforge.net/tracker/?func=add&group_id=105292&atid=640804 

Cheers!
Sean