Follow-up Comment #2, bug #48348 (project gnustep):
While I see your point, that goes completely against established conventions
for *-config scripts.
I tested various config scripts (freetype-config, icu-config, xml2-config and
pkg-config, to name a few). The convention is that flags-type arguments output
-I and -D directives, and libs-type arguments output -L and -l directives.
This makes sense, because most folks just want to know where to find the
headers and library, and how to link to the library.
I think we should be able to do "$ gcc $OBJCFLAGS $LIBS `gnustep-config
--objc-flags --base-libs` main.m" to build a simple tool, just like I can do
"$ gcc $CFLAGS $LIBS `xml2-config --cflags --libs` main.c", without having the
output of gnustep-config interfere with $OBJCFLAGS and $LIBS already in place.
This is the simplest possible example I could come up with.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48348>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
