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

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

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

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@...

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

Yes, works fine with either.

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

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

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@...

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.

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

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

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

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

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

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

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

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

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

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