From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 75957 invoked by alias); 6 Sep 2018 16:25:54 -0000 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 Received: (qmail 75850 invoked by uid 89); 6 Sep 2018 16:25:53 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=dwhobrey, OpenSC, opensc, WND X-HELO: mail-qt0-f171.google.com Received: from mail-qt0-f171.google.com (HELO mail-qt0-f171.google.com) (209.85.216.171) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 06 Sep 2018 16:25:52 +0000 Received: by mail-qt0-f171.google.com with SMTP id g44-v6so12913391qtb.12 for ; Thu, 06 Sep 2018 09:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+9+he06pBYEGgnRvID8ZP3qVBS/raBxOzueHmLwOtqY=; b=LN34Dne8AwR9DUGWRRproH7YzxBdjPH2v75ihCvFH1s3CGu62lUF4sOUYhBZSVGN/5 SQln20qCrCXoTXQLmys+7drijwrplcQ1CGzQXUTbh/2v2/r46pGgVOxQKQotDI7l8Zg2 VxNYcstdEu6g67SwWpqf9Sgpuu5h9YceD8la6+zBtZdV/U9mQ3FXCsqtJumD8Buofa49 tGqQjEdfyVqVpTX7LDQpkUDi1X2NKK5KHTrLCS8vGJlAHTWFZgs6wh2swkS7L3i5gJWs kRTH3RgA1E4POABD59v+ObLquRQBuJHX8AS4QjYMkPEqJs24LI5D0Ht8kno5Qmw11r2w AN4w== MIME-Version: 1.0 Received: by 2002:ac8:2ef3:0:0:0:0:0 with HTTP; Thu, 6 Sep 2018 09:25:49 -0700 (PDT) In-Reply-To: <1677001344.20180906165924@yandex.ru> References: <1536212829808-0.post@n5.nabble.com> <1677001344.20180906165924@yandex.ru> From: Csaba Raduly Date: Thu, 06 Sep 2018 16:25:00 -0000 Message-ID: Subject: Re: Advice on setting Cygwin build parameters for OpenSC. To: cygwin list Cc: dwhobrey Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-09/txt/msg00121.txt.bz2 Hi Andrey, On Thu, Sep 6, 2018 at 3:59 PM, Andrey Repin wrote: > Greetings, dwhobrey! > >> Thank you for the feedback. >> WND would be _WIN32 builds. > > If you are going for native builds, why using Cygwin in the first place? > If you still want to use Cygwin for building, you have to install > cross-compilers and properly specify target host. In OpenSC's build system (configure.ac), the Cygwin-specific parts are 10-11 years old. "cygwin native = yes" means the old-style Mingw build ( -mno-cygwin ) to create native Win32 programs/libraries, whereas "cygwin native = no" means generating Cygwin programs/libraries (with CRYPTOKI_FORCE_WIN32 being forcibly - and probably incorrectly - defined). Csaba -- You can get very substantial performance improvements by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler So if you're looking for a completely portable, 100% standards-conformat way to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK) -- 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