irclog2html for #brlcad on 20100203

01:00.20starseekerbrlcad: well, except when we require something newer than the distro has packaged
01:02.05``Erikdebian stable used to be notorious for being a few years behind, I used 'testing' when I ran debian servers...
01:13.56starseekerWell, that figures.
01:14.30starseekerLooks like the whole thing of mixing multiple raytracing threads and Tcl interps is going to have to be handled with some care
01:15.16starseekerIf I'm understanding right, the initial success of the framebuffer code on non-corefoundation X11 was more accidental than a consequence of intended system features
01:17.27starseekerhow annoying
01:26.38poolioStattrav: (really delayed reply), but the undergrad graphics course at CMU
01:36.23pooliobrlcad: Have you ever played around with signed distance functions?
01:54.10brlcadstarseeker: more importantly, Tcl should not be involved in the raytracing->framebuffer process
01:59.34brlcadpoolio: not much
01:59.51brlcadthey're very much related to the way we solve implicit primitives, though
02:00.32brlcadjust a bit more generalized (or a different characterization of the surface as a function)
02:00.52brlcaddynamic implicit surfaces
02:34.34starseekerbrlcad: uh... considering we're using tcl/tk mechanisms to draw the pixels to the framebuffer, and using a Tk_Photo as the image repository...
02:35.49starseekerthe raytracing process generates the lines of data, but it's up to tcl/tk to actually draw it
02:40.44starseekermy understanding of the problem was we have (say) 8 threads, each generating their own little piece of the puzzle, and calling tk_write to get it on the framebuffer.  However, since tcl/tk limits things to one thread per interp, it was getting lots of nonsensical stuff when trying to do the update call
02:40.52brlcadah, you mean the new Tk framebuffer, I thought you were just trying to get the existing X11 framebuffer working with the new Tk
02:40.58starseekeroh, no :-)
02:42.42starseekerjust a "does this crash" test, until I get it on a Mac
02:44.00starseekerin some ways, it's almost worse when something accidently works
02:44.07brlcadso then am wondering since you did a fairly major upgrade, whether the previous still works
02:45.06brlcadmm.. pretty much certain that I'm not going to be driving tomorrow.. already have about three inches here
02:45.27brlcadcoming down nice really nice
02:46.32starseekerI believe it works if you compile with --disable-core something or other
02:46.39starseekeryeah, getting a lot here too
02:47.42starseekerah, --disable-corefoundation
02:47.49starseekerbut of course that rules out AquaTk
02:49.05starseekerthe whole tcl/tk/itcl/itk upgrade caused other problems - MGED doesn't start in dmtogl branch at the moment, even if you do manage to compile it
02:49.34starseekerI had to hand feed tcl a final gcc compile line that linked in our libz .o files in lu of theirs
02:49.54starseekerif their build logic has a concept of an external libz I haven't found it yet
02:50.21starseekerand other fun
02:51.10``Erikyeesh, I may be snowed in tomorrow as well, doubt they'll plow in time O.o
02:51.44starseekernothing insurmountable I'm sure, but a headache
02:51.50starseeker``Erik: yeah, I'm thinking that too
02:52.17starseekereven if I dig the driveway out, I'm not equipped to deal with this kinda stuff unplowed
02:58.51starseekerand they say there's a WORSE storm that may show up at the end of the week?
02:58.54starseekerblegh
03:00.56``Erikup to 40 tomorrow, snow on friday(38)/saturday(31), so'z it might not be all that bad
03:06.31starseekerah, above freezing will help
03:09.39``Erikhttp://www.europeanfecalstandardsandmeasurements.org/  O.o
03:10.15starseekeruh...
03:10.44``Eriksouth park links
03:11.23starseekerah, that figures
03:29.43louipchow fast?
03:29.55starseekerprobably not invented yet
03:30.07louipchah
03:30.23louipcare you trying to break the latest crypto?
03:30.30starseekermine makes hard work with the docbook pdf stuff, especially when there are hundreds of 'em
03:30.50louipcaarg
03:31.22louipcyeah good idea
03:31.25louipcdefinitely
03:32.42louipcI wish there was a better format
03:35.24louipcbut then we'll need to power our computers by nuclear fusion or something :/
03:35.28starseekerhehe
03:35.38starseekeryou say that like it's a bad thing :-))
03:36.45starseekeraannnnd... Tcl_Mutex just sits there when doing a raytrace
03:38.02louipcwell, seems like a waste of energy just to watch youtube or whatever
06:42.26*** join/#brlcad Stattrav (~Stattrav@202.3.77.161)
07:42.58*** join/#brlcad PhurlIpv4 (~mdupont@cl-1773.dus-01.de.sixxs.net)
09:45.58*** join/#brlcad Elrohir (~kvirc@p5B14962D.dip.t-dialin.net)
10:35.51*** join/#brlcad |Elrohir| (~kvirc@p5B149B3D.dip.t-dialin.net)
11:36.05starseekerah, well - roads plowed, driveway shoveled, wheee
11:43.31starseekererahum.  brlcad, do you know if we build tcl with --enable-threads ?  If not, could we?
11:56.28*** join/#brlcad d_rossberg (~rossberg@BZ.BZFLAG.BZ)
11:56.44*** join/#brlcad Phurl (~mdupont@ip-81-210-228-126.unitymediagroup.de)
12:05.20*** join/#brlcad d_rossberg (~rossberg@BZ.BZFLAG.BZ)
13:38.31*** join/#brlcad ``Erik (~erik@c-69-140-109-104.hsd1.md.comcast.net)
14:15.09brlcad<PROTECTED>
14:15.17brlcadthink it's just the defaults
14:15.30brlcadmostly
15:54.38CIA-43BRL-CAD: 03brlcad * r37532 10/brlcad/trunk/HACKING: add a (temporary) section on refactoring individual files. highly overlaps with the style section so .. the doc needs some refactoring of its own.
17:19.37*** join/#brlcad ibot (ibot@rikers.org)
17:19.37*** topic/#brlcad is BRL-CAD Open Source Solid Modeling || http://brlcad.org || http://sf.net/projects/brlcad || #brlcad logs at http://ibot.rikers.org/%23brlcad/ || Happy Open Source Anniversary! (December 21st) || Release 7.16.4 in prep, should be posted 20100114
17:22.15*** join/#brlcad yukonbob (1000@s142-179-54-198.bc.hsia.telus.net)
18:37.00``Erik*yawn*
18:40.56``Erikd-lo: was 'darkstar' the thing you were looking at for game infrastructure?
18:42.35``Erikstarseeker: src/rt/viewedge.c lines 533, ~770, 779... everything that uses 'bif'
18:43.48``Erikviewinit and viewend are main thread functions, view_eol is a worker thread func, iirc
18:47.44starseekerhrm
18:48.46``Erikthat semaphore probably isn't needed
19:28.14starseekerhehe
19:28.33CIA-43BRL-CAD: 03erikgreenwald * r37533 10/brlcad/trunk/src/librt/primitives/nmg/nmg_tri_mc.c: note position in table
19:34.46Stattrav``Erik: :O
19:38.09*** join/#brlcad mafm (~mafm@99.Red-83-45-252.dynamicIP.rima-tde.net)
20:20.01``Erikcmd for altering bot (orientation, plate mode, whatever)
20:32.57brlcadque?
20:33.37``Erikattr set somethingorrather, but I don't know the magic names
20:34.11brlcadcat regress/bots.sh
20:34.14brlcadform bot
20:34.26brlcadget somebot orient
20:35.39brlcadbot_sync makes all normals point one way, bot_flip makes them all point the opposite way
20:38.54``Erikdang input bug :/
20:41.13``Erikveeeedddyyy iiiinterestink
20:41.17``Erikbot_merge btw
20:43.38``Erikthnx, now'z I have some functions to try to visualize O.o
20:56.59brlcadwhat about bot_merge?
20:58.17brlcadthat combines bot data sets together, the script shows it in action too along with then recondensing if you have overlapping bots
20:58.34brlcadfg
20:59.01``Erikdid, not sure if my bad data is from my nmg construction or the table... gonna build a 'put' command in a bit
21:00.48CIA-43BRL-CAD: 03brlcad * r37534 10/brlcad/trunk/src/librt/CMakeLists.txt: add new generic.c file
21:15.36mafmhuh
21:16.08mafmbrl-cad doesn't use even numbers not even (no pun intended) for bugfix releases?
21:16.38``Erikeven is a release, odd is a development phase
21:20.46mafmI knew that for the "minor", second component
21:20.58mafmbut didn't know that I applied to the third one
21:35.52mafmhmm
21:36.09mafmhow would I compile without the stuff in src/other?
21:36.29mafmother than disabling it one by one
21:37.53``Erikif it can detect stuff, it should infer the --disable-
21:39.03brlcadmafm: --disable-all will turn everything off (and configure will then abort if it doesn't find something it needs)
21:39.05mafmyep, but I want to force the disable for all 3rd party software, to try to evaluate the difficulty to get brl-cad into debian
21:39.30mafmmm, good
21:39.35mafmthx
21:40.04*** join/#brlcad R0b0t1 (~Enigma@unaffiliated/r0b0t1)
21:40.21brlcadmafm: options are described in detail in the INSTALL file
21:40.48brlcadyou will probably have to build at least openNURBS and a couple others
21:41.37mafmurt
21:41.45brlcadI believe I summarized things in the gentoo portage tracker a little whileback regarding where things are at
21:52.45mafmdid it ever got into gentoo?
21:54.14Tecanhttp://www.missoulian.com/news/state-and-regional/article_9db5e032-0a22-11df-95bc-001cc4c002e0.html
21:54.22mafmconfigure: WARNING: The floating point implementation does not seem to be IEEE 754                                                                      
21:54.32mafmcue the Pentium rounding error jokes... :P
21:59.13mafmit doesn't detect the tcl libraries or something :|
21:59.36*** part/#brlcad Tecan (~fsadf@unaffiliated/unit41)
22:03.20mafm| #ifdef HAVE_TCL_H
22:03.21mafm| #  include <tcl.h>
22:03.23mafm| #endif
22:03.44mafmit seems that, by disabling-all, this is not defined and thus the test fails (?)
22:08.40brlcada lot of systems don't seem to be IEEE 754 compliant (and nothing requires them to be really)
22:08.48brlcadnot usually an issue
22:09.46brlcadthat define comes from earlier tcl.h header checks, so if it fails, something is either not installed, not compatible, or search flags aren't set right
22:12.00brlcadall of the checks are pretty independent, there are header checks, library checks, and then functionality (make sure it works) checks
22:12.17brlcadall three have to pass
22:15.23mafmwell, it's there: /usr/include/tcl8.4/tcl.h
22:15.42brlcadand how does it know to look there for it?
22:16.40brlcadi.e., "not compatible, or search flags aren't set right"
22:24.22``Erikiiiiinteresting patterns
22:25.53``Erikiirc, there's a way to convince the intel fpu to do zomfg 754/854 at the cost of performance, but the only bit it really comes up is the ntohd htond calls
22:27.18CIA-43BRL-CAD: 03bob1961 * r37535 10/brlcad/trunk/src/libged/ (54 files): Quell a few warnings when compiling 64-bit Windows.
22:29.32brlcadyeah, ntohd and htond is the only scary bit, if the byte representation couldn't be parsed by a different compile
22:31.15brlcadheh, thanks bob :)
22:31.28``Erikbrlcad: do you have a gtk2 enabled machine handy?
22:31.43brlcadhm, lemme check
22:33.19``Erikhttp://brlcad.org/~erik/oddnmg.g http://brlcad.org/~erik/oddbot.g  (rt will crap itself on oddnmg.g, but will kinda sorta render oddbot.g... both results of the same g-nmg, just the -b flag and name)
22:33.49``Erikisst will crank them up and assume unoriented, and allow ya to look around a bit :D
22:34.15``Erikneat stuff, ainnit? I'll be busy tomorrow
22:34.20brlcadwell that's promising
22:34.58``Erikthere're some details that strike me as vrrrry odd and looking closely with isst
22:35.42``Erikhopefully, the table I stole is correct :/
22:39.36``Erikaaanyways, time to roll out, bbi45m O.o
22:39.41brlcadcya
22:39.47brlcadyeah, no gtk2 handy
22:48.09mafm--tcl-includes=/usr/include/tcl8.5/
22:48.11mafmconfigure: error: unrecognized option: --tcl-includes=/usr/include/tcl8.5/
22:52.25brlcadthat looks like an invalid configure option to me too
23:00.29CIA-43BRL-CAD: 03bob1961 * r37536 10/brlcad/trunk/src/liboptical/ (material.c sh_stxt.c shade.c): Quell a few warnings when compiling for 64-bit Windows.
23:15.31mafmso what does this means, then?
23:15.36mafmX features:
23:15.37mafm<PROTECTED>
23:16.02mafmI expect to use "--tcl-includes=DIR" when I want to include that directory
23:38.01CIA-43BRL-CAD: 03bob1961 * r37537 10/brlcad/trunk/include/bu.h: Quell a few warnings when compiling for 64-bit Windows.
23:41.53CIA-43BRL-CAD: 03bob1961 * r37538 10/brlcad/trunk/src/libpkg/pkg.c: Quell a few warnings when compiling for 64-bit Windows.

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with infobot logs, split per channel, etc.