|
Our code development
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
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
|
By
Larry Gritz <larry...@...>
·
#61
·
|
|
Re: Question about BSDFClosure functions
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
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
|
By
Larry Gritz <l...@...>
·
#60
·
|
|
Re: Question about BSDFClosure functions
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
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
|
By
Alex Conty <aco...@...>
·
#59
·
|
|
Question about BSDFClosure functions
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
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
|
By
brecht <brechtv...@...>
·
#58
·
|
|
Review: bug fix with compound initializers
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,
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,
|
By
Larry Gritz <l...@...>
·
#55
·
|
|
Re: Bug fix with compound initializers (issue189060)
LGTM
http://codereview.appspot.com/189060
LGTM
http://codereview.appspot.com/189060
|
By
cku...@...
·
#57
·
|
|
Bug fix with compound initializers (issue189060)
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
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
|
By
larry...@...
·
#56
·
|
|
Review: message passing of closures, and bug fixes
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,
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,
|
By
Larry Gritz <l...@...>
·
#54
·
|
|
Re: Got it working I think?
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:
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:
|
By
Jon Macey <jma...@...>
·
#53
·
|
|
Re: Got it working I think?
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
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
|
By
Larry Gritz <l...@...>
·
#52
·
|
|
Re: Got it working I think?
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
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
|
By
Jon Macey <jma...@...>
·
#51
·
|
|
Got it working I think?
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
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
|
By
Jon Macey <jma...@...>
·
#50
·
|
|
Re: Build errors
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
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
|
By
Larry Gritz <larry...@...>
·
#49
·
|
|
Build errors
Hi,
I encountered several minor build errors both on release and debug. I
corrected a few (I'll release a patch if you're interrested) but there
is one i can't explain
Hi,
I encountered several minor build errors both on release and debug. I
corrected a few (I'll release a patch if you're interrested) but there
is one i can't explain
|
By
Adrien Herubel <her...@...>
·
#48
·
|
|
Overview of unique OSL features and state of the project
I've posted a Wiki page giving a brief introduction to the project, a
list of things unique to OSL (compared to other shading languages), a
status report on the current state of the project.
Click on
I've posted a Wiki page giving a brief introduction to the project, a
list of things unique to OSL (compared to other shading languages), a
status report on the current state of the project.
Click on
|
By
Larry Gritz <larry...@...>
·
#47
·
|
|
Re: Today is the day
OK, it seems to have been synced. The trunk is now where we're
actually doing all our development. We will periodically make release
branches and tags at stable points.
-- lg
OK, it seems to have been synced. The trunk is now where we're
actually doing all our development. We will periodically make release
branches and tags at stable points.
-- lg
|
By
Larry Gritz <larry...@...>
·
#46
·
|
|
Re: OSL language spec available
Whoops, I see what I did.
Thanks David
Whoops, I see what I did.
Thanks David
|
By
Gene Crucean <emailgene...@...>
·
#45
·
|
|
Re: OSL language spec available
http://code.google.com/p/openshadinglanguage/downloads/list
wrote:
http://code.google.com/p/openshadinglanguage/downloads/list
wrote:
|
By
David Hawbaker <djhaw...@...>
·
#44
·
|
|
Re: OSL language spec available
Am I blind? If I click on "Files" I don't see any files listed. There is also no downloads link.
Am I blind? If I click on "Files" I don't see any files listed. There is also no downloads link.
|
By
Gene Crucean <emailgene...@...>
·
#43
·
|
|
OSL language spec available
On the "downloads" tab.
By
Larry Gritz <larry...@...>
·
#42
·
|