Re: Building Cyrus SASL 2.1.26 on Win 64
Karthikeyan Manivannan <[email protected]>
| Newsgroups | gmane.comp.security.cyrus.sasl |
|---|---|
| Message-ID | <CY1PR16MB0110D2CE7BFB697D85D14105C35A0@CY1PR16MB0110.namprd16.prod.outlook.com> |
Sorry for not being clearer with my question: If I try to run nmake /f NTMakefile, the build fails in the plugins folder because of some missing plugin dependencies (openssl, DB etc). All I want to build is the sasl lib dll and the 'plain' plugin. My use case is as follows: I have written a Cyrus SASL plugin that implements a proprietary authentication mechanism. I have tested this on Linux and now I want to test this on Windows. Before I test my plugin, I want to sanity-check the setup and sasl lib build by using the 'plain' mechanism. I managed to build just the lib and 'plain' plugin by changing the PLUGINS variable in plugins/NTMakefile. I was just wondering if there was a cleaner way to do this? ________________________________ From: WinPORTS <[email protected]> Sent: Thursday, February 16, 2017 1:12:44 PM To: Karthikeyan Manivannan Cc: [email protected]; Alexandru N. Barloiu Subject: Re: Building Cyrus SASL 2.1.26 on Win 64 > but the simple solution is to make a virtual machine. and just use > linux. on windows. food for thought. > of one in existence). sorry. curious. It looks like this fella forgot to take his pill (or perhaps on the blob)! :-[ >> What do I need to do if I want to replicate the same on a Win64 machine? What have you tried so far? Any error messages? We have successfully built it on (native) Windows.