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