forked from qt-creator/qt-creator
f5dde31558
On macOS, files in Contents/PlugIns/ need to be codesigned individually. Since Lua plugins are not really binaries, per Apple's documentation that is to be avoided (and we currently only sign executables there). Just move Lua plugins generally to the resources directory, like we do for other scripts like the debugger Python scripts, and load them from there. Change-Id: Idabd6b7c0c7c6e842b1752488cb7073f00e7be49 Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
21 lines
666 B
Lua
21 lines
666 B
Lua
-- Copyright (C) 2024 The Qt Company Ltd.
|
|
-- SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GPL-3.0-only WITH Qt-GPL-exception-1.0
|
|
return {
|
|
Name = "LuaTests",
|
|
Version = "1.0.0",
|
|
CompatVersion = "1.0.0",
|
|
Vendor = "The Qt Company",
|
|
Category = "Tests",
|
|
DisabledByDefault = true,
|
|
Experimental = true,
|
|
Description = "This plugin tests the Lua API.",
|
|
LongDescription = [[
|
|
It has tests for (almost) all functionality exposed by the API.
|
|
]],
|
|
Dependencies = {
|
|
{ Name = "Lua", Version = "14.0.0" }
|
|
},
|
|
setup = function() require 'tests'.setup() end,
|
|
printToOutputPane = true,
|
|
} --[[@as QtcPlugin]]
|