public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Bash silently truncates the Command Line when called programatically via CreateProcess as MAXPATHLEN was reduced to 8192 from 16384
Date: Wed, 28 May 2014 11:04:00 -0000	[thread overview]
Message-ID: <5385A486.4090900@tiscali.co.uk> (raw)
In-Reply-To: <CANMjiJqkm1pD5zuKWc_aRw8h9mzfdpwSkk6u6ybLmgHKGEd0PQ@mail.gmail.com>

On 27/05/14 14:19, Abhijit Bhattacharjee wrote:
> Yes, MSVS is Microsoft Visual Studio.
>
> and I am using the make for Windows

Using the Windows version of gmake to invoke Cygwin bash to call the 
Microsoft compiler seems a little complicated to me. Instead of gmake 
and bash, are you able to use 'nmake' (that comes with MSVC)?

Obviously, that is a non-Cygwin suggestion, and this is a Cygwin mailing 
list, so we wouldn't be able to help you with that here. However, by 
simplifying your call chain, the problems that you're experiencing might 
go away.

Dave.


--
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

  parent reply	other threads:[~2014-05-28  8:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 17:28 Abhijit Bhattacharjee
2014-05-26 20:38 ` Christopher Faylor
2014-05-27  3:18   ` René Berber
2014-05-27  6:54     ` Christopher Faylor
     [not found]       ` <CANMjiJpDU-aVxg1X8G_Lk8pKLEmXbs24+ieD=w3f8ZmQ2jdjTw@mail.gmail.com>
2014-05-27 22:11         ` Abhijit Bhattacharjee
2014-05-28  9:48           ` Christopher Faylor
2014-05-28 11:04           ` David Stacey [this message]
2014-05-28 19:48             ` Warren Young
2014-05-31 13:37               ` Abhijit Bhattacharjee
2014-05-31 17:55                 ` Cliff Hones
2014-05-31 19:22                 ` Christopher Faylor
2014-05-28 16:07 Houder
2014-05-28 17:59 ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5385A486.4090900@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).