<html>
<head>
    <base href="https://wiki.asterisk.org/wiki">
            <link rel="stylesheet" href="/wiki/s/en/2171/18/9/_/styles/combined.css?spaceKey=TOP&amp;forWysiwyg=true" type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Building+on+Windows">Building on Windows</a></h2>
    <h4>Comment <b>removed</b> by              <a href="https://wiki.asterisk.org/wiki/display/~beagles">Brent Eagles</a>
    </h4>
    <br/>
    <div class="notificationGreySide">
        <p>Follow-up on platform support: For clarification, it's not just an issue of which platforms can handle the failover process we want. (Although that is indeed an  issue). There's also the issue of which platforms are we going to test our own software on, and provide support for. For example, for now, we aren't going to try to support any MS compiler prior to 2008. We likely could, but differences in handling of C++ templates and other headaches just aren't worth it. Since we're a brand new project, we shouldn't worry so much about the platforms and development tools people were using 10 years ago unless we find a very compelling reason to, which would be community driven. </p>
    </div>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;" class="grey">
                        <a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=TOP">Stop watching space</a>
            <span style="padding: 0px 5px;">|</span>
                <a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
    </div>
</div>
</div>
</div>
</div>
</body>
</html>