Re: Windows 95 port

[jsp@xxxxxxxxxxxxx (John Pawling)]

All,

Dave Harris, VDA, is one of the lead developers on the SFL project.  Dave
writes:

>John,
>    I think the answer to this question depends partly on what the user
>wants to do.  If the user intends to use the source we provide with the
>Crypto++ CTI, then that user would need Microsoft Visual C++ v5.0.  The user
>would use MSVC50 to build the Free CTI Library, the Crypto++ 2.3 library,
>and the SFL.
>    In theory, the user could use another compiler (Borland, for example) to
>build the library, however, we have not tried this.  Also, because static
>libraries are not the same between different compilers, a Borland user would
>need to rebuild the SNACC library as well.
>    While we haven't packaged the snacc compiler for Windows, in theory a
>user could use the snacc 1.3 baseline and our patches to generate the
>compiler so they could compile asn files on Windows.  This would require
>flex and bison as snacc requires them.  Again, I should emphasize that we
>currently do our asn compiling on the sun.  
<snip>
>    So, to do what we've done (excluding ASN compiling), all you need is
>MSVC50.
>dave

================================
John Pawling, jsp@xxxxxxxxxxxxx                             
J.G. Van Dyke & Associates, Inc.   
www.jgvandyke.com         
================================


At 10:38 AM 3/27/98 -0800, Paul Hoffman / IMC wrote:
>What will someone need to use the library with Win95? Which compilers and
>other toolkits?
>
>--Paul Hoffman, Director
>--Internet Mail Consortium
>