X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.3 required=5.0 tests=BAYES_00,FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <25193163.post@talk.nabble.com> Date: Fri, 28 Aug 2009 09:42:57 -0700 (PDT) From: ken j To: cygwin AT cygwin DOT com Subject: Re: Cannot get 'Hello World' to compile In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <25188895 DOT post AT talk DOT nabble DOT com> <25189372 DOT post AT talk DOT nabble DOT com> <25191024 DOT post AT talk DOT nabble DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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. Mark J. Reed wrote: > > 2) what does the command 'pwd' tell you? /home/username -- View this message in context: http://www.nabble.com/Cannot-get-%27Hello-World%27-to-compile-tp25188895p25193163.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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