Changes between Initial Version and Version 1 of Ticket #65354
- Timestamp:
- Jun 16, 2022, 3:02:37 PM (23 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #65354 – Description
initial v1 1 1 The other day a new revision (3) of iTerm2 was released and it still gives some of us users of older systems problems due to `SafeAreaInsets`, which seems to be related to the notch on newer Macs. 2 2 3 As the iTerm2 project development seems to have left the 3.4 .15-erait may be possible that a submission to George Nachman would not necessarily be expediently addressed for source builds, I submit here a workaround source code- and Portfile patch that removes any use of `SafeAreaInsets` which were identified in now closed [ticket:63824]. This solves the build problems for at least MacOS 10.15, but will likely solve similar problems on 10.14 as well.3 As the iTerm2 project development seems to have left the 3.4-era and moved on to working on v3.5, it may be possible that a submission to George Nachman would not necessarily be expediently addressed for source builds, I submit here a workaround source code- and Portfile patch that removes any use of `SafeAreaInsets` which were identified in now closed [ticket:63824]. This solves the build problems for at least MacOS 10.15, but will likely solve similar problems on 10.14 as well. 4 4 5 5 There have been indications (see the closed ticket above) that also MacOS 11 may have this issue, so maybe the initial tests for `${os.major}` in the Portfile should be set to `> 20` instead of `${os.major} > 19`, but I do not have a MacOS 11 machine to test this on, so I played safe and put what I can test there. If someone wants to test on a MacOS 11 system and incorporate these fixes, feel free to just test that, it may work if you have issues building.