whitequark changed the topic of #solvespace to: SolveSpace--parametric 2d/3d CAD · latest version 2.3 · http://solvespace.com · code at https://github.com/solvespace/solvespace · logs at https://irclog.whitequark.org/solvespace
<tristero> nvm, I worked around it by moving my constraints earlier in the sequence
<GitHub> [solvespace] foror commented on issue #276: I'm not an expert in this topic, but probably there needs to add gcc: sudo apt install gcc cmake zlib1g-dev libpng-dev libcairo2-dev libfreetype6-dev sudo apt install libjson-c-dev libfontconfig1-dev libgtkmm-3.0-dev libpangomm-1.4-dev libgl-dev libglu-dev libspnav-dev https://github.com/solvespace/solvespace/issues/276#issuecomment-320825910
<GitHub> [solvespace] foror commented on issue #276: I'm not an expert in this topic, but probably there needs to add **gcc**: sudo apt install gcc cmake zlib1g-dev libpng-dev libcairo2-dev libfreetype6-dev sudo apt install libjson-c-dev libfontconfig1-dev libgtkmm-3.0-dev libpangomm-1.4-dev libgl-dev libglu-dev libspnav-dev https://github.com/solvespace/solvespace/issues/276#issuecomment-320825910
<whitequark> tristero: sorry, constrain -> comment
<travis-ci> solvespace/solvespace#431 (master - 16540b1 : whitequark): The build is still failing.
<tristero> are there any best practices for keeping designs in git? and is there a non-interactive way to update a top-level slvs file if some of its component parts change?
<whitequark> not really, and not in version 2.3 unfortunately
<tristero> it would be useful as part of a Makefile for objects
<whitequark> sure
<whitequark> it's present in the master branch
<whitequark> called solvespace-cli
<whitequark> I think I'll release that sooner than I wanted before, call it 2.4 maybe
f8l has quit [Quit: Environment change]
f8l has joined #solvespace