----- Original Message -----
From: "chm" <devel.chm...@gmail.com>
To: "Sisyphus" <sisyph...@optusnet.com.au>
Cc: "Nicholas Clark" <n...@ccl4.org>; "David Oswald" <daosw...@gmail.com>;
<inline@perl.org>
Sent: Thursday, December 22, 2011 12:11 AM
Subject: Re: Inline::CPP Namespaces.
Devel::CheckLib offers a standard way to do
this type of check.
Yes, I had mentioned Devel::CheckLib to David earlier, but its documentation
says that it uses $Config{cc}, which is usually a different compiler to the
one in use. (Maybe it also provides a facility to override that ?)
With MS compilers, the cpp compiler is usually 'cl -TP' and that poses
another problem regarding this testing.
The following works fine with my nuisance MS x64 compiler:
cl -Fe:try.exe try.cpp bufferoverflowU.lib
But the following does not work:
cl -TP -Fe:try.exe try.cpp bufferoverflowU.lib
That now treats bufferoverflowU.lib as an input file (that can't be found),
thereby causing failure.
Much simpler if we don't have to go beyond the compile stage, thereby
avoiding the issue of whether bufferoverflowU.lib is present/needed.
Cheers,
Rob
