Merge lp:~thomas-voss/location-service/fix-zesty-ftbfs into lp:location-service
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Thomas Voß | ||||
Approved revision: | 298 | ||||
Merged at revision: | 298 | ||||
Proposed branch: | lp:~thomas-voss/location-service/fix-zesty-ftbfs | ||||
Merge into: | lp:location-service | ||||
Diff against target: |
151 lines (+17/-11) 10 files modified
debian/control (+1/-0) debian/control.in (+1/-0) snapcraft.yaml (+2/-0) src/location/providers/fusion/provider.h (+2/-0) src/location/providers/gps/android_hardware_abstraction_layer.cpp (+1/-0) src/location/providers/gps/android_hardware_abstraction_layer.h (+2/-0) src/location/providers/gps/sntp_client.cpp (+1/-0) src/location/providers/proxy.h (+1/-0) src/location/providers/ubx/_8/assist_now_online_client.cpp (+2/-0) tests/CMakeLists.txt (+4/-11) |
||||
To merge this branch: | bzr merge lp:~thomas-voss/location-service/fix-zesty-ftbfs | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Thomas Voß | Approve | ||
Review via email: mp+321479@code.launchpad.net |
Commit message
Fix location-service FTBFS on zesty, mainly tracked on LP: #1640320
There are 2 compound causes for the FTBFS:
1. googletest update that caused cmake errors
2. missing vector includes that caused undefined reference errors
== googletest update issues ==
The googletest updated error is better described on LP: #1644062. The same fix applied to cmake-extras [1] (see comment #3 [2]) allows to detect and set the right paths for gtest and gmock, but then it runs into the same problem as comment #7 [3] which again causes the build to fail because dh_install complains about the extra files installed by googletest. This issue is better described by the commit that introduced the googletest install clause [4] and the comments there indicate that bundling googletest is not recomended - it should instead be added as an external project. This is exactly the approach taken by GMockConfig.make [5] file in cmake-extras does. The proposed solution for the first part of the FTBFS fix is to rely on that to properly reference and include both gtest and gmock.
== missing vector includes ==
The missing includes for vector causes yet another FTBFS. The includes used in this merge are simple a suggestion, I'm not familiar with location-service code so it is very likely that there is a better place to put those (or even use a different include).
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] http://
Description of the change
Fix location-service FTBFS on zesty, mainly tracked on LP: #1640320
There are 2 compound causes for the FTBFS:
1. googletest update that caused cmake errors
2. missing vector includes that caused undefined reference errors
== googletest update issues ==
The googletest updated error is better described on LP: #1644062. The same fix applied to cmake-extras [1] (see comment #3 [2]) allows to detect and set the right paths for gtest and gmock, but then it runs into the same problem as comment #7 [3] which again causes the build to fail because dh_install complains about the extra files installed by googletest. This issue is better described by the commit that introduced the googletest install clause [4] and the comments there indicate that bundling googletest is not recomended - it should instead be added as an external project. This is exactly the approach taken by GMockConfig.make [5] file in cmake-extras does. The proposed solution for the first part of the FTBFS fix is to rely on that to properly reference and include both gtest and gmock.
== missing vector includes ==
The missing includes for vector causes yet another FTBFS. The includes used in this merge are simple a suggestion, I'm not familiar with location-service code so it is very likely that there is a better place to put those (or even use a different include).
[1] https:/
[2] https:/
[3] https:/
[4] https:/
[5] http://
LGTM.