Hey, It can be interesting to detect the evas modules (engines, loaders, savers) with pkg-config. I can see several possibilities:
1) using a variable for each module in evas.pc, which can be retrieved with pkg-config --variable=VARIABLENAME evas 2) using a variable for each kind of module, like: engines: xlib directfb etc... loaders: jpeg png and parsing the result with sed or another tool. That can be annoying. 3) Creating a .pc file for each module. The detection can be done with the --print-errors --exists options of pkg-config. I don't like very much the 2nd idea. And I find the 3rd one too heavy, especially because a .pc file is usually used to get flags or prefix, not just the existence of a lib. So I prefer the 1st one. tilman prefers the 3rd one. We would like other opinions, and maybe other (better ?) ideas in order to detect those modules with pkg-config thank you Vincent ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
