<div dir="ltr">I am sorry, but I have sent a message to Peter instad to the list and therefore he has sent the reply only to me as well..<br><br><div class="gmail_quote">2008/10/8 Peter Johansson <span dir="ltr"><<a href="mailto:trojkan@gmail.com">trojkan@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Matěj Týč wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thank you for your reply,<br>
<br>
Ever thought that perhaps nobody really feels they have the<br>
knowledge to answer your questions? Especially when your questions<br>
come to how to interface two different packages such as pkg-config<br>
and autotools. Can't remember exactly what your question was<br>
about, but it never hurts to look through the Autoconf Macro Archive.<br>
<br>
Well, pkg-config is considered as part of autotools (see this article <a href="http://www.linux.com/articles/114061" target="_blank">http://www.linux.com/articles/114061</a>)<br>
</blockquote></div>
I disagree. IMHO autoconf, automake, and libtools together form autotools.</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
and it even contains autotools support.<br>
</blockquote></div>
pkg-config is something outside of autotools that provide some support for autotools indeed.<div class="Ih2E3d"></div></blockquote><div> I agree with that, however pkg-config and autotools may complement each other extremely well </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If maintainers don't know how to use that in a smart way, who should? Besides, there really should be an "official" guide.<br>
</blockquote></div>
A guide would be welcome, in particular on how where to install *.pc files etc</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The next thing that wasn't followed by any reaction was the questions about C++ programs. Why not implement --cppflags and --cxxflags options for C++ developers that need them?<br>
</blockquote></div>
Personally I would prefer if the flags were more matched to the FLAGS in automake. I get the feeling the interface was designed against usage in Makefiles.<br>
<br>
Other than that, what would be the difference between cflags and cxxflags. I mean only do C++ and I've just put my cxxflags into the cflags. Is that wrong?</blockquote><div><br>Sometimes it is vital to be able to use CFLAGS and CXXFLAGS separatelly (I know that wxWidgets library requires this and possibly other projects that use C and C++ code). I agree with you regarding the usage in makefiles<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Anybody knows?<br>
</blockquote>
I don't know, and you only sent your email to me !<br>
<br>
thanks,<br>
Peter<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Regards,<br>
Matej<br>
</blockquote>
<br>
</blockquote></div><br></div>