Craig A. Berry wrote:
At 1:48 PM +0200 10/29/04, Abe Timmerman wrote:
Hi,
Am I right in thinking that the combination:
@Configure -Dusevmsdebug mmk/macro=("__DEBUG__=1")
is equivalent to the DEBUGGING thing for *nix?
Totally unrelated. usevmsdebug compiles and links everything for the VMS debugger (more or less equivalent to gdb). It also generates compiler listings (files names *.lis) if you want to see the world from the C compiler's point of view with macros expanded, include files included, ifdef paths taken and not taken, etc.
A bit like: -Doptimize='-g' ?
-DDEBUGGING means the same thing it does no other platforms, i.e., build support for Perl's debugger. In case you don't know already, you do need to quote argumetns to configure.com to preserve case:
$ @configure -"DDEBUGGING" -"des"
This is done under the hood in Test::Smoke. I chose to not show it, to keep the reports looking the same for all platforms.
but DEBUGGING support is the default, so you'd really only need to specify it explicitly if you want to switch it off.
Okay, so do we want the results of -Dusevmsdebug in the reports?
Another question is about PerlIO. Does VMS support the PERLIO logical? If so, is there a difference between it being set to 'stdio' or 'perlio'?
Good luck,
Abe
--
The Enterprise is captured by a vastly superior alien intelligence which
does not put them on trial.
-- 20 Things that never happen in Star Trek #11
