mirrors/ladybird
0
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-09-25 02:38:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Meta: Change the default build directories to exclude "ladybird" prefix

Browse source 
The reason for this change is that CMake/vcpkg are unable to detect a
change to VCPKG_LIBRARY_LINKAGE. So when we switch to dynamic builds,
the switch would be non-functional, and every developer would have to
remove their Build and vcpkg cache directories manually. By changing
these directories, vcpkg is able to detect it must rebuild.
This commit is contained in:
Timothy Flynn 2024-09-30 09:55:48 -04:00 • committed by Andrew Kaster
commit 4ffca2089e
Notes: github-actions[bot] 2024-11-06 17:40:19 +00:00
9 changed files with 48 additions and 48 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Documentation/EditorConfiguration/EmacsConfiguration.md
View file

@ -7,7 +7,7 @@ Emacs can be configured with `lsp-mode` and `clangd` to work well.
The official clangd extension can be used for C++ comprehension.
Run cmake (`Meta/ladybird.sh run ladybird` or similar) at least once for clangd
to work, as doing so will generate the `Build/ladybird/compile_commands.json`
to work, as doing so will generate the `Build/release/compile_commands.json`
that is needed by `clangd`.
### lsp-mode

8
Documentation/EditorConfiguration/QtCreatorConfiguration.md
View file

@ -25,10 +25,10 @@ First, make sure you have a working toolchain and can build and run Ladybird. Go
Userland/
Userland/Libraries/
Userland/Services/
Build/ladybird/
Build/ladybird/Userland/
Build/ladybird/Userland/Libraries/
Build/ladybird/Userland/Services/
Build/release/
Build/release/Userland/
Build/release/Userland/Libraries/
Build/release/Userland/Services/
AK/
```

34
Documentation/EditorConfiguration/VSCodeConfiguration.md
View file

@ -28,7 +28,7 @@ Clangd has the best support for modern compilers, especially if configured as no
The official clangd extension can be used for C++ comprehension. It is recommended in general, as it is most likely to work on all platforms.
clangd uses ``compile_commands.json`` files to understand the project. CMake will generate these in Build/ladybird.
clangd uses ``compile_commands.json`` files to understand the project. CMake will generate these in Build/release.
Run ``./Meta/ladybird.sh run ladybird`` at least once to generate the ``compile_commands.json`` file.
@ -58,10 +58,10 @@ following ``c_cpp_properties.json`` to circumvent some errors. Even with the con
"name": "ladybird-gcc",
"includePath": [
"${workspaceFolder}",
"${workspaceFolder}/Build/ladybird/",
"${workspaceFolder}/Build/ladybird/Userland",
"${workspaceFolder}/Build/ladybird/Userland/Libraries",
"${workspaceFolder}/Build/ladybird/Userland/Services",
"${workspaceFolder}/Build/release/",
"${workspaceFolder}/Build/release/Userland",
"${workspaceFolder}/Build/release/Userland/Libraries",
"${workspaceFolder}/Build/release/Userland/Services",
"${workspaceFolder}/Userland",
"${workspaceFolder}/Userland/Libraries",
"${workspaceFolder}/Userland/Services"
@ -72,7 +72,7 @@ following ``c_cpp_properties.json`` to circumvent some errors. Even with the con
"cStandard": "c17",
"cppStandard": "c++23",
"intelliSenseMode": "linux-gcc-x86",
"compileCommands": "Build/ladybird/compile_commands.json",
"compileCommands": "Build/release/compile_commands.json",
"compilerArgs": [
"-Wall",
"-Wextra",
@ -81,16 +81,16 @@ following ``c_cpp_properties.json`` to circumvent some errors. Even with the con
"browse": {
"path": [
"${workspaceFolder}",
"${workspaceFolder}/Build/ladybird/",
"${workspaceFolder}/Build/ladybird/Userland",
"${workspaceFolder}/Build/ladybird/Userland/Libraries",
"${workspaceFolder}/Build/ladybird/Userland/Services",
"${workspaceFolder}/Build/release/",
"${workspaceFolder}/Build/release/Userland",
"${workspaceFolder}/Build/release/Userland/Libraries",
"${workspaceFolder}/Build/release/Userland/Services",
"${workspaceFolder}/Userland",
"${workspaceFolder}/Userland/Libraries",
"${workspaceFolder}/Userland/Services"
],
"limitSymbolsToIncludedHeaders": true,
"databaseFilename": "${workspaceFolder}/Build/ladybird/"
"databaseFilename": "${workspaceFolder}/Build/release/"
}
}
],
@ -165,7 +165,7 @@ The following three example tasks should suffice in most situations, and allow y
"base": "$gcc",
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
]
}
],
@ -199,14 +199,14 @@ The following three example tasks should suffice in most situations, and allow y
"base": "$gcc",
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
]
},
{
"source": "gcc",
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
],
"pattern": [
{
@ -241,14 +241,14 @@ The following three example tasks should suffice in most situations, and allow y
"base": "$gcc",
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
]
},
{
"source": "gcc",
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
],
"pattern": [
{
@ -275,7 +275,7 @@ The following three example tasks should suffice in most situations, and allow y
],
"fileLocation": [
"relative",
"${workspaceFolder}/Build/ladybird"
"${workspaceFolder}/Build/release"
]
}
]