X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.1 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: References: <4A221A61.2050207@cygwin.com> <17393e3e0905310011i3b6bd318ud323d64a9fe3581b@mail.gmail.com> <416096c60905310156n523dd947xfb73bdd6acfac83f@mail.gmail.com> <4A2290CC.8000004@gmail.com> Date: Sun, 31 May 2009 19:27:47 +0400 Message-ID: Subject: Re: Win2k Command Window Can't Execute G++ From: Alexey Borzenkov To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Sun, May 31, 2009 at 6:36 PM, Roger Head wrote: > Ummmm... errrr.... no, no, that's too easy. There must be a harder way to do it. As an alternative you can try looking into my http://git.kitsu.ru/mine/shell-wrapper.git (use snapshot link for topmost commit if you don't have git and don't know how to clone) Basically, for any command in bin you can create a .exe file in C:\cygwin\bin-public, which you can later add to your PATH. If will work for any cygwin executable, because it goes thru a wrapper that runs the command with cygwin's exec functions. First run make, then look at makewrappers.cmd for example of how I use it myself. -- 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/