public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ronald Landheer-Cieslak <ronald@landheer.com>
To: "Baer, Scott [LBRT/LNA]" <Scott.Baer@liebert.com>
Cc: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: cygwin presentation ???
Date: Thu, 26 Jun 2003 10:54:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0306261126240.2545-100000@localhost.localdomain> (raw)
In-Reply-To: <51926FAD8BCBD411AA6C00508B69371C014D0477@ohfld02.liebert.com>

Sorry, should have spoken up sooner.

I am about to give a presentation on Cygwin (in french, so I don't have 
the same language problems cgf apparently had).

Basically, the red line in the presentation will be:
* Cygwin - what is it?
  * Cygwin - the - kernel
  * Cygwin - the - distribution
* Cygwin - what is it good for?
  * Kernel: POSIX emulation layer
  * Distri: UNIX-like working environment with many, many tools
* Cygwin distribution - what does it contain?
* Cygwin distribution - how to install (demo)
* Cygwin distribution - how to use (some examples of compiling, running, 
  handling the shell)
* Cygwin - what can WE use it for?
  * The utils we'll use here
    * Autotools
    * GNU Make
    * GNU Compiler Collection
  * How to use those utils in light of portability of the code
    * GCC C&C++ standards compliance
    * POSIX functions provided by Cygwin
    * Windows stuff not in Cygwin (structures exceptions)
* Cygwin - what is it not?
  * gcc != libc (a common mistake here, so I had to put it in)
  * Cygwin != UNIX

I don't show X because (mostly) I don't use it (I do everything on a 
console). I demonstrate just about everything with little programs I've 
prepared in advance that will or will not compile with Cygwin resp. MSVC. 
I also give a demonstration of Setup by partially installing the Cygwin 
net distro (I'll make sure not to have installed everything on the 
demonstration machine in advance, but I'll also install at least part of 
the distro so the installation doesn't take too long).

For the people here, I need to put the accent on gcc et al, and a bit less 
on Cygwin itself (the kernel). They're mostly Windows programmers used to 
GUIs, MSVC, Borland C++ Builder, etc. The goal is to at least be able to 
compile the programs under Cygwin so I have a bit less to do porting them 
to UNIX.

HTH

rlc

On Mon, 23 Jun 2003, Baer, Scott [LBRT/LNA] wrote:

> 
> Hello,
> 
> I'm getting ready to do a presentation to our local LUG on cygwin.. and
> wondered if anyone has put something together that I can work from ?  
> If not, I'm sure I can come up with something..  (basically the way I use
> it,.. remote X... but I know cygwin is so much bigger than that)
> 
> Just thought I would check first.
> 
> Thanks for your time,
> 
> Scott
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2003-06-26  9:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 20:36 Baer, Scott [LBRT/LNA]
2003-06-25 16:52 ` R. Scott Baer
2003-06-26  5:47   ` Larry Hall
2003-06-26  7:40     ` Christopher Faylor
2003-06-26 15:37       ` andrew brian clegg
2003-06-26 10:54 ` Ronald Landheer-Cieslak [this message]
2003-06-26 13:01 Brian.Kelly
2003-06-26 15:31 ` Max Bowsher
2003-06-27  3:01 ` Larry Hall
2003-06-27  7:41   ` Igor Pechtchanski
2003-06-27  3:35 ` Gary R. Van Sickle
2003-06-27 17:39 Brian.Kelly

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=Pine.LNX.4.44.0306261126240.2545-100000@localhost.localdomain \
    --to=ronald@landheer.com \
    --cc=Scott.Baer@liebert.com \
    --cc=cygwin@cygwin.com \
    /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).