| 01:02.27 | mpictor | awesome, hoiji! :D |
| 03:50.27 | *** join/#stepcode hoiji (671b082a@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.42) |
| 05:41.13 | hoiji | Thanks brlcad :) |
| 11:42.22 | hoiji | Hi, How do I open .g files? |
| 11:48.24 | hoiji | I mean how do I view them |
| 11:57.58 | hoiji | One more question. How do I link my version of stepcode with the step-g converter? |
| 13:45.08 | mpictor | hoiji:for the latter, I guess you set BRLCAD_SC=OFF and replace the stepcode dir with yours |
| 13:45.20 | mpictor | http://svn.code.sf.net/p/brlcad/code/brlcad/trunk/src/other/stepcode/ |
| 13:45.45 | mpictor | so src/other/stepcode |
| 13:47.50 | mpictor | but starseeker and brlcad have messed with brlcad much more recently than I ;) |
| 14:14.56 | starseeker | hoiji: to open a .g file, use mged or archer (part of the BRL-CAD build) |
| 14:15.18 | starseeker | hoiji: the simplest approach is just to replace src/other/stepcode with the current stepcode |
| 14:15.31 | starseeker | (for that, you leave BRLCAD_SC set to ON) |
| 14:15.47 | starseeker | then the BRL-CAD build will also build stepcode |
| 14:16.32 | starseeker | I actually don't know if anyone has ever tried with a system stepcode - until relatively recently, that wasn't a likely thing to find in the wild |
| 14:17.03 | starseeker | (hence the stuff we're having to work through for OpenVSP - I still need to track down the SC_INSTALL_PREFIX issue) |
| 14:18.04 | starseeker | oh - in mged, once you've opened the .g file, you use the "tops" command to see what the toplevel objects are and the "draw" command to try drawing them |
| 14:18.23 | starseeker | for large NURBS objects, the latter step can take a minute. |
| 16:26.05 | hoiji | Oh thanks! btw I forget to tell you, when I tried step-g http://www.steptools.com/support/stdev_docs/stpfiles/ap203/weldment_asm_solid.stp |
| 16:26.14 | hoiji | I got a seg-fault |
| 16:27.46 | hoiji | (to be clear: until then I had not modified src/other/stepcode) |
| 16:28.38 | hoiji | When I tried a different file i.e http://www.steptools.com/support/stdev_docs/stpfiles/ap203/1797609in.stp step-g ran fine |
| 17:28.35 | *** join/#stepcode hoiji (671b082a@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.42) |
| 17:50.28 | *** join/#stepcode hoiji (671b082a@gateway/web/cgi-irc/kiwiirc.com/ip.103.27.8.42) |
| 18:23.00 | hoiji | hi it seems I am having some problems with the COMPILER FLAGS in the my version of stepcode. |
| 18:24.30 | hoiji | Basically the problem is related to -std=c++0x compiler flag not being passed to the src/other/stepcode |
| 18:25.06 | hoiji | -std=c++0x is needed as I make use of std::mutex in my code |
| 18:25.27 | hoiji | Is there any way I can change the flag in brlcad |
| 18:45.56 | starseeker | hoiji: erm |
| 18:47.39 | starseeker | as a quick hack, could you try something like set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} "-std=c++0x") in stepcode's toplevel? |
| 18:48.15 | starseeker | I don't know if we're going to want to rely on c++0x - that's a brlcad (Sean) question |
| 20:07.29 | *** join/#stepcode infobot (ibot@rikers.org) |
| 20:07.29 | *** topic/#stepcode is STEPcode - data exchange with the technologies of ISO10303 || http://stepcode.org || LOG http://ibot.rikers.org/%23stepcode/ |