[gtkada] How to compile for debug
David C. Hoos, Sr.
david.c.hoos.sr at ada95.com
Mon Sep 4 12:37:04 CEST 2000
In order to compile a gnat program for debug, the binder and
linker must know about it, as well as the compiler.
So... instead of -cargs -g, just put -g on the command line
following gnatmake.
Also, remember that the argument sets -cargs, -bargs, and -largs
must be the last thing on the command line, so if you're going
to use these, they should come after the `gtkada-config`.
Since what you have here is a gnat question, rather than a
gtkada question, I suggest that the best place to look for
answers is in the Gnat User's Guide.
----- Original Message -----
From: Robert B. Love <rlove at neosoft.com>
To: <gtkada at gtkada.eu.org>
Sent: September 03, 2000 5:44 PM
Subject: [gtkada] How to compile for debug
> Actually, I have two questions.
>
> The first it how to compile for debug with gtkada? When I
> issue the command:
>
> % gnatmake my_main.adb -cargs -g `gtkada-config`
>
> I get this error:
>
> gnatmake: "gtk.adb" not found
>
> It seems like it wants to recompile some or all of the gtkada
> source. If I don't have the cargs -g then everything builds
> fine. So, what is the trick to compile with debugging turned
> on? I don't want to look at gtkada code, just my own.
>
> Second question is, is there an archive of this mailing list
> so I can look there first before asking here?
>
>
> ----------------------------------------------------------------
> Bob Love
> rlove at neosoft.com
> ----------------------------------------------------------------
>
>
> _______________________________________________ gtkada mailing list
gtkada at gtkada.eu.org http://gtkada.eu.org/cgi-bin/mailman/listinfo/gtkada
>
More information about the gtkada
mailing list