Konstantin, On 6/18/14, 7:40 PM, Konstantin Preißer wrote: > Hi Christopher, > >> -----Original Message----- >> From: Christopher Schultz [mailto:ch...@christopherschultz.net] >> Sent: Thursday, June 19, 2014 1:31 AM >> To: Tomcat Developers List >> Subject: Re: Building tcnative on win32 [progress!] >> >> Konstantin, >> >> On 6/18/14, 5:54 PM, Konstantin Preißer wrote: >>>> -----Original Message----- >>>> From: Konstantin Preißer [mailto:kpreis...@apache.org] >>>> Sent: Wednesday, June 18, 2014 11:42 PM >>> >>>> Although Winrar.exe isn't a command-line tool, you can start it from >>>> command-line to extract a file. Unfortunately, when I try to run this >>>> command from an elevated cmd.exe to extract the OpenSSL source code >>>> package, WinRAR fails to create the Symlinks ("the system cannot find the >>>> specified path"): >>>> Start /wait "" "%ProgramFiles%\WinRAR\winrar.exe" x openssl- >> 1.0.1h.tar.gz >>> >>> OK, I think the problem is when running the above command, WinRAR uses >> a relative path to create a symlink which fails. It works if you specify an >> absolute path as target: >>> >>> Start /wait "" "%ProgramFiles%\WinRAR\winrar.exe" x openssl- >> 1.0.1h.tar.gz C:\MyFolder\OpenSSL-Output\ >>> >>> With this command it will extract it to C:\MyFolder\OpenSSL-Output\ and >> create the symlinks successfully. >>> >>> >>> Unfortunately, WinRAR is proprietary software (not free). I have >>> tried 7-Zip, but instead of actually creating the symlinks, it just >>> seems to copy the file to the path where the symlink should be >>> created. >> >> I was using 7za.exe and it was creating files whose contents contained >> the path-target of the symlink instead of what you describe above. >> >> I'd be perfectly happy if it would just duplicate the files instead of >> creating symlinks, but that does not seem to be the actual behavior. > > Sorry, you are right: After I looked at the files, I saw that 7z.exe created > files which contained only the path for the symlinks, instead of duplicating > the file. :( > > Unfortunately, I also have not found another tool which could duplicate the > symlink file or actually create the NTFS symlink other than WinRAR.
Seems like the intertubes agree. :( After more digging, it appears that OpenSSL, after making things a pain in the ass (broken "symlinks" on win32 tarball-expansions), the build process creates an inc32/openssl directory containing all of the C header files you might need. So, instead of sensibly using the OPENSSL_HOME where I expanded the source and build the library, I can simply copy inc32/openssl/*.h to somewhere else that then has include/openssl/*.h where tcnative's build can find it. tcnative is now compling, but it's having trouble locating the APR libraries. Time to take a break for some more World Cup action. It's much more fun than fighting builds on Windows. -chris
signature.asc
Description: OpenPGP digital signature
