[QGIS-Developer] Suggestion for improved macOS build compatibility testing

[Tom Elwertowski]

Hi Matthias,

I build QGIS dependencies mostly from source. I don't use homebrew or 
macports. When I started, fink was popular and very useful for the first 
few months. Once I became familiar with Unix-style tools however, 
building directly from source was less problematic than dealing with the 
external issues in package managers.

Currently, I install Qt binaries and Kyngchaos frameworks and use 
configure/make for everything else. I can document the steps. I haven't 
in the past because people asking for mac builds have said they are not 
developers.

After review of my build process, we can determine if it can be automated.

Tom


On 4/26/18 2:19 PM, Matthias Kuhn wrote:
> Hi Tom,
> 
> Sorry to hear that. In the past we had macOS continuous integration 
> tests in place but had to disable them, because the package manager used 
> there (homebrew) was breaking dependencies unpredictably (I don't think 
> that's unexpected news for you if you are building on mac though ;) )
> 
> There is no "verification machine" on linux, but there is a docker 
> image. However I am not sure how easy it is to modify this image put 
> headers in different folders and make all the executables (xxx-config) 
> return the modified paths - while keeping the infrastructure maintainable.
> 
> Alternatively, I would very much like to get the mac builds back up and 
> running. I don't think we can do this again with the upstream homebrew 
> repo since we don't want our pull requests flagged erroneous for 
> external problems. The best alternative I see is, that we need a curated 
> list of formulae in a separate repository, which would not only help the 
> testing but potentially also the release process. Would you be 
> interested in taking a lead on this?
> 
> Best regards
> 
> Matthias
> 
> 
> On 04/26/2018 07:58 PM, Tom Elwertowski wrote:
>> Hi all,
>>
>> Both yesterday and today, the macOS build failed due to missing CMake 
>> INCLUDE specifications.
>>
>> MacOS puts each framework in a separate directory while Linux merges 
>> everything into /usr/local. Thus, Linux commits will compile when a 
>> new dependency is added as long as some other dependency already 
>> specifies /usr/local.
>>
>> Here is an idea that would help macOS build compatibility. Place each 
>> dependency on the verification build machine in a separate directory 
>> such as
>> /usr/local/gdal-2.2.3/
>> /usr/local/geos-3.6.1/
>>
>> This would make commits fail upfront on Linux if CMake INCLUDES needed 
>> by macOS were missing.
>>
>> Tom
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>
> 
> -- 
> Matthias Kuhn
> matthias at opengis.ch <mailto:matthias at opengis.ch>
> +41 (0)76 435 67 63 <tel:+41764356763>
> OPENGIS.ch Logo <http://www.opengis.ch>
> 
> 
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>