X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.3 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: <4B7DA704.1080709@cygwin.com> References: <98f79fac1002180955m1ddea014id0b27cc3b909a17a AT mail DOT gmail DOT com> <4B7D80B3 DOT 4000300 AT cygwin DOT com> <98f79fac1002181224g7987690dn6822d025d1a59405 AT mail DOT gmail DOT com> <4B7DA704 DOT 1080709 AT cygwin DOT com> Date: Fri, 19 Feb 2010 13:37:34 +0100 Message-ID: <98f79fac1002190437g5fec3138mb2c7e24d8f03212a@mail.gmail.com> Subject: Re: CreateProcess() - executed program gets different argument depending if it's compiled with gcc (cygwin) or cl (VS)? From: Piotr Krukowiecki To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 Thu, Feb 18, 2010 at 9:45 PM, Larry Hall (Cygwin) wrote: > On 02/18/2010 03:24 PM, Piotr Krukowiecki wrote: >> On Thu, Feb 18, 2010 at 7:02 PM, Larry Hall (Cygwin) >>> On 02/18/2010 12:55 PM, Piotr Krukowiecki wrote: >>>> - if the executed program is compiled with cygwin's gcc the program >>>> receives \127.0.0.127\foo.cxx (just one backslash at the begining). >>>> - if it's compiled with cl it gets \\127.0.0.127\foo.cxx (double >>>> backslash - what I expected) >>> >>> '\' is an escape character in C, Unix, and Linux. =A0In Windows, it's a >>> path separator. =A0Use '/' instead when working with Cygwin and you'll >>> avoid allot of problems. =A0Better yet, use POSIX paths exclusively. >> >> "\\hostname" is remote path location, I don't think I can use >> "//hostname" instead, either for cygwin program and especially not for >> not-cygwin program, can I? (can't check it now) > > With Windows, you're free to use either path separator. =A0With Cygwin, > you're life will be easier if you use '/' though it will accept '\' too if > properly escaped. > > Cygwin understands UNC path syntax using '/'. =A0I would expect > Windows to be cranky about '//' as a UNC path indicator though. > If you need the source to compile, link, and run appropriately > on either compiler, then you need to port it so it will, if that's > what you're concerned about. ok, so it works for paths - but what about other arguments, that are not paths, just simple strings? They are also changed. String "search \\me" is not the same as "search //me". Example: given two "grep"-like programs, one compiled with cygwin, one compiled without cygwin, I have to CreateProcess() with different argument (different search string) to achieve same results - otherwise one will search a file for "search \me" and the other for "search \\me". I don't know which program (cygwin/windows) is going to be executed. Do I have to check before execution if the program is compiled under cygwin and implement different logic in that case? From what I understood so far this is the only way? --=20 Piotr Krukowiecki -- 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