From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: [ot] Windows programming
Date: Thu, 21 Jun 2007 20:37:41 -0700 [thread overview]
Message-ID: <20070622033741.GB27880@localhost.localdomain> (raw)
In-Reply-To: <000701c7b477$f91e5110$ab00a8c0@tenstac>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Another option for a development environment is microsoft's windows
services for unix:
http://www.microsoft.com/downloads/details.aspx?FamilyID=896C9688-601B-44F1-81A4-02878FF11778&displaylang=en
If you want to use an ide, which uses mingw as the compiler, check out
dev-c++:
http://www.bloodshed.net/dev/devcpp.html
It's fairly accessible with wineyes, a bit more so after I created a set
file and key label dictionary for it.
As for a win32 tutorial, I found:
http://winprog.org/tutorial/
to be useful.
Since we're discussing this on here, does anyone know of anything for
c/c++ that would abstract the win32 api a bit more, so it wouldn't be
such a chore to program for it, making it a bit easier to write win32
applications? Thanks.
Greg
On Thu, Jun 21, 2007 at 09:49:37PM -0500, Doug Sutherland wrote:
> The simplest windows programming environment for a linux programmer
> is of course GNU C, which you have already mentioned. Cygwin is more
> full functioned than MinGW but more complex and has a few quirks that
> I really do not like, for example it's installation process is bizarre and
> annoying, the way it maps windows directories to unix naming is weird,
> the options for file types can be confusing, and I found that sometimes
> its impossible to remove all of cygwin. It creates some files that just
> cannot be deleted, I hate software that does that. On the other hand
> it's an impressive environment, you can almost have it look exactly
> like a linux machine.I have used Cygwin and MinGW and I have to
> say that MinGW was simple in the way I like it. I do not like complex
> development environments. I don't want to spend a week just to
> figure out how to do hello world. MinGW is faster to get actually
> programming with, and although limited in comparison, was just
> right for my needs. It has the win32 API:
>
> http://www.mingw.org/docs.shtml#win32api
>
> I did some win32 with this and I loved it because it's GNU and very
> straightforward. The Win32 API however is extremely complex and
> very annoying. Surprised? <g> Your battle will be more one of
> understanding the win32 API that one of tools. It can take quite a
> while to do the simplest of things with win32. I would recommend
> looking for some small tutorials, that's what I did and found a few
> that got me started. Find a getting started tutorial for MinGW and
> look for really simple win32 examples. I didn't do any win32 serial
> code but you can most likely find some examples on the net.
> I don't know anything about SAPI.
>
> -- Doug
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGe0QF7s9z/XlyUyARAr9VAJ9Q4DhtxWl6bd6Qgxosh67tY8ztSACgxUEf
2I8gFT7o1+4dP96aW6Ro3Rw=
=xtxk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Shane
` Kerry Hoath
` Doug Sutherland
` Gregory Nowak [this message]
` Steve Holmes
` Littlefield, tyler
` Gregory Nowak
` Littlefield, tyler
[not found] ` <20070623200010.GA30877@cm.nu>
` Kerry Hoath
` Travis Siegel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070622033741.GB27880@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).