mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-05-10 13:12:56 +00:00
92f8514a85
These ones all manage their storage internally, whereas the WebContent and ImageDecoder ones require the caller to manage their lifetime. This distinction is not obvious to the user without looking through the code, so an API that makes this clearer would be nice.
24 lines
768 B
C++
24 lines
768 B
C++
/*
|
|
* Copyright (c) 2021, timmot <tiwwot@protonmail.com>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <FileSystemAccessServer/ClientConnection.h>
|
|
#include <LibCore/LocalServer.h>
|
|
#include <LibCore/System.h>
|
|
#include <LibGUI/Application.h>
|
|
#include <LibIPC/ClientConnection.h>
|
|
#include <LibMain/Main.h>
|
|
|
|
ErrorOr<int> serenity_main(Main::Arguments)
|
|
{
|
|
TRY(Core::System::pledge("stdio recvfd sendfd rpath cpath wpath unix thread"));
|
|
|
|
auto app = GUI::Application::construct(0, nullptr);
|
|
app->set_quit_when_last_window_deleted(false);
|
|
|
|
auto socket = TRY(Core::LocalSocket::take_over_accepted_socket_from_system_server());
|
|
(void)IPC::new_client_connection<FileSystemAccessServer::ClientConnection>(move(socket), 1);
|
|
return app->exec();
|
|
}
|