<br><br><div class="gmail_quote">On Sat, Jun 19, 2010 at 11:16 AM, Andreas Metzler <span dir="ltr"><<a href="mailto:ametzler@downhill.at.eu.org">ametzler@downhill.at.eu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div><div></div><div class="h5">Dan Nicholson <<a href="mailto:dbn.lists@gmail.com">dbn.lists@gmail.com</a>> wrote:<br> > On Thu, Jun 17, 2010 at 2:35 PM, Vincent Torri <<a href="mailto:vincent.torri@gmail.com">vincent.torri@gmail.com</a>> wrote:<br> >> Hey,<br> <br> >> We have 2 libraries, named Eina and Evas. Eina is some kind of data types<br> >> lib. Evas depends on Eina. Hence, Eina is "public". Its types are used in<br> >> the API and we have, for example, in Evas.h (the public header)<br> <br> >> #include <Eina.h><br> <br> >> The .pc file of Eina is named eina-0.pc<br> <br> >> My question is:<br> <br> >> should I put eina-0 in the Requirements field, or in the<br> >> Requirements.private field ?<br> <br> > Requires.private. You need to make sure that users get the Cflags from<br> > Eina for the datatypes, but they don't need to explicitly link to Eina<br> > unless they're statically linking. See FAQ #2 here:<br> <br> > <a href="http://people.freedesktop.org/%7Edbn/pkg-config-guide.html" target="_blank">http://people.freedesktop.org/~dbn/pkg-config-guide.html</a><br> <br> > This guide is also in the latest pkg-config release if you have it.<br> <br> </div></div>Quote<br> "Requires.private: A list of private packages required by this package<br> but not exposed to applications."<br> Unquote<br> <br> If Evas.h includes <Eina.h> then evas *does* expose Eina's API to the<br> application.<br> cu andreas<br></blockquote><div><br>So ? What should I do ?<br><br>Vincent Torri<br></div></div>