Date   

No OSL TSC meeting this week

Larry Gritz
 

US holiday tomorrow, meeting is cancelled. See you all for the next TSC meeting in 2 weeks.


Larry Gritz
lg@larrygritz.com


OSL TSC meeting ( every other week ) - Thu, 11/26/2020 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 26 November 2020, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Upcoming Events #cal-summary

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Open Shading Language discussion list Upcoming Events

OSL TSC meeting ( every other week )

When:
Thursday, 26 November 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 10 December 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 24 December 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 7 January 2021, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week ) - Thu, 11/26/2020 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 26 November 2020, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Re: LoadMemoryCompiledShader return value

Larry Gritz
 

Proposed fix:  https://github.com/imageworks/OpenShadingLanguage/pull/1302


On Nov 11, 2020, at 10:24 AM, Larry Gritz <lg@...> wrote:

Yes, I think it should return false if it's unable to complete its task.

Want to make a PR to fix this?


On Nov 11, 2020, at 1:28 AM, zap.andersson@... wrote:

Is there any particular reason the LoadMemoryCompiledShader call returns true even if it fails to parse the shader?

Code at the end of the function reads:

 

        // if (debug()) {

        //     std::string s = r->print ();

        //     if (s.length())

        //         info ("%s", s.c_str());

        // }

    } else {

        error ("Unable to parse preloaded shader \"%s\"", shadername);

    }

 

    return true;

}

 
 

/Z


--
Larry Gritz





--
Larry Gritz





Some OSL stuff at Autodesk University

Zap Andersson
 


Re: Windows Build and Documentation

Reza Aarabi
 

Sure @Dieter De Baets we will figure it out together

I will study oiio too, thank
yes, windows is a little bit stupid in finding dll or lib file, should define their paths exactly for it.
thanks @Larry Gritz 

On Fri, Nov 13, 2020 at 9:53 AM Larry Gritz <lg@...> wrote:
If you look at the OIIO project, it has two Windows CI builds *almost* totally working -- they build, but they currently disable running the tests (SKIP_TESTS: 1) because I had trouble making that fully work with finding the DLLs and whatnot. Probably something obviously fixable to people who use Windows regularly. (The dependency setup is a little janky, too, and doesn't yet include a lot of the optional dependencies, but we can fix that later.)

You can see how the OIIO Windows CI is set up here: https://github.com/OpenImageIO/oiio/blob/master/.github/workflows/ci.yml#L279

I think as a first step, figuring out how to get that fully working so it can run the tests would be a great start. With that completed, it would then provide a blueprint for how to do it all for OSL (their build and CI scripts are 90% shared between the two projects).


On Nov 13, 2020, at 12:24 AM, Dieter De Baets <debaetsd@...> wrote:

I did some github actions Windows builds in the past (though nothing as complex as OSL) 
While it felt a bit like trial & error at the time, it did work out in the end.
Reza, let me know if I can help somehow.



On Fri, Nov 13, 2020 at 1:50 AM Reza Aarabi <madoodia@...> wrote:
Thanks, yes, I know it's meaning,

So, with CI we can install it easily and automatically on linux. I didn''t test with that method.
Btw, I'm studying related topics, and I try to help on Windows side.
yaml and bash scripts of OSl will help me.

thanks again

On Thu, Nov 12, 2020 at 4:47 PM Mitch Prater <mprater@...> wrote:
Hi Reza, 

If I understand your questions correctly, CI stands for Continuous Integration, which means the OSL code is built automatically and continuously. There are tools in github that help make this possible. However, we don't currently have any CI build for Windows, and need someone to help with that.

mitch




-- 


---------------------
--= Reza Aarabi =--



--
Larry Gritz






--


---------------------
--= Reza Aarabi =--


Re: Windows Build and Documentation

Larry Gritz
 

If you look at the OIIO project, it has two Windows CI builds *almost* totally working -- they build, but they currently disable running the tests (SKIP_TESTS: 1) because I had trouble making that fully work with finding the DLLs and whatnot. Probably something obviously fixable to people who use Windows regularly. (The dependency setup is a little janky, too, and doesn't yet include a lot of the optional dependencies, but we can fix that later.)

You can see how the OIIO Windows CI is set up here: https://github.com/OpenImageIO/oiio/blob/master/.github/workflows/ci.yml#L279

I think as a first step, figuring out how to get that fully working so it can run the tests would be a great start. With that completed, it would then provide a blueprint for how to do it all for OSL (their build and CI scripts are 90% shared between the two projects).


On Nov 13, 2020, at 12:24 AM, Dieter De Baets <debaetsd@...> wrote:

I did some github actions Windows builds in the past (though nothing as complex as OSL) 
While it felt a bit like trial & error at the time, it did work out in the end.
Reza, let me know if I can help somehow.



On Fri, Nov 13, 2020 at 1:50 AM Reza Aarabi <madoodia@...> wrote:
Thanks, yes, I know it's meaning,

So, with CI we can install it easily and automatically on linux. I didn''t test with that method.
Btw, I'm studying related topics, and I try to help on Windows side.
yaml and bash scripts of OSl will help me.

thanks again

On Thu, Nov 12, 2020 at 4:47 PM Mitch Prater <mprater@...> wrote:
Hi Reza, 

If I understand your questions correctly, CI stands for Continuous Integration, which means the OSL code is built automatically and continuously. There are tools in github that help make this possible. However, we don't currently have any CI build for Windows, and need someone to help with that.

mitch




-- 


---------------------
--= Reza Aarabi =--



--
Larry Gritz





Re: Windows Build and Documentation

Dieter De Baets <debaetsd@...>
 

I did some github actions Windows builds in the past (though nothing as complex as OSL) 
While it felt a bit like trial & error at the time, it did work out in the end.
Reza, let me know if I can help somehow.



On Fri, Nov 13, 2020 at 1:50 AM Reza Aarabi <madoodia@...> wrote:
Thanks, yes, I know it's meaning,

So, with CI we can install it easily and automatically on linux. I didn''t test with that method.
Btw, I'm studying related topics, and I try to help on Windows side.
yaml and bash scripts of OSl will help me.

thanks again

On Thu, Nov 12, 2020 at 4:47 PM Mitch Prater <mprater@...> wrote:
Hi Reza,

If I understand your questions correctly, CI stands for Continuous Integration, which means the OSL code is built automatically and continuously. There are tools in github that help make this possible. However, we don't currently have any CI build for Windows, and need someone to help with that.

mitch



--


---------------------
--= Reza Aarabi =--


Upcoming Events #cal-summary

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Open Shading Language discussion list Upcoming Events

OSL TSC meeting ( every other week )

When:
Thursday, 26 November 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 10 December 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 24 December 2020, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


OSL TSC meeting ( every other week )

When:
Thursday, 7 January 2021, 2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer: Chris Kulla ckulla@...

Details:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR

View Event


Re: Windows Build and Documentation

Reza Aarabi
 

Thanks, yes, I know it's meaning,

So, with CI we can install it easily and automatically on linux. I didn''t test with that method.
Btw, I'm studying related topics, and I try to help on Windows side.
yaml and bash scripts of OSl will help me.

thanks again


On Thu, Nov 12, 2020 at 4:47 PM Mitch Prater <mprater@...> wrote:
Hi Reza,

If I understand your questions correctly, CI stands for Continuous Integration, which means the OSL code is built automatically and continuously. There are tools in github that help make this possible. However, we don't currently have any CI build for Windows, and need someone to help with that.

mitch



--


---------------------
--= Reza Aarabi =--


Re: Windows Build and Documentation

Mitch Prater
 

Hi Reza,

If I understand your questions correctly, CI stands for Continuous Integration, which means the OSL code is built automatically and continuously. There are tools in github that help make this possible. However, we don't currently have any CI build for Windows, and need someone to help with that.

mitch


Re: Windows Build and Documentation

Reza Aarabi
 

I'm not very good at CI, but I can work on it to see can I find a straightforward solution to install OSL through CI and will update the thread
I'll do my best.

just if I know what CI and installing a repo through CI is for code coverage or for using, if you tell me what is the exact reason of having CI in a repo, would be great.


On Wed, Nov 11, 2020 at 10:29 PM Reza Aarabi via lists.aswf.io <madoodia=gmail.com@...> wrote:
No problem, thanks! 
My Centos7 has problem in make and automake (for one of deps, don't remember exactly which one)
I couldn't test it on linux but I think it works there too
btw, I will add other deps to it too
and will test it on virtual machine for linux too.


On Wed, Nov 11, 2020 at 9:59 PM Larry Gritz <lg@...> wrote:
Sorry it took me a few days to get to take a look, but this is really promising, Reza.



On Nov 6, 2020, at 12:37 PM, Reza Aarabi <madoodia@...> wrote:

Hello all

Based on my experiences on building OSL in windows, I prepared a documentation of how I did that.
https://docs.google.com/document/d/1w980RjV8VWvsT2ha2EnV60EexoS97j1cUUukrr16c_U/edit?usp=sharing

The build system is in my local fork in this address https://github.com/madoodia/OpenShadingLanguage (rz-building-on-windows)

it is a custom setup, for example all dependencies are built before osl, because I had lots of issues on using external installation (like llvm)
and I tried this method on llvm 7, 8 and 9, all with error, so my current build setup is on llvm 11 and C++14, it can be changed in code. (I am trying to make it easy to use for changing configs with arguments)

please take a look at docs and let me know my mistakes.

this method worked fine for me for release, debug and debugging in visual studio.

<build1.JPG>

thanks

--
Larry Gritz






--


---------------------
--= Reza Aarabi =--



--


---------------------
--= Reza Aarabi =--


OSL TSC meeting ( every other week ) - Thu, 11/12/2020 #cal-notice

osl-dev@lists.aswf.io Calendar <noreply@...>
 

OSL TSC meeting ( every other week )

When:
Thursday, 12 November 2020
2:00pm to 3:00pm
(GMT-08:00) America/Los Angeles

Where:
https://zoom.us/j/100511909

Organizer:
ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


OSL TSC meeting ( every other week ) - Thu, 11/12/2020 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 12 November 2020, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


OSL TSC meeting ( every other week ) - Thu, 11/12/2020 2:00pm-3:00pm #cal-reminder

osl-dev@lists.aswf.io Calendar <osl-dev@...>
 

Reminder: OSL TSC meeting ( every other week )

When: Thursday, 12 November 2020, 2:00pm to 3:00pm, (GMT-08:00) America/Los Angeles

Where:https://zoom.us/j/100511909

View Event

Organizer: Chris Kulla ckulla@...

Description:

Every other week meeting of the OSL TSC.

Meeting Agenda / Notes: https://docs.google.com/document/d/1yf0bG6eoE2EvKZBNZX3nskdTvu99ADTDTNOknCDJd1I/

Confirm this meeting invite is still valid by finding the meeting at https://lists.aswf.io/calendar.

Join Zoom Meeting https://zoom.us/j/100511909

Meeting ID: 100 511 909

One tap mobile +16465588656,,100511909# US (New York) +13126266799,,100511909# US (Chicago)

Dial by your location +1 646 558 8656 US (New York) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US +1 301 715 8592 US +1 346 248 7799 US (Houston) 877 369 0926 US Toll-free 855 880 1246 US Toll-free +1 587 328 1099 Canada +1 647 374 4685 Canada +1 647 558 0588 Canada +1 778 907 2071 Canada +1 438 809 7799 Canada 855 703 8985 Canada Toll-free Meeting ID: 100 511 909 Find your local number: https://zoom.us/u/acBVrM6HWR


Re: Windows Build and Documentation

Reza Aarabi
 

No problem, thanks! 
My Centos7 has problem in make and automake (for one of deps, don't remember exactly which one)
I couldn't test it on linux but I think it works there too
btw, I will add other deps to it too
and will test it on virtual machine for linux too.


On Wed, Nov 11, 2020 at 9:59 PM Larry Gritz <lg@...> wrote:
Sorry it took me a few days to get to take a look, but this is really promising, Reza.



On Nov 6, 2020, at 12:37 PM, Reza Aarabi <madoodia@...> wrote:

Hello all

Based on my experiences on building OSL in windows, I prepared a documentation of how I did that.
https://docs.google.com/document/d/1w980RjV8VWvsT2ha2EnV60EexoS97j1cUUukrr16c_U/edit?usp=sharing

The build system is in my local fork in this address https://github.com/madoodia/OpenShadingLanguage (rz-building-on-windows)

it is a custom setup, for example all dependencies are built before osl, because I had lots of issues on using external installation (like llvm)
and I tried this method on llvm 7, 8 and 9, all with error, so my current build setup is on llvm 11 and C++14, it can be changed in code. (I am trying to make it easy to use for changing configs with arguments)

please take a look at docs and let me know my mistakes.

this method worked fine for me for release, debug and debugging in visual studio.

<build1.JPG>

thanks

--
Larry Gritz






--


---------------------
--= Reza Aarabi =--


Re: Windows Build and Documentation

Larry Gritz
 

Sorry it took me a few days to get to take a look, but this is really promising, Reza.



On Nov 6, 2020, at 12:37 PM, Reza Aarabi <madoodia@...> wrote:

Hello all

Based on my experiences on building OSL in windows, I prepared a documentation of how I did that.
https://docs.google.com/document/d/1w980RjV8VWvsT2ha2EnV60EexoS97j1cUUukrr16c_U/edit?usp=sharing

The build system is in my local fork in this address https://github.com/madoodia/OpenShadingLanguage (rz-building-on-windows)

it is a custom setup, for example all dependencies are built before osl, because I had lots of issues on using external installation (like llvm)
and I tried this method on llvm 7, 8 and 9, all with error, so my current build setup is on llvm 11 and C++14, it can be changed in code. (I am trying to make it easy to use for changing configs with arguments)

please take a look at docs and let me know my mistakes.

this method worked fine for me for release, debug and debugging in visual studio.

<build1.JPG>

thanks

--
Larry Gritz





Seeking contributors and area leads for OSL project

Larry Gritz
 

I've mentioned a few times, and especially at the last OSL TSC meeting, that I am hoping for several people to take more active leadership roles in the OSL project. So here are a few major areas that could use attention. If volunteers were forthcoming, each could be appropriate to have an ongoing "area leader" or small team responsible for it.

It is not necessary for all of these to be filled. I'd be thrilled (and much more productive) if even a few of them ended up with dedicated leaders and could be taken off my list of daily worries.  Also note that even if you don't feel like you're able to take primary responsibility for an area, this perhaps serves as a list of some of the many task areas where we could use more people actively contributing, every little bit helps. I don't consider any of these to be menial tasks; every one is vital to the project and could be done in a way that is exhibits great creativity and craftsmanship.

Windows  (<--- This is my #1 priority to fill because I have no competency in this area)
* Set up a proper CI test to build and test on Windows (we currently lack this, and it hurts us).
* Improve documentation or tools to make it as easy and flawless as possible for Windows users to install dependencies and build OSL.
* Keep us running smoothly for Windows users and generally advise the rest of the project.
* Watch and review PRs for changes that might break or have issues on Windows.
* Triage and respond to Windows related issues or questions on the mail list.
* Coordinate with Build/CI lead and Docs lead on areas of overlap.

Build/CI
* Maintain and make ongoing improvements to our CMake build system and CI practices.
* Investigate build breaks, issues related to the build system.
* Patrol dependencies and our CI coverage thereof -- for example, our CI matrix entry that tests against the "current" release of all dependencies needs to be periodically updated to account for new releases of those dependencies, and sometimes changes in our code are necessary to deal with changes in the APIs of our dependencies.
* Improve our strategy for easily building missing dependencies.
* Coordinate on areas of overlap with the Windows lead, ASWF CI working group, and VFX Platform.

Release manager
* Determine timing of major releases, branch, schedule and announce code freezes, rally developers to complete their tasks (and take a hard line on what gets withheld from a release because it's not ready).
* Backport from master to release branch (or make the decisions on which PRs should be backported by their authors) based on what's safe and necessary.
* Execute monthly patch releases -- backport, freeze, update release notes, tag, announce.

Documentation  (Mitch Prater has volunteered to lead this area)
* Make an actual web site / landing page.
* Robust installation and build instructions.
* Guide for how to integrate OSL into a renderer (beyond simply reading headers and source code for testshade/testrender).
* A better on-ramp or guide for people who want to contribute to the project.
* Web-based doc portal containing all the relevant documentation, akin to https://openimageio.readthedocs.io or OpenColorIO's https://opencolorio.org/ and https://opencolorio.readthedocs.io . 
* Tutorial or cookbook material for people learning to write OSL shaders (beyond the formal language spec, which may be a good language reference, but is not intended to teach you how to write interesting shaders).
* Blog or email newsletter with periodic tips or tutorials for OSL shader writers.

LLVM
* Responsible for maintaining deep knowledge of LLVM.
* Improve OSL's use of LLVM, especially as it impacts compilation and execution performance. (Including, if necessary, sending patches to LLVM.)
* Keep our code base apace with new LLVM releases, port to them, decide how/when we should phase out support of old LLVM releases.

Cuda/OptiX
* Somebody who knows more about Cuda/OptiX programming than I do!
* Lead the effort to flesh out more full implementation of OSL on Cuda/OptiX, coordinating the overall strategy, tasks, and contributions of the other developers.
* Code review all the PRs from other contributors that touch the GPU code path.
* Keep up with evolving Cuda/OptiX features and development culture, migrate our code base to always be using best practices.


Most of these roles (all but the LLVM and GPU leads) require only intermediate-level general programming skills in C++ and CMake, and do not require extensive prior experience with OSL or its internals. You need not be a TSC member to work on these, though taking major responsibility for one of these areas can certainly earn you a seat if you don't already have one.

Ideally, I'm looking for an area leader for each one, but that doesn't mean that it's a one-person-only set of tasks. Any little bit of contribution would help, and part of the job of the area lead is to help coordinate the efforts of other developers. Also, this list is not exhaustive; if there is a large area that needs attention that has not occurred to me, please do point it out or volunteer to help with it.

--
Larry Gritz
lg@...





Re: LoadMemoryCompiledShader return value

Larry Gritz
 

Yes, I think it should return false if it's unable to complete its task.

Want to make a PR to fix this?


On Nov 11, 2020, at 1:28 AM, zap.andersson@... wrote:

Is there any particular reason the LoadMemoryCompiledShader call returns true even if it fails to parse the shader?

Code at the end of the function reads:

 

        // if (debug()) {

        //     std::string s = r->print ();

        //     if (s.length())

        //         info ("%s", s.c_str());

        // }

    } else {

        error ("Unable to parse preloaded shader \"%s\"", shadername);

    }

 

    return true;

}

 
 

/Z


--
Larry Gritz




401 - 420 of 4849