On 10/16/2013 5:25 AM, Brian Sidebotham wrote: > I patched the LuaDist CMake build system to work successfully on OpenSSL > 1.0.1e. > > Downloading, patching and building OpenSSL with CMake on Windows has an > issue though (Doesn't everything being built on Windows!?) > > The issue is that CMake, or more precisely libarchive used by CMake > doesn't deal with symbolic links on Windows. Even 7z doesn't deal with > them at all well either. The source archive for OpenSSL includes > symbolic links in the include directory. > > 7z outputs an ascii file with a line of text that is the relative path > to the actual file. Not very useful, but this was at least parse-able > and therefore fixable in CMake. > > CMake -E tar fails with the message: "Cannot create \". There's plenty > of information about this, and a fix is targeted at the 2.8.12 > release: http://www.cmake.org/Bug/print_bug_page.php?bug_id=13251 > > It may work okay under the MSYS shell actually - I've not tried as I > don't have it.
I successfully built OpenSSL using the MSYS shell. It does build, test, and install properly for 32 bit builds. It even installs ssleay32.dll in /mingw/bin instead of /mingw/lib which is where most autotools installs end up. > > I'm unsure how we will get around this problem on Windows. > > Best Regards, > > Brian. > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp