<html><head><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head><body><div data-externalstyle="false" dir="ltr" style="font-family:Calibri,'Segoe UI',Meiryo,'Microsoft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','Khmer UI','Nirmala UI',Tunga,'Lao UI',Ebrima,sans-serif;font-size:12pt;"><div>It’s a bad bad really bad idea to make the build of OpenSSL “in-house” as you’ve been calling it... CMake SHOULD use the system openssl for distributions that have one already.</div><div> </div><div>If there are problems with that approach, then the problems should be addressed, but bringing a security component into “we have our own custom build of that which you must use”-land is NEVER a good idea.</div><div> </div><div>Just my opinion. Feel free to flame me if I’m wrong.</div><div> </div><div>I agree with your assessment that the build should produce a warning/error somewhere if CMake is built without openssl support, but I think you’ll find that a tough sell to some other important CMake devs. <span style='font-family: "Segoe UI Symbol","Apple Color Emoji";' data-externalstyle="false">😊</span></div><div> </div><div> </div><div>David C.</div><div> </div></div></body></html>