Are the plugins directories necessary for client code?

[redfloyd@gmail.com]

On Aug 8, 11:15 am, Ken Raeburn <raeb... at MIT.EDU> wrote:
> On Aug 8, 2007, at 12:22, redfl... at gmail.com wrote:

> > I think the issue is actually in the configure script.  --enable-
> > static and --disable-shared don't work properly, and I had to
> > externally set then environment variable krb5_force_static to get the
> > thing to even configure properly.
>
> Ah, actually, I don't expect them to work well at all; in fact, in  
> the current sources, they'll just report errors and refuse to  
> configure the tree.  We've made some changes that assume you're using  
> shared libraries; the plugin support is part of it, but it's also let  
> us simplify some of the library-building configuration a little.  You  
> can try doing static-only builds, but I doubt they'll work, and  
> they're not going to be a high priority for us to fix.

That certainly makes sense.

> That said, if you or someone else would like to take a look at making  
> static builds work again, get some discussion going on the krbdev  
> list on whether plugins need to work, if it's sufficient for non-KDC  
> programs only to work, how best to deal with the AIX configs where  
> static and shared libraries have the same suffix, etc., and let's see  
> how clean the patches can be made.  (IMNSHO, the existing library  
> build rules still need more cleanup; don't make that harder.)

I have just recently joined krbdev, and was thinking of lurking a bit
before commenting/requesting.

I will definitely consider your suggestion, but would like to have a
bit more experience with krb development before jumping in on
something like that.

Thanks,

Scott