On 1 November 2013 09:54, Christopher Sean Morrison <[email protected]> wrote: > If you have coding experience, you should not shy away from reading and > understanding that output. The information is right there rather plainly in > the output: "variable X is set but not used" and "all warnings being treated > as errors".
I guess I should have taken more time to understand the error rather than posting it here first. > It says there is a variable. It's in the obr.c file. It's getting set to > some value apparently, but that variable is then not being used. If it's not > used, why did we bother setting it? So a warning is getting issued by the > compiler. The current mode of compilation turns all warnings into errors. > Compilation stops. > > The error is resolved by 1) removing the unused variable(s), 2) using the > variable(s), or 3) don't treat warnings as errors. > > Since you had to ask this question, I presume #3 is most suitable to your > situation. The INSTALL file says the BRLCAD_ENABLE_STRICT option controls > that mode of compilation, so you can run cmake with the > -DBRLCAD_ENABLE_STRICT=NO argument and then rerun make. I appended '-DBRLCAD_ENABLE_STRICT=NO' to cmake and it ran successfully. Thanks for making it much clearer. -- Gurjot Singh Blog: http://bhattigurjot.wordpress.com ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
