From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Advice on setting Cygwin build parameters for OpenSC.
Date: Sun, 09 Sep 2018 03:41:00 -0000 [thread overview]
Message-ID: <1103e83d-9436-6ce3-1174-fae1c81db39a@gmail.com> (raw)
In-Reply-To: <CAEhDDbAwyOU4b+azs-PQuW7JPn8BJH_wzaukhx59Q12gjWk3Bw@mail.gmail.com>
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
prev parent reply other threads:[~2018-09-09 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 1:22 Darren Whobrey
2018-09-02 9:08 ` Hans-Bernhard Bröker
2018-09-06 5:47 ` dwhobrey
2018-09-06 14:05 ` Andrey Repin
2018-09-06 16:25 ` Csaba Raduly
2018-09-09 3:41 ` cyg Simple [this message]
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=1103e83d-9436-6ce3-1174-fae1c81db39a@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.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).