<div dir="ltr">Hi,<br><div class="gmail_extra"><div><div class="gmail_signature"><br></div></div>
<br><div class="gmail_quote">On Mon, Sep 5, 2016 at 12:00 AM, Nyall Dawson <span dir="ltr"><<a href="mailto:nyall@north-road.com" target="_blank">nyall@north-road.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 5 September 2016 at 15:51, Matthias Kuhn <<a href="mailto:matthias@opengis.ch">matthias@opengis.ch</a>> wrote:<br>
><br>
> Hi<br>
><br>
> On 09/05/2016 07:06 AM, Nyall wrote:<br>
> > I was just digging in to the new build errors for the OSX Travis builds,<br>
> > and was led to this discussion:<br>
> ><br>
> > <a href="https://github.com/Homebrew/homebrew-core/issues/4365" rel="noreferrer" target="_blank">https://github.com/Homebrew/<wbr>homebrew-core/issues/4365</a><br>
> ><br>
> > My understanding is that this is game over for the Qt4 homebrew builds.<br>
> > Am I mistaken here?<br>
> ><br>
> > If so - is it time to "call it" and kill Qt4 support in master? I was<br>
> > hoping to get all the unit tests passing under the Travis Qt5 builds<br>
> > first but am now wondering if that's just needlessly prolonging things.<br>
> > Some of the current blacklist could be much easier to address if we<br>
> > don't need to care about backward compatibility.<br>
><br>
> What's the connection between having Qt4 support in the code and<br>
> shipping Qt5 builds on Mac?<br>
<br>
</span>I explained that badly - I was thinking mostly about what the fastest<br>
way to get some supported osx version back up and running again is. If<br>
i'm understanding the implications of that homebrew issue correctly,<br>
there's now no way of building master (or even 2.16) on osx.<br></blockquote><div><br></div><div>I have been working on this for ~ a day. Later today and throughout next week I will be working on a resolution for these issues. Sorry for the delay.</div><div><br></div><div>Larry Shaffer<br>Dakota Cartography<br>Black Hills, South Dakota<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Which lead in a roundabout way to thinking about the quickest way to<br>
resolve the remaining qt5 test failures and how to avoid spending<br>
*any* more wasted minutes on qt4 compatibility ;)<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Nyall<br>
</font></span><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<br>
<br>
<br>
><br>
> I don't mind too much dropping Qt4 support. So far I didn't see any<br>
> reason to do it and thought there are more urgent issues where time can<br>
> be invested (having mac builds for 2.16, having Qt5 mac builds, having<br>
> Qt5 Windows builds, sorting out API issues...). If you say that there<br>
> are blacklisted tests (or other things) which can be resolved easier<br>
> without Qt4, I think we should just proceed.<br>
><br>
> Matthias<br>
><br>
> ><br>
> > Nyall<br>
> ><br>
> ><br>
> ><br>
> > <<a href="http://north-road.com" rel="noreferrer" target="_blank">http://north-road.com</a>>       *North Road*<br>
> > Cartography • Development • Spatial Analysis<br>
> > ------------------------------<wbr>------------------------------<wbr>------------<br>
> > *<a href="http://north-road.com" rel="noreferrer" target="_blank">north-road.com</a>* <<a href="http://north-road.com" rel="noreferrer" target="_blank">http://north-road.com</a>><br>
> > <<a href="https://twitter.com/northroadgeo" rel="noreferrer" target="_blank">https://twitter.com/<wbr>northroadgeo</a>><<a href="https://www.facebook.com/North-Road-997236690392419/home" rel="noreferrer" target="_blank">https://www.<wbr>facebook.com/North-Road-<wbr>997236690392419/home</a>><<a href="https://www.linkedin.com/company/north-road-studios" rel="noreferrer" target="_blank">https://<wbr>www.linkedin.com/company/<wbr>north-road-studios</a>><<a href="https://plus.google.com/b/108321726558543789406" rel="noreferrer" target="_blank">https://<wbr>plus.google.com/b/<wbr>108321726558543789406</a>><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Qgis-developer mailing list<br>
> > <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> > List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
> > Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
> ><br>
> ______________________________<wbr>_________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
> Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
______________________________<wbr>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a></div></div></blockquote></div><br></div></div>