The function is, however, used in OSL, so on hurd it looks like it may be
problematic for oslc to automatically find stdosl.h (though that may explain
why Blender people seem to habitually #include <stdosl.h> by hand instead of
letting it happen automatically).
-- lg
On Jul 21, 2013, at 8:55 AM, Larry Gritz wrote:
> OK, I've amended that fix to https://github.com/OpenImageIO/oiio/pull/642
> It doesn't do the right thing on Hurd, but at least it should compile. Please
> give that a try if you can.
> (It's not so bad that it doesn't work right on Hurd, because at the moment,
> this function is not actually called within the OIIO code itself.)
>
>
>
> On Jul 20, 2013, at 2:01 PM, Matteo F. Vescovi wrote:
>
>> Hi!
>>
>> Il giorno 19/lug/2013 04:59, "Larry Gritz" <[email protected]> ha scritto:
>> > Do you know, for HURD, what is the correct call to tell you the current
>> > executable's path?
>>
>> I've been told that currently there is no way to do that on the Hurd.
>>
>> Cheers.
>>
>> --
>> Matteo F. Vescovi
>> Debian Maintainer
>> GnuPG KeyID: 0x83B2CF7A
>>
>
> --
> Larry Gritz
> [email protected]
>
>
> _______________________________________________
> Oiio-dev mailing list
> [email protected]
> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
--
Larry Gritz
[email protected]
_______________________________________________
Oiio-dev mailing list
[email protected]
http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
