feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity
Files
7b6543268885e66174938b0a0a7e932675d30de7
qt-creator/src/plugins/webassembly/webassemblydevice.h

11 lines
247 B
C
Raw Normal View History

Use SPDX license identifiers Replace the current license disclaimer in files by a SPDX-License-Identifier. Task-number: QTBUG-67283 Change-Id: I708fd1f9f2b73d60f57cc3568646929117825813 Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2022-08-19 15:59:36 +02:00
// Copyright (C) 2019 The Qt Company Ltd.
Remove GPL-3.0+ from license identifiers Since we also license under GPL-3.0 WITH Qt-GPL-exception-1.0, this applies only to a hypothetical newer version of GPL, that doesn't exist yet. If such a version emerges, we can still decide to relicense... While at it, replace (deprecated) GPL-3.0 with more explicit GPL-3.0-only Change was done by running find . -type f -exec perl -pi -e "s/LicenseRef-Qt-Commercial OR GPL-3.0\+ OR GPL-3.0 WITH Qt-GPL-exception-1.0/LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0/g" {} \; Change-Id: I5097e6ce8d10233993ee30d7e25120e2659eb10b Reviewed-by: Eike Ziller <eike.ziller@qt.io>
2022-12-21 10:12:09 +01:00
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
WebAssembly: Initial commit This change adds WebAssembly support in the shape of a plugin. - Auto-detection of the emsdk toolchain - Handling of "asmjs-unknown-emscripten" Abi - Binary detection of WebAssembly libraries - Auto-creation of a "WebAssembly runtime" device (with icon) - Runconfiguration that launches the application via the "emrun" tool which spawns a local web server and runs the application on the chosen web browser. Limitations: - So far only tested on Windows/MinGW and Linux - Not yet tested with Qt WebAssembly installation form the installer Only tested with self-built Qt and manually added kit - The attempt to launch an application via emrun, while a previous application is still running, will fail. The reason is that the web servers spawned by emrun listen to the same default port but serve only the content of one application. Possible solutions: We could either spawn the different web servers with different ports, or we could use one single web server instance which serves the whole default project location (home directory). Task-number: QTCREATORBUG-21068 Task-number: QTCREATORBUG-22249 Change-Id: I1a16fbe52382d45c37e9bc624a943a6ca475fa09 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2019-07-12 13:40:00 +02:00
#pragma once
WebAssembly: Convert to new plugin setup scheme Change-Id: I7d5def6084a0cc2cf164a4d72b693b44f8be7005 Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2023-11-24 15:33:31 +01:00
namespace WebAssembly::Internal {
WebAssembly: Initial commit This change adds WebAssembly support in the shape of a plugin. - Auto-detection of the emsdk toolchain - Handling of "asmjs-unknown-emscripten" Abi - Binary detection of WebAssembly libraries - Auto-creation of a "WebAssembly runtime" device (with icon) - Runconfiguration that launches the application via the "emrun" tool which spawns a local web server and runs the application on the chosen web browser. Limitations: - So far only tested on Windows/MinGW and Linux - Not yet tested with Qt WebAssembly installation form the installer Only tested with self-built Qt and manually added kit - The attempt to launch an application via emrun, while a previous application is still running, will fail. The reason is that the web servers spawned by emrun listen to the same default port but serve only the content of one application. Possible solutions: We could either spawn the different web servers with different ports, or we could use one single web server instance which serves the whole default project location (home directory). Task-number: QTCREATORBUG-21068 Task-number: QTCREATORBUG-22249 Change-Id: I1a16fbe52382d45c37e9bc624a943a6ca475fa09 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2019-07-12 13:40:00 +02:00
WebAssembly: Convert to new plugin setup scheme Change-Id: I7d5def6084a0cc2cf164a4d72b693b44f8be7005 Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2023-11-24 15:33:31 +01:00
void setupWebAssemblyDevice();
WebAssembly: Initial commit This change adds WebAssembly support in the shape of a plugin. - Auto-detection of the emsdk toolchain - Handling of "asmjs-unknown-emscripten" Abi - Binary detection of WebAssembly libraries - Auto-creation of a "WebAssembly runtime" device (with icon) - Runconfiguration that launches the application via the "emrun" tool which spawns a local web server and runs the application on the chosen web browser. Limitations: - So far only tested on Windows/MinGW and Linux - Not yet tested with Qt WebAssembly installation form the installer Only tested with self-built Qt and manually added kit - The attempt to launch an application via emrun, while a previous application is still running, will fail. The reason is that the web servers spawned by emrun listen to the same default port but serve only the content of one application. Possible solutions: We could either spawn the different web servers with different ports, or we could use one single web server instance which serves the whole default project location (home directory). Task-number: QTCREATORBUG-21068 Task-number: QTCREATORBUG-22249 Change-Id: I1a16fbe52382d45c37e9bc624a943a6ca475fa09 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io> Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2019-07-12 13:40:00 +02:00
WebAssembly: Convert to new plugin setup scheme Change-Id: I7d5def6084a0cc2cf164a4d72b693b44f8be7005 Reviewed-by: Alessandro Portale <alessandro.portale@qt.io>
2023-11-24 15:33:31 +01:00
} // WebAssembly::Interenal
Copy Permalink