On 25/05/2012 11:11 a.m., Alex Rousskov wrote:
> On 05/23/2012 10:20 PM, kshitij wrote:
>> Hi,
>> I need some help to run squid-3.0 or squid -3.1 on windows platform.
>>
>> I already tried the squid-2.7 binary at
>> http://squid.acmeconsulting.it/download/squid-2.7.STABLE8-bin.zip
>> The squid-2.7 binary works great.
>>
>> Now I want to move further and need to implement some icap
>> transformations. I understand that there is no stable binary
>> available for squid3.0+ windows port.
>> Would like to get some pointers on how to proceed such that a
>> squid-3.0+ windows can be created
>> Q1. Which branch of squid would be a good starting point for
>> compilation on windows.
> I am not a Windows expert so I hope others who recently worked on the
> Windows port will chime in, but if you get no responses, start with v3.1
> or later because v3.0 is no longer supported.
We have quite a lot of (very slow) progress on 3.2 for Windows, to the
point of compiling now with certain configure options (can't recall off
the top of my head what they are though sorry). The results are being
ported to 3.1 when its clear how to port properly, but in general 3.1 is
not expected to run on Windows without a *lot* more work. There is still
hope for 3.2 of someone with coding skills and interest in Windows has
time to donate for it.
>
>
>> Q2. Are there major stumbling blocks for a windows squid 3.0+ port or
>> the effort is more on compilation and then testing it out.
> I think the answer depends on your Squid needs. If you need just basic
> proxying functionality and do not care about performance, then making a
> successful build with minimal features may suffice. If your needs are
> more complex, you may have to optimize and/or add code to use
> Windows-specific APIs.
>
> For example, eCAP should work on Windows in principle, but the dynamic
> module loading code may need to be adjusted to deal with Windows DLLs.
>
> Overall, it may be easier and faster to deploy Squid in a Linux virtual
> machine running on a Windows host (while talking to your ICAP server
> running on Windows if needed) than to port Squid to (and especially
> optimize it on) Windows.
That is pretty much the state of it. If you need a working squid-3.x on
any kind of deadline Windows is not a viable/reliable option yet.
If you just have an interest in progressing the code to support Windows,
please jump right in. We have a special branch of code
(http://bzr.squid-cache.org/bzr/squid3/branches/mswin) which is closer
to working than squid 3.HEAD / trunk.
Amos
Received on Sun May 27 2012 - 09:33:21 MDT
This archive was generated by hypermail 2.2.0 : Sun May 27 2012 - 12:00:13 MDT