WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
186380
[Xcode] Opt out of the New Build System
https://bugs.webkit.org/show_bug.cgi?id=186380
Summary
[Xcode] Opt out of the New Build System
mitz
Reported
2018-06-06 19:58:56 PDT
In Xcode 10 beta 1, the New Build System is used by default. Until all projects in the stack are building successfully with the New Build System, we should opt out of using it. For command-line builds, I think this can be done by changing webkitdirs.pm to include -UseNewBuildSystem=NO in the xcodebuild command-line. For building from within Xcode, I think this can be done by changing the WebKit workspace at the root of the source tree. People opening individual projects in Xcode, or using their own workspaces, will need to change the project or workspace settings to select the Legacy Build System.
Attachments
Use the Legacy Build System in the workspace and in command-line builds
(2.42 KB, patch)
2018-06-06 20:05 PDT
,
mitz
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
mitz
Comment 1
2018-06-06 20:05:53 PDT
Created
attachment 342109
[details]
Use the Legacy Build System in the workspace and in command-line builds
WebKit Commit Bot
Comment 2
2018-06-06 22:09:29 PDT
Comment on
attachment 342109
[details]
Use the Legacy Build System in the workspace and in command-line builds Clearing flags on attachment: 342109 Committed
r232573
: <
https://trac.webkit.org/changeset/232573
>
WebKit Commit Bot
Comment 3
2018-06-06 22:09:31 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 4
2018-06-06 22:10:23 PDT
<
rdar://problem/40881265
>
Darin Adler
Comment 5
2018-06-07 09:13:14 PDT
(In reply to mitz from
comment #0
)
> In Xcode 10 beta 1, the New Build System is used by default. Until all > projects in the stack are building successfully with the New Build System, > we should opt out of using it.
Just curious: Which projects don’t build successfully with it?
Jonathan Bedard
Comment 6
2018-06-07 09:23:11 PDT
(In reply to Darin Adler from
comment #5
)
> (In reply to mitz from
comment #0
) > > In Xcode 10 beta 1, the New Build System is used by default. Until all > > projects in the stack are building successfully with the New Build System, > > we should opt out of using it. > > Just curious: Which projects don’t build successfully with it?
WebCore and WebKit are the big ones, but I think WebInspector has issues as well.
Darin Adler
Comment 7
2018-06-07 09:27:17 PDT
(In reply to Jonathan Bedard from
comment #6
)
> WebCore and WebKit are the big ones, but I think WebInspector has issues as > well.
Is someone working on that, or are we putting it off?
Jonathan Bedard
Comment 8
2018-06-07 09:35:15 PDT
(In reply to Darin Adler from
comment #7
)
> (In reply to Jonathan Bedard from
comment #6
) > > WebCore and WebKit are the big ones, but I think WebInspector has issues as > > well. > > Is someone working on that, or are we putting it off?
I think we're still determining who will be doing this. For the time being, we are putting it off, but I don't think we will be able to get away with pushing it back much farther than September or October.
mitz
Comment 9
2018-06-07 09:42:05 PDT
(In reply to Darin Adler from
comment #5
)
> (In reply to mitz from
comment #0
) > > In Xcode 10 beta 1, the New Build System is used by default. Until all > > projects in the stack are building successfully with the New Build System, > > we should opt out of using it. > > Just curious: Which projects don’t build successfully with it?
Last I tried, JavaScriptCore was the first project in the stack to fail to build. I should file a bug here to track that (I want it to be linked to the Apple-internal bug and I was too lazy to find that one last night).
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug