<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8"> <META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0"> </HEAD> <BODY> On Wed, 2010-06-16 at 08:45 -0700, Dan Nicholson wrote: <BLOCKQUOTE TYPE=CITE> <PRE> Since the reason for these variables is to populate the pkg-config Requires field, I don't think it makes sense to have an "optional" version. When you call "pkg-config --cflags xorg-server", the module will be required. So, I'd just put everything under SDK_REQUIRED_MODULES. SDK_OPTIONAL_MODULES is misleading since it seems to mean "optional in the build" and modules are required once they're exposed by the sdk. In other words, if you've built the server such that the DRI2 extension is enabled _and_ dri2proto datatypes/protocal are exposed in the sdk headers, then the module is required by xorg-server. </PRE> </BLOCKQUOTE> I see how it can be confusing. <BLOCKQUOTE TYPE=CITE> <PRE> Also, we only want to add modules to Requires that are explicitly exposed by the sdk. If a driver decides it needs a specific API that's not exposed by the xorg sdk, then it should handle that itself. </PRE> </BLOCKQUOTE> It took me a while to figure out what is "exposed" vs "what is not exposed". I never used that SDK... <BLOCKQUOTE TYPE=CITE> <PRE> Thanks for grovelling through all the drivers, though. It's definitely good to know what APIs are actually in use. </PRE> </BLOCKQUOTE> Thanks for your patience, it will help reducing and strengthening driver configuration. <BLOCKQUOTE TYPE=CITE> <PRE> -- Dan </PRE> </BLOCKQUOTE> </BODY> </HTML>