Aha, you must be a prior OpenImageIO user. You need to 'svn update' and recompile your OIIO -- this code in OSL requires a recent change to the ParamValueList helper class that's part of OIIO. At

Building on Mac OS X (Darwin) seems to work and run but when I try most of the tests it seems to fail with a bus error For example (geomath) edit run.py to work with my local

I've just run it in gdb and got the following Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000001 0x0016a07d in

The "run.py" script takes arguments (which are passed when the testsuite is run). You want: cd testsuite/YOURTEST ./run.py . ../../build/ARCH (ARCH in your case is "macosx") Does that help? If

still getting the fails, If I do a make debug I get loads of boost Undefined symbols: errors (for example) Linking CXX shared library liboslexec.dylib Undefined symbols:

We're big fans of code reviews BEFORE committing into the trunk, and at SPI used ReviewBoard religiously while developing OSL. We're still trying to figure out how to do reviews the way we prefer,

Reviewers: , Message: Review at http://codereview.appspot.com/189060 Description: Bug introduced with r507 when I overhauled compound initializers in ASTvariable_declaration. Forgot one place where

LGTM http://codereview.appspot.com/189060

http://codereview.appspot.com/189060 Sorry, I can't quite seem to get the review comments to automatically get sent to this list. Do we care? Would you guys like to see every review-related email,

Hi, First, let me say thanks for releasing this as open source, it's looking very impressive. I'm working on the shading system in Blender and was looking into how this design compares to what I'm

Apparently I can't post here from my work address, so resending. Sorry if somebody gets a duplicate. Hi Brecht, I'm Alejandro Conty (jandro in the old blender days), we met several times at the

If it's just a case of the message bouncing because it doesn't know you (at work) are a member of the group, try signing up for a second googlegroups membership, using your work address, and check the

I hope you all can see from the traffic in the last few days that Imageworks is not merely planning to occasionally snapshot OSL and release it, but rather we are committed to developing the whole

http://codereview.appspot.com/189073 Ugh, still having trouble making it send all review emails to this list automatically. -- Larry Gritz l...@...

Status: New Owner: larrygritz CC: os...@... New issue 48 by larrygritz: texture() should take optional param for missing

Updates: Cc: larrygritz Labels: Type-Enhancement Priority-Medium Milestone-20100210 Comment #1 on issue 48 by larrygritz: texture() should take optional param for missing

Now that OSL is open source (congrats!), I recommend using the following guide on crediting patches from non-core developers in log

Comment #2 on issue 48 by jonogibbs: texture() should take optional param for missing texture http://code.google.com/p/openshadinglanguage/issues/detail?id=48 I would want a separate color per

Comment #3 on issue 48 by larrygritz: texture() should take optional param for missing texture http://code.google.com/p/openshadinglanguage/issues/detail?id=48 Agreed. After I posted that, I was

In an effort to keep the mail list free of clutter, I think we're deciding NOT to CC the list on every ticket. Instead, those of you who want to follow the gory details of every ticket and every