X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48B706FB.4CAE7693@dessent.net> Date: Thu, 28 Aug 2008 13:13:47 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: "cygwin AT cygwin DOT com" Subject: Re: Probably stupid make question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Phil Smith wrote: > We're perverting CMake and Cygwin make to use a cross-compiler for z/OS (IBM mainframe). We've beaten it mostly into submission, but are hitting an issue with definitions being passed. Cygwin make seems to be passing them in the format: > -Dvarname value > rather than: > -Dvarname=value > and the cross-compiler doesn't like that much. Some discussion with more *IX-savvy friends suggests that the "blank" format is older, and is deprecated due to ambiguity (does "-Dvarname abc.c xyz.c" mean "set varname to abc.c and compile xyz.c", or "set varname to 1 and compile abc.c and xyz.c"?). I think you're going to have to be more specific, such as providing a testcase that reproduces the problem. This must be due to some aspect of cmake, because there's nothing in plain make (AFAIK) that has anything to do with how -D or any other parameter is passed to any tool -- make executes commands exactly as written in the Makefile, no more no less. Brian -- 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/