From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10267 invoked by alias); 2 Dec 2011 17:39:27 -0000 Received: (qmail 10179 invoked by uid 22791); 2 Dec 2011 17:39:25 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 02 Dec 2011 17:39:06 +0000 Received: (qmail 85184 invoked by uid 13447); 2 Dec 2011 17:39:05 -0000 Received: from unknown (HELO [172.20.0.42]) ([71.33.34.251]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 2 Dec 2011 17:39:05 -0000 Message-ID: <4ED90D35.6070306@etr-usa.com> Date: Fri, 02 Dec 2011 17:39:00 -0000 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Cygwin-L Subject: Re: best way to prevent a cygwin build? References: <4ED88260.8010004@cs.cmu.edu> In-Reply-To: <4ED88260.8010004@cs.cmu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-12/txt/msg00025.txt.bz2 On 12/2/2011 12:46 AM, Paul Allen Newell wrote: > > I am not happy with having to run two separate source trees and would > like a way (as in "best standard") to add something to any Maya makefile > which will prevent execution if it is being compiled on Cygwin. You might get better answers if you give an example of what you mean by "prevent execution". Not because we don't know what that means in general, but because it *is* too general. For example, if what you were after is to have some programs in a system compiled conditionally, Automake + Autoconf makes that easy: https://www.gnu.org/s/hello/manual/automake/Conditional-Programs.html If you want something else suppressed, the answer might be different. Generally speaking, any time you want to do some up-front tests for platform compatibility issues that affect how a program gets built, Autoconf is probably a good answer. It is not a pretty tool, but it's one of those tools that keeps getting reinvented poorly, so it remains the most popular out of lack of better alternatives. On one of my projects, I use another Automake competitor, Bakefile. Bakefile builds Autoconf Makefile.in files, generic GNU Makefiles, Visual C++ project files, Xcode project files, etc., all from a single high-level description of what you want built. You can include things conditionally based on platform or pretty much any criterion you can code up in a Python extension to Bakefile. Bakefile is not in the Cygwin package repo, however, partly because it doesn't build cleanly on Cygwin. The native Windows port works just fine with Cygwin, though. You might also look at cmake, which competes with the Autotools and Bakefile, and *is* in the Cygwin package repo. I can't tell you anything more about it. -- 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