You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finally, run `ninja` (or the generator you're using) to start the build:
130
130
131
131
```
132
-
ninja -CBuild/release
132
+
ninja -C Build/release
133
133
```
134
134
135
135
For more information, see [Custom CMake build directory](#custom-cmake-build-directory) and [Running manually](#running-manually).
136
136
137
137
### macOS:
138
138
139
-
Xcode 14 versions before 14.3 might crash while building ladybird. Xcode 14.3 or clang from homebrew may be required to successfully build ladybird.
139
+
Xcode 15 or clang from homebrew is required to successfully build ladybird.
140
140
141
141
```
142
142
xcode-select --install
@@ -214,7 +214,7 @@ The simplest way to build and run ladybird is via the ladybird.sh script:
214
214
215
215
```bash
216
216
# From /path/to/ladybird
217
-
./Meta/ladybird.sh run ladybird
217
+
./Meta/ladybird.sh run
218
218
```
219
219
220
220
On macOS, to build using clang from homebrew:
@@ -231,11 +231,14 @@ The above commands will build a Release version of Ladybird. To instead build a
231
231
`Meta/ladybird.sh` script with the value of the `BUILD_PRESET` environment variable set to `Debug`, like this:
232
232
233
233
```bash
234
-
BUILD_PRESET=Debug ./Meta/ladybird.sh run ladybird
234
+
BUILD_PRESET=Debug ./Meta/ladybird.sh run
235
235
```
236
236
237
237
Note that debug symbols are available in both Release and Debug builds.
238
238
239
+
If you want to run other applications, such as the headless-browser, the JS REPL, or the WebAssembly REPL, specify an
240
+
executable with `./Meta/ladybird.sh run <executable_name>`.
241
+
239
242
### The User Interfaces
240
243
241
244
Ladybird will be built with one of the following browser frontends, depending on the platform:
@@ -305,9 +308,9 @@ a suitable C++ compiler (g++ >= 13, clang >= 14, Apple Clang >= 14.3) via the CM
305
308
CMAKE_C_COMPILER cmake options.
306
309
307
310
```
308
-
cmake -GNinja -B MyBuildDir
311
+
cmake --preset default -B MyBuildDir
309
312
# optionally, add -DCMAKE_CXX_COMPILER=<suitable compiler> -DCMAKE_C_COMPILER=<matching c compiler>
310
-
cmake --build MyBuildDir
313
+
cmake --build --preset default MyBuildDir
311
314
ninja -C MyBuildDir run-ladybird
312
315
```
313
316
@@ -367,15 +370,8 @@ Simply run the `ladybird.sh` script as normal, and then make sure to codesign th
367
370
368
371
Now you can open the Instruments app and point it to the Ladybird app bundle.
369
372
370
-
If you want to use Xcode itself for debugging, you will need to generate an Xcode project.
371
-
The `ladybird.sh` build script does not know how to generate Xcode projects, so creating the project must be done manually.
372
-
373
-
```
374
-
cmake -GXcode -B Build/release
375
-
```
376
-
377
-
After generating an Xcode project into the specified build directory, you can open `ladybird.xcodeproj` in Xcode. The project has a ton of targets, many of which are generated code.
378
-
The only target that needs a scheme is the ladybird app bundle.
373
+
Building the project with Xcode is not supported. The Xcode project generated by CMake does not properly execute custom
374
+
targets, and does not handle all target names in the project.
0 commit comments