Re: why is AM_OAF_PATH still in gnome-libs's

> Sorry if I'm off-mark here, since I'm just starting to dig into the
> Gnome source code, but why does gnome-libs's still check
> for AM_OAF_PATH? If I'm reading the CVS logs correctly, liboafgnome
> (which is what I assume this OAF thing is) got swallowed by
> libgnomeui, and nobody provides such a macro anymore. The module
> seems to configure and compile itself just fine with the AM_OAF_PATH
> commented out. 

I'm not 100% certain,
but I think liboaf has been moved from gnome-libs into the oaf module on CVS.
Someone with more knowledge about it all will probably correct me.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]