|
Release: OSL v1.12.9.0
We have tagged v1.12.9.0 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
We have tagged v1.12.9.0 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
|
By
Larry Gritz
· #5099
·
|
|
Are setmessage/getmessage still used by anybody?
In the last OSL TSC meeting, we were discussing the continued role of the setmessage/getmessage functions. Now, let's put aside how getmessage("trace", ...) doubles as a way to retrieve information fr
In the last OSL TSC meeting, we were discussing the continued role of the setmessage/getmessage functions. Now, let's put aside how getmessage("trace", ...) doubles as a way to retrieve information fr
|
By
Larry Gritz
· #5090
·
|
|
Release: OSL v1.12.8.0
We have tagged v1.12.8.0 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
We have tagged v1.12.8.0 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
|
By
Larry Gritz
· #5082
·
|
|
Handling of std::locale during parse
Yeah, that sounds fine. The OIIO::Strutil::stof is locale-independent, so if we're using that, we don't need to mess with locales. -- Larry Gritz lg@...
Yeah, that sounds fine. The OIIO::Strutil::stof is locale-independent, so if we're using that, we don't need to mess with locales. -- Larry Gritz lg@...
|
By
Larry Gritz
· #5081
·
|
|
Question about Imath headers
Joey, I'm still a little confused about some of the ambiguities in your description. Which project do you mean by "my project?" What is the specific #include (and in which file) that fails? That is, w
Joey, I'm still a little confused about some of the ambiguities in your description. Which project do you mean by "my project?" What is the specific #include (and in which file) that fails? That is, w
|
By
Larry Gritz
· #5071
·
|
|
Question about Imath headers
Yes, works fine with either.
Yes, works fine with either.
|
By
Larry Gritz
· #5070
·
|
|
Question about Imath headers
I suspect that what's happening is that you actually have TWO copies of either openexr or imath or both on your system -- one the new 3.x you are trying to build, and also another 2.x probably install
I suspect that what's happening is that you actually have TWO copies of either openexr or imath or both on your system -- one the new 3.x you are trying to build, and also another 2.x probably install
|
By
Larry Gritz
· #5068
·
|
|
Release: OSL v1.12.7.1
We have tagged v1.12.7.1 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
We have tagged v1.12.7.1 as the latest production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases. Rel
|
By
Larry Gritz
· #5058
·
|
|
No TSC meeting this week
Reminder that this Thursday's scheduled OSL TSC meeting is cancelled because it falls on US Thanksgiving holiday, lots of members will be on vacation this week. -- lg -- Larry Gritz lg@...
Reminder that this Thursday's scheduled OSL TSC meeting is cancelled because it falls on US Thanksgiving holiday, lots of members will be on vacation this week. -- lg -- Larry Gritz lg@...
|
By
Larry Gritz
· #5054
·
|
|
Release: OSL 1.12.7.0
We have tagged v1.12.7.0 as the latest OSL production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases.
We have tagged v1.12.7.0 as the latest OSL production release and moved the "release" branch marker to that point. This is guaranteed to be API, ABI, and link back-compatible with prior 1.12 releases.
|
By
Larry Gritz
· #5036
·
|
|
Individual layer execution
The only think I can think of is this: execute() unconditionally executes all nodes that produce renderer outputs (which may in turn lazily execute upstream layers). Maybe we thought that if different
The only think I can think of is this: execute() unconditionally executes all nodes that produce renderer outputs (which may in turn lazily execute upstream layers). Maybe we thought that if different
|
By
Larry Gritz
· #5021
·
|
|
Individual layer execution
Per today's TSC meeting... The PR that originally added the per-layer execution is this one from 2015: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/553 Unfortunately, though t
Per today's TSC meeting... The PR that originally added the per-layer execution is this one from 2015: https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/553 Unfortunately, though t
|
By
Larry Gritz
· #5020
·
|
|
Build failure on anything other than x86*
I see, you are correct! It looks like there are a few places where the inclusion of certain headers that are specific to the SIMD batch shading should be guarded by `#if OSL_USE_BATCHED`. I'll try to
I see, you are correct! It looks like there are a few places where the inclusion of certain headers that are specific to the SIMD batch shading should be guarded by `#if OSL_USE_BATCHED`. I'll try to
|
By
Larry Gritz
· #5012
·
|
|
Release: OSL v1.12.6.2 (new supported release family!)
OSL version 1.12 has been released! Officially tagged as "v1.12.6.2", we have also moved the "release" branch tag to this position. Henceforth, 1.12 is the supported production release family. The API
OSL version 1.12 has been released! Officially tagged as "v1.12.6.2", we have also moved the "release" branch tag to this position. Henceforth, 1.12 is the supported production release family. The API
|
By
Larry Gritz
· #5010
·
|
|
OSL v1.12.6.1-RC1 release candidate
We have tagged the release candidate as "v1.12.6.1-RC1". Changes since the beta: * Fix overrunning allocation region in debug common_ancestor_between. #1577 * Fix bug where assigning an init-op param
We have tagged the release candidate as "v1.12.6.1-RC1". Changes since the beta: * Fix overrunning allocation region in debug common_ancestor_between. #1577 * Fix bug where assigning an init-op param
|
By
Larry Gritz
· #5004
·
|
|
Now passing OpenSSF CII badge
With the merge of https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1581, OSL is now at 100% of the OpenSSF Core Infrastructure Initiative Best Practices badge at the "passing" lev
With the merge of https://github.com/AcademySoftwareFoundation/OpenShadingLanguage/pull/1581, OSL is now at 100% of the OpenSSF Core Infrastructure Initiative Best Practices badge at the "passing" lev
|
By
Larry Gritz
· #5001
·
|
|
Q on preferred version bumping practice
As discussed in the last TSC meeting, I'm working on documenting our release practices, and I have a question about how people prefer to have the timing of version number changes in the trunk. We rele
As discussed in the last TSC meeting, I'm working on documenting our release practices, and I have a question about how people prefer to have the timing of version number changes in the trunk. We rele
|
By
Larry Gritz
· #4989
·
|
|
OSL v1.12.6.0-beta
At long last, we have tagged "v1.12.6.0-beta"! This is the first beta test release of OSL 1.12. The current plan is to have a true release or or about October 1, after which the 1.12 family will be th
At long last, we have tagged "v1.12.6.0-beta"! This is the first beta test release of OSL 1.12. The current plan is to have a true release or or about October 1, after which the 1.12 family will be th
|
By
Larry Gritz
· #4987
·
|
|
OSL/MaterialX meeting at SIGGRAPH
Only slightly off-topic: Everybody going, please travel and attend safely! I'm organizing https://twitter.com/SIGGRAPHCO2 please follow and promote this account which will live tweet CO2 readings of s
Only slightly off-topic: Everybody going, please travel and attend safely! I'm organizing https://twitter.com/SIGGRAPHCO2 please follow and promote this account which will live tweet CO2 readings of s
|
By
Larry Gritz
· #4971
·
|
|
OSL/MaterialX meeting at SIGGRAPH
https://events.linuxfoundation.org/open-source-days/program/schedule/ As part of the ASWF's "Open Source Days" (presented as a SIGGRAPH event), the 10:40am block on Monday, MaterialX and OSL will give
https://events.linuxfoundation.org/open-source-days/program/schedule/ As part of the ASWF's "Open Source Days" (presented as a SIGGRAPH event), the 10:40am block on Monday, MaterialX and OSL will give
|
By
Larry Gritz
· #4970
·
|