X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Fri, 28 Aug 2009 12:52:31 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cannot get 'Hello World' to compile
Message-ID:	<20090828165231.GA26088@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<25188895 DOT post AT talk DOT nabble DOT com> <f60fe000908280531j433aa646s7a26de5c0154c54e AT mail DOT gmail DOT com> <25189372 DOT post AT talk DOT nabble DOT com> <f60fe000908280604j6924f3a6wb294edefbdff7e3d AT mail DOT gmail DOT com> <25191024 DOT post AT talk DOT nabble DOT com> <f60fe000908280741id85de4ck23d14f9846d0176f AT mail DOT gmail DOT com> <25193163 DOT post AT talk DOT nabble DOT com>
MIME-Version:	1.0
In-Reply-To:	<25193163.post@talk.nabble.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Fri, Aug 28, 2009 at 09:42:57AM -0700, ken j wrote:
>
>
>Mark J. Reed wrote:
>> 
>> On Fri, Aug 28, 2009 at 10:34 AM, ken j wrote:
>>>BTW I've found that I do NOT need to type './' but
>>> rather only '/' to get an exe file to run in Cygwin.
>> 
>> That's only true if the executable is in the root directory (c:\cygwin
>> in Windows, / in Cygwin).
>
>OK I see that now - I had been moving the compiled programs from
>C:\cgwin\home\username to c:\cygwin, actually because I didn't know about
>the './' command.
>
>Mark J. Reed wrote:
>> 
>>> Also, all of my compiled executables go to c:\cygwin\home\username, not
>>> the
>>> directory I'm in, which is c:\cygwin.
>> 
>> That makes no sense.   g++ -o file will put the executable in that
>> file in the current directory.  If it's going elsewhere, then you're
>> telling it to put it elsewhere.
>
>My mistake. I was IN the c:\cygwin\home\username directory, which is why the
>exe's went there. I then copied some of them to c:\cygwin, which made me
>able to run some with just '/' instead of './'
>
>
>
>Mark J. Reed wrote:
>> 
>> 1) Why do you keep reporting Windows paths when talking about Cygwin?
>> You're running these commands inside a Cygwin bash window, right?
>
>This illustrates my lack of understanding how paths work in cygwin. Yes all
>this programming effort is being done in a cygwin bash window.

It isn't paths in cygwin.  It is paths in UNIX.  That's what Cygwin is
emulating.

>Mark J. Reed wrote:
>> 
>> 2) what does the command 'pwd' tell you?
>
>/home/username

I'm not seeing a whole-lot of cygwin-specific issues here.  The cygwin
list is not here to help people get up to speed on how to program or how
to use UNIX.

I've been hoping that I won't have to step in and be mean but I would
appreciate it if you would find some other forum for working out your
beginner programming issues.

cgf

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

- Raw text -