On Sun, 2007-09-02 at 18:17 +0530, Hrishikesh Muruk wrote:
> Hi
>
> I am trying to check if STL is supported by the system and then
> include the STL headers path in my include path.
The term "STL" has been sufficiently misapplied at this point that it
isn't an adequate descriptor for anything
On Sun, Sep 02, 2007 at 11:53:48AM +0200, Roman Rumisek wrote:
> Exists easy way to build multi option libraries (for example: with/without
> debug feature) into different library names (for example:
> liba_d.so and liba.so)?
Many Debian packages build the production library and objcopy the
debugg
Roman Rumisek wrote:
Exists easy way to build multi option libraries (for example: with/without
debug feature) into different library names (for example:
liba_d.so and liba.so)?
I can think of three things, the last one might be the most applicable.
1. I believe the libtool manual has some e
Hi
I am trying to check if STL is supported by the system and then
include the STL headers path in my include path.
I used AC_CXX_HAVE_STL from the macro archive. So now my configure
script checks for STL when run. How do I determine the path to the
STL headers directory so that I can put
Exists easy way to build multi option libraries (for example: with/without
debug feature) into different library names (for example:
liba_d.so and liba.so)?
Thanx. Roman
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/