Thank you everyone for your time and reply. I believe from your reply
I am able to get the problem sorted out. I would also try to reply to
each of your queries
@Chris J. Breisch
@Warren Young
Qs/Stmt: Why are you using that make and not the Cygwin make?
Qs/Stmt: I suggest that you switch to
On 31/05/2014 14:28, Abhijit Bhattacharjee wrote:
...
Qs/Stmt: Possibly setting the CYGWIN environment variable to noglob
might cause things to work as desired.
Ans: I am yet to test this, but I trust your answer. I am yet to
figure out as to how I can set the environment variables CYGWIN
On Sat, May 31, 2014 at 06:58:59PM +0530, Abhijit Bhattacharjee wrote:
Thank you everyone for your time and reply. I believe from your reply
I am able to get the problem sorted out. I would also try to reply to
each of your queries
@Christopher Faylor
Qs/Stmt: A Cygwin program which calls another
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
Hi Abhijit,
Please note, when I am saying the path is getting truncated, its the
bash that is truncating it. Also, its immaterial how and what is
getting called. With the latest Cygwin, any program that is compiled
and linked with the CRT would exhibit this behavior. The truncation
issue in
On Wed, May 28, 2014 at 05:41:19PM +0200, Houder wrote:
As far as I can tell, it is not bash, but the Cygwin supervisor, that
does the truncation.
The code in Cygwin has already been repeatedly identified.
Possibly setting the CYGWIN environment variable to noglob might
cause things to work as
On 5/28/2014 02:55, David Stacey wrote:
are you able to use 'nmake' (that comes with MSVC)?
nmake is awfully primitive in itself compared to GNU make, and it is
doubly crippled by being restricted to cmd.exe syntax for shell commands
in the targets.
Instead, Abhijit, I suggest that you
Yes, MSVS is Microsoft Visual Studio.
and I am using the make for Windows
(http://gnuwin32.sourceforge.net/packages/make.htm).
Please note, when I am saying the path is getting truncated, its the
bash that is truncating it. Also, its immaterial how and what is
getting called. With the latest
On Tue, May 27, 2014 at 06:49:43PM +0530, Abhijit Bhattacharjee wrote:
Yes, MSVS is Microsoft Visual Studio.
and I am using the make for Windows
(http://gnuwin32.sourceforge.net/packages/make.htm).
Please note, when I am saying the path is getting truncated, its the
bash that is truncating it.
On a typical configuration, we use gmake on windows as the build
system. GMAKE calls the Cygwin bash in order to invoke the MSVS
compiler in-order to satisfy the dependency if a rule to call the
compiler is present.
Now, for certain modules, the command line was seemingly getting
truncated. On
On Mon, May 26, 2014 at 08:59:56PM +0530, Abhijit Bhattacharjee wrote:
On a typical configuration, we use gmake on windows as the build
system. GMAKE calls the Cygwin bash in order to invoke the MSVS
compiler in-order to satisfy the dependency if a rule to call the
compiler is present.
If you're
On 5/26/2014 3:08 PM, Christopher Faylor wrote:
If you're using Cygwin's make it will not truncate paths if it is
running cygwin programs. Not sure what MSVS is.
Microsoft Visual Studio (or Something)?
--
René Berber
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On Mon, May 26, 2014 at 03:38:13PM -0500, René Berber wrote:
On 5/26/2014 3:08 PM, Christopher Faylor wrote:
If you're using Cygwin's make it will not truncate paths if it is
running cygwin programs. Not sure what MSVS is.
Microsoft Visual Studio (or Something)?
Probably.
cgf
--
Problem
13 matches
Mail list logo