Re: [cgkit-user] slparse imporvements

[Matthias B. <mat...@gm...>]

Hi Simon,

Simon Bunker wrote:
> Being able to interrogate binary shaders with cgkit is a great new addition.
> 
> However I was wondering if it could fall back to parsing the output
> from sloinfo etc. The reason for this is that prman at least, normally
> doesn't come with the devkit - it is a separate download - and so most
> people won't have it.

Oh, does that mean the prman library is not installed by default (e.g.
$RMANTREE/lib/libprman.so on Linux)? I thought the actual renderer and
the Python stuff would be using this shared library as well, so that it
would always be available?
(btw, which version of prman are you referring to? I was basically
targetting prman 14 and above as previous versions didn't ship with a
shared library anyway.... or is that what you mean, does prman <14 come
with a shared library in the devkit? (I never installed prman myself)).

Running and parsing sloinfo shouldn't be a problem. I just have to see
how it's best integrated into the package so that by default, it's all
done transparently to the user but, if necessary, the user could also
control how the shader should be parsed and which sloinfo to use, etc.

> PS good idea to switch to git - it is much nicer to work with than
> other source control.

In particular, it makes it much easier for me to support Python 2 and
Python 3 at the same time.

Cheers,

- Matthias -