On Fri, Jun 14, 2013 at 2:09 PM, Ben Reser <ben_at_reser.org> wrote:
> Yes and I guess that's probably the easiest solution for this older
> APIs. In 1.6. we introduced the platform specific APIs that make it
> easier to deal with runtime detection of platform specific auth
> runtimes. Given that I guess going back and mucking with the older
> APIs doesn't seem necessary to deal with the runtime issues.
Actually now that I think about it a bit more I'm not sure that helps.
It'll probably just shift it to a link time error because the defines
will be there so it'll build, SWIG will generate wrappers for them
that depend on the functions in our libraries, which won't be
available in the libraries they built because we exclude them on their
We can work around that by adding logic to SWIG to specifically
exclude these functions based on the same conditions as we have in our
headers and build systems. But then we've added yet another place to
So it turns into hacks all the way down.
The alternative is to fix it so the error happens at runtime, which
shifts that to the library user. In these specific cases, simply
providing a noop provider, hides the entire problem from even the
Received on 2013-06-14 14:21:31 CEST