nanogui: Thread: Win32/DOS build environment


[<<] [<] Page 1 of 1 [>] [>>]
Subject: Win32/DOS build environment
From: "Darran D. Rimron-Molloy" ####@####.####
Date: 6 Jul 2000 17:09:44 -0000
Message-Id: <003701bfe76d$07b18830$6e64a8c0@VERONICA>

I'm finally in a position to start hacking again (a very long story) but
it looks like I'm going to be forced to do it on a Win32 build
environment....

How do we stand on Freeware/Shareware/GPL'ed build environment on Win32?

    -Darran


Subject: Re: Win32/DOS build environment
From: "Greg Haerr" ####@####.####
Date: 6 Jul 2000 22:25:07 -0000
Message-Id: <01fe01bfe799$7d613b80$3017dbd0@censoft.com>

: I'm finally in a position to start hacking again (a very long story) but
: it looks like I'm going to be forced to do it on a Win32 build
: environment....

Hopefully your new wife isn't taking too much time ;-)



: 
: How do we stand on Freeware/Shareware/GPL'ed build environment on Win32?

Well, I think there should be no big problems if we use the gnu mingw32
compiler.  I would prefer this to cygwin.

A new screen driver will need to be built, which will be interesting,
since it links with code with exactly the same signatures as the actuall
win32 api.  So it will probably need to be a DLL and use GetProcAddress
and dynamic linking, rather than statically linked.

Regards,

Greg



Subject: Re: Win32/DOS build environment
From: "Darran D. Rimron-Molloy" ####@####.####
Date: 6 Jul 2000 23:21:43 -0000
Message-Id: <003701bfe7a1$134e6940$6e64a8c0@VERONICA>

> > How do we stand on Freeware/Shareware/GPL'ed build environment on
Win32?
> Search for MingW32 or CygWin.-
> Both are complete
> Mingw32 is the compiler and creates plain EXEs
> CygWIn is for those who has to port Posix (aka Unix's) apps

I have used both before, and seem to recall that someone made a build
environment for Borland C ( I can't even recall what version it was now)
which I have kicking around somewhere on a pile of floppy disks :-) but
I was checking to see if anyone had ported anying over to djgcc or
similar in the make files or if I was going to have to hack device
drivers myself (again, after hacking around with the Linux Console ones
oh-so-long ago....)

    -Darran

Subject: Re: Win32/DOS build environment
From: "Darran D. Rimron-Molloy" ####@####.####
Date: 6 Jul 2000 23:26:35 -0000
Message-Id: <004301bfe7a1$a742d870$6e64a8c0@VERONICA>

----- Original Message -----
From: "Greg Haerr" ####@####.####
To: "Darran D. Rimron-Molloy" ####@####.####
####@####.####
Sent: Thursday, July 06, 2000 11:28 PM
Subject: Re: Win32/DOS build environment


> : I'm finally in a position to start hacking again (a very long story)
but
> : it looks like I'm going to be forced to do it on a Win32 build
> : environment....
>
> Hopefully your new wife isn't taking too much time ;-)
>
Only in the very best ways :-)

> : How do we stand on Freeware/Shareware/GPL'ed build environment on
Win32?
> Well, I think there should be no big problems if we use the gnu
mingw32
> compiler.  I would prefer this to cygwin.

cygwin is a tad on the bloated side, I seem to recall in both devopment
and application manners, and I kinda don't like the commercial path it
has taken....

> A new screen driver will need to be built, which will be interesting,

And if an elephant stood on your toes it may hurt some -- Greg, master
of understatement speaks again.

> since it links with code with exactly the same signatures as the
actuall
> win32 api.  So it will probably need to be a DLL and use
GetProcAddress
> and dynamic linking, rather than statically linked.

I've got (aka, do or die) to write a contact management system for Linux
and Win32 and DOS so I decided to use nanogui, because I can.... :)
Plus not better way to learn it than to try, is there? :-)  I've still
got the MS-DirectDraw code I was using for a device driver back last
September kicking around somewhere, but I thought I'd go for a freeware
solution rather than comitting to VC++.

    -Darran

[<<] [<] Page 1 of 1 [>] [>>]


Powered by ezmlm-browse 0.20.