tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <cos...@gmail.com>
Subject Re: native connector tool chain
Date Mon, 21 May 2012 14:35:55 GMT
Sorry, haven't compiled on windows in last >10 years.
I suspect the easiest path would be cygwin and gcc.

If you want to use vcc - you need to find a way to generate the project
file with the right flags. One option would be to use the CMakeLists.txt -
you'll probably need to adjust the options and file list for windows. It
can generate native projects for both visual studio and eclipse. The file
is still there in main branch, the official solution is autoconf, but
sometimes it's good to consider alternatives too.

Costin

On Mon, May 21, 2012 at 5:05 AM, Mark Thomas <markt@apache.org> wrote:

> I am trying to build the 1.1.x native connector from trunk so I can test
> the changes I plan to make to support per socket time outs. I can build
> using dynamic linking but not statically. What tool chain are folks
> currently using to build the native connector binaries we currently ship?
>
> My current issue relates to statically linking to OpenSSL. I get the
> same failure with 1.0.c, 0.9.8x and 0.9.8k. I am using:
> - Visual Studio 6 + SP6
> - Win 2003 r2 Platform SDK
> - OpenSSL binaries from http://slproweb.com/products/Win32OpenSSL.html
> - Targeting 64-bit platform
>
> I am working through the VS6 GUI and the errors I am getting are
> variations of this:
> ssleay32MT.lib(t1_enc.obj) : error LNK2001: unresolved external symbol
> __GSHandlerCheck
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message