public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "JP Shipherd" <jp@Nuance.COM>
To: <cygwin@sourceware.cygnus.com>
Subject: spawning nmake from a gnumake Makefile
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <001101be659b$2a269360$fe29a2ce@sneech.nuance.com> (raw)
Message-ID: <19990331194500.zpPF6VgGl6_4R5eEVK0RWgzfC4rZ-3RWH4JvMpBAfKY@z> (raw)

We've got a pretty UNIXy source tree that uses gnumake for the most part,
but there are some win32 platform specific parts of it.  We build these in
DevStudio and export the makefiles.  Then we put these all these projects
under win32 module with a gnumake Makefile that simply goes to the various
project subdirs and spawns nmake.

I've been stuck on B18 for a while because the following expression in a
Makefile hasn't worked since then:

NMAKE = MFLAGS= MAKEFLAGS= nmake

        @cd ../MFCWaveEdit/Wavetools; \
        $(NMAKE) /NOLOGO /F Wavetools.mak ALL
INCLUDE="$(INCLUDE);$(W32_NUANCE)/
include" \
                LIB="$(LIB);$(W32_NUANCE)/lib/win32" CFG=$(WTCNF$(OPTION))
OS=$(OS)

This worked fine in B18 but B19 and B20 complain:

Wwavetools.mak(1) : fatal error U1023: syntax error in expression
Stop.

Does anyone have any idea what changed and/or a strategy for modifying my
gnumakefile so it can work with the later betas?

Thanks,
--jp


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-03  9:28 JP Shipherd [this message]
1999-03-31 19:45 ` JP Shipherd
1999-03-03 10:46 Earnie Boyd
     [not found] ` < 19990303184725.13880.rocketmail@send103.yahoomail.com >
1999-03-03 11:36   ` JP Shipherd
1999-03-31 19:45     ` JP Shipherd
1999-04-01 17:53     ` Peter Moulder
1999-04-30 18:32       ` Peter Moulder
1999-03-31 19:45 ` Earnie Boyd

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='001101be659b$2a269360$fe29a2ce@sneech.nuance.com' \
    --to=jp@nuance.com \
    --cc=cygwin@sourceware.cygnus.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).