From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115339 invoked by alias); 9 Sep 2018 03:41:39 -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 115324 invoked by uid 89); 9 Sep 2018 03:41:37 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=mingw X-HELO: mail-it0-f49.google.com Received: from mail-it0-f49.google.com (HELO mail-it0-f49.google.com) (209.85.214.49) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 09 Sep 2018 03:41:27 +0000 Received: by mail-it0-f49.google.com with SMTP id f14-v6so25446557ita.4 for ; Sat, 08 Sep 2018 20:41:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=A0u+XJWh7ajpcI19HDcvgRPF5N6hPzFxF1AfB+dk6wg=; b=Ale7bV0rjKVfJAT3hYYAjwxBl8aFhW4y54+eTJcsfH8j6veJlDDBQJA+8ezqaRJ0lx /nN2KVK1YPX8D3KRDPJCeXTDenTaqrQrbiE3fz7/36eRnxsUV8Q0x/RxJDC8/uvQ7RpN ebi2lsegi7oeZnWgsZ1VNP2PTnQjPPf3oD1Qb8bKjwl++EQDJP2LE1/4MlzvYeGaCSKW BM6+UxaHSUoJ3btHirOARx6z40pqBWVVMr0xEI+heeHAYcf5LlNkAoI8sayQ9QUIPPRb K3TfR8+51ewlzKXYrlsqaDVTHZjmYZmVoxxhaLocjq+x7AvyYg3Nijxq7uyB89s7DyeV FhQQ== Return-Path: Received: from [192.168.0.16] ([69.47.131.109]) by smtp.gmail.com with ESMTPSA id u6-v6sm5179217itg.27.2018.09.08.20.41.24 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 08 Sep 2018 20:41:25 -0700 (PDT) Subject: Re: Advice on setting Cygwin build parameters for OpenSC. To: cygwin@cygwin.com References: <1536212829808-0.post@n5.nabble.com> <1677001344.20180906165924@yandex.ru> From: cyg Simple Openpgp: preference=signencrypt Message-ID: <1103e83d-9436-6ce3-1174-fae1c81db39a@gmail.com> Date: Sun, 09 Sep 2018 03:41:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00147.txt.bz2 On 9/6/2018 12:25 PM, Csaba Raduly wrote: > 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 ) The -mno-cygwin has been dead for a few several years now. The option is no longer available in current GCC. You now install the {x86_64,i686}-w64-mingw32 cross compilers and specify --host={x86_64,i686}-w64-mingw32 when you configure. > 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). > So to get Cygwin specific build you just don't specify the --host option. The change to configure.ac and supporting .m4 files is up to you. But -mno-cygwin isn't available if you plan to use current GCC regardless. -- cyg Simple -- 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