X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <25189372.post@talk.nabble.com> References: <25188895 DOT post AT talk DOT nabble DOT com> <25189372 DOT post AT talk DOT nabble DOT com> Date: Fri, 28 Aug 2009 09:04:02 -0400 Message-ID: Subject: Re: Cannot get 'Hello World' to compile From: "Mark J. Reed" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 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 On Fri, Aug 28, 2009 at 8:51 AM, ken j wrote: > That was it - using g++ as the compiler and changing the file name to .cpp > The executable file was placed in my cygwin/home/username folder. Do I have > to specify that folder in the set path variable for Cygwin to see it? I'm > not entirely clear on this issue. You can always specify the path to an executable, in which case its directory doesn't have to be in your $PATH. If you've just compiled it, it's probably in the same directory you're in, and you can just do ./name to run it. If what you've created is a useful program that you want to keep around and be able to run as a command without specifying the path every time, then the thing to do is move it into a directory that's in your $PATH. Many people have a "bin" directory in their home directory for adding their own commands to the system, and put "$HOME/bin" in the front of their $PATH. -- Mark J. Reed -- 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