Port Foreground process assertion to RunningBoard.
<rdar://problem/61831863>
Created attachment 399157 [details] Patch
Comment on attachment 399157 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=399157&action=review r=me > Source/WebKit/Configurations/WebKit.xcconfig:60 > +// FIXME: It is unnecessary to link against AssertionServices with the latest SDK for the following platforms too. > +WK_ASSERTION_SERVICES_LDFLAGS_watchos = -framework AssertionServices; > +WK_ASSERTION_SERVICES_LDFLAGS_watchsimulator = -framework AssertionServices; > +WK_ASSERTION_SERVICES_LDFLAGS_appletvos = -framework AssertionServices; > +WK_ASSERTION_SERVICES_LDFLAGS_appletvsimulator = -framework AssertionServices; > +WK_ASSERTION_SERVICES_LDFLAGS_maccatalyst = -framework AssertionServices; Is this about building using the old SDK? (Do we do that?)
(In reply to Geoffrey Garen from comment #3) > Comment on attachment 399157 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=399157&action=review > > r=me > > > Source/WebKit/Configurations/WebKit.xcconfig:60 > > +// FIXME: It is unnecessary to link against AssertionServices with the latest SDK for the following platforms too. > > +WK_ASSERTION_SERVICES_LDFLAGS_watchos = -framework AssertionServices; > > +WK_ASSERTION_SERVICES_LDFLAGS_watchsimulator = -framework AssertionServices; > > +WK_ASSERTION_SERVICES_LDFLAGS_appletvos = -framework AssertionServices; > > +WK_ASSERTION_SERVICES_LDFLAGS_appletvsimulator = -framework AssertionServices; > > +WK_ASSERTION_SERVICES_LDFLAGS_maccatalyst = -framework AssertionServices; > > Is this about building using the old SDK? (Do we do that?) Yes, we need to keep building on shipping.
Committed r261860: <https://trac.webkit.org/changeset/261860> All reviewed patches have been landed. Closing bug and clearing flags on attachment 399157 [details].