Annoying text window

Annoying text window

[jboulais]

I've recently switched from Gnat v. 3.04a to Gnat v. 3.11p as the
compiler for developing windows apps with ada.  I've found that with
Gnat v. 3.11p, even when just double-clicking the executable form
windows, I get a "DOS Window" that comes up an accompanies the windows
application that is running.  Is there any way to supress this text
window?  Thanks...


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Re: Annoying text window

[Martin C. Carlisle]

In article <7j0trd$7lq$1@nnrp1.deja.com>,  <jboulais@my-deja.com> wrote:
>I've recently switched from Gnat v. 3.04a to Gnat v. 3.11p as the
>compiler for developing windows apps with ada.  I've found that with
>Gnat v. 3.11p, even when just double-clicking the executable form
>windows, I get a "DOS Window" that comes up an accompanies the windows
>application that is running.  Is there any way to supress this text
>window?  Thanks...

You need to specify the -mwindows linker option.  You can do this either
on the command line, or (if using AdaGIDE) via Tools/GNAT Options in 
Current Directory, or (my preferred method) add the following to your
main program:

pragma Linker_Options("-mwindows");

--Martin

-- 
Martin C. Carlisle, Asst Prof of Computer Science, US Air Force Academy
carlislem@acm.org, http://www.usafa.af.mil/dfcs/bios/carlisle.html
DISCLAIMER:  This content in no way reflects the opinions, standards or 
policy of the US Air Force Academy or the United States Government.

Re: Annoying text window

[dennison]

In article <7jh2bh$u7p$1@nnrp1.deja.com>,
  Robert Dewar <robert_dewar@my-deja.com> wrote:
> In article <7jgq4e$r1o$1@nnrp1.deja.com>,
>   dennison@telepath.com wrote:
> > And of couse its a copyright violation to use that library if
> > you don't have Visual C++ installed. :-(
>
> This is a false statement, there is no requirement for
> Visual C++ to be installed. In any case, always take
> responsibility yourself for making sure you have appropriate
> licenses, or ask your vendor to help you make sure!

Yikes! That's right. I misread Martin's "-mwindows" as "-lwindows".
Unfortunately that's a pretty thin excuse, as it just makes me triply
wrong:

  1)  "-mwindows" is a special gcc linker flag for just this purpose
(see
http://sourceware.cygnus.com/cygwin/cygwin-ug-net/programming.html#GCC-G
UI for docs on it).

  2)  There's no such library as "libwindows.a" in gnat's win32
distribution anyway.

  3)  Even if there *were* such a library, there shouldn't be any
problem with just linking it in, as the Win32 libs were created from the
Microsoft DLL's using automated tools, which is really no different than
if they were read by some shrink-wrapped product I bought (eg: Sid
Meyer's Alpha Centauri). Microsoft may diagree on this point, though.
For instance, they might try to claim that this constitutes
"dissasembly", which the EULA prohibits.

The problem arises (I really hope I'm getting it right this time) when
you try to *compile* against the win32 bindings (Ada source code).
That's roughly because that code that was created using knowledge gained
directly from Microsoft souce code.

--
T.E.D.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Re: Annoying text window

[dennison]

In article <7j610c$llg$1@cnn.Princeton.EDU>,
  mcc@entropy.cs.princeton.edu (Martin C. Carlisle) wrote:
> In article <7j0trd$7lq$1@nnrp1.deja.com>,  <jboulais@my-deja.com>
wrote:
> >I've recently switched from Gnat v. 3.04a to Gnat v. 3.11p as the
> >compiler for developing windows apps with ada.  I've found that with
> >Gnat v. 3.11p, even when just double-clicking the executable form
> >windows, I get a "DOS Window" that comes up an accompanies the
windows
> >application that is running.  Is there any way to supress this text
> >window?  Thanks...
>
> You need to specify the -mwindows linker option.  You can do this
either
> on the command line, or (if using AdaGIDE) via Tools/GNAT Options in
> Current Directory, or (my preferred method) add the following to your
> main program:
>
> pragma Linker_Options("-mwindows");

Of couse that means you have to have libmswindows.a in your libarary
path. And of couse its a copyright violation to use that library if you
don't have Visual C++ installed. :-(

--
T.E.D.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Re: Annoying text window

[Robert Dewar]

In article <7jgq4e$r1o$1@nnrp1.deja.com>,
  dennison@telepath.com wrote:
> And of couse its a copyright violation to use that library if
> you don't have Visual C++ installed. :-(

This is a false statement, there is no requirement for
Visual C++ to be installed. In any case, always take
responsibility yourself for making sure you have appropriate
licenses, or ask your vendor to help you make sure!


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Re: Annoying text window

[Larry Kilgallen]

In article <7jgq4e$r1o$1@nnrp1.deja.com>, dennison@telepath.com writes:

> Of couse that means you have to have libmswindows.a in your libarary
> path. And of couse its a copyright violation to use that library if you
> don't have Visual C++ installed. :-(

Are you sure ?  That seems quite strange.

I would expect such a restriction to be that it is a copyright violation
unless the machine is licensed for Visual C++, but requiring installation
is not something I have encountered.

Larry Kilgallen

Re: Annoying text window

[dennison]

In article <7jh2bh$u7p$1@nnrp1.deja.com>,
  Robert Dewar <robert_dewar@my-deja.com> wrote:
> In article <7jgq4e$r1o$1@nnrp1.deja.com>,
>   dennison@telepath.com wrote:
> > And of couse its a copyright violation to use that library if
> > you don't have Visual C++ installed. :-(
>
> This is a false statement, there is no requirement for
> Visual C++ to be installed. In any case, always take
> responsibility yourself for making sure you have appropriate
> licenses, or ask your vendor to help you make sure!

Yikes! That's right. I misread Martin's "-mwindows" as "-lwindows".
Unfortunately that's a pretty thin excuse, as it just makes me triply
wrong:

  1)  "-mwindows" is a special gcc linker flag for just this purpose
(see
http://sourceware.cygnus.com/cygwin/cygwin-ug-net/programming.html#GCC-G
UI for docs on it).

  2)  There's no such library as "libwindows.a" in gnat's win32
distribution anyway.

  3)  Even if there *were* such a library, there shouldn't be any
problem with just linking it in, as the Win32 libs were created from the
Microsoft DLL's using automated tools, which is really no different than
if they were read by some shrink-wrapped product I bought (eg: Sid
Meyer's Alpha Centauri). Microsoft may diagree on this point, though.
For instance, they might try to claim that this constitutes
"dissasembly", which the EULA prohibits.

The problem arises (I really hope I'm getting it right this time) when
you try to *compile* against the win32 bindings (Ada source code).
That's roughly because that code that was created using knowledge gained
directly from Microsoft souce code.

--
T.E.D.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.