ca4dbabf70
Nothing beyond the example module was ever built with the PythonQt bindings, as far as I can tell. They have been deprecated, defaulting OFF for over two years now. QML modules fill the gap with customizable, run-time interpreted UI and stronger support from the C++ side of Calamares.
31 lines
1.1 KiB
C
31 lines
1.1 KiB
C
/* === This file is part of Calamares - <https://calamares.io> ===
|
|
*
|
|
* SPDX-FileCopyrightText: 2020 Adriaan de Groot <groot@kde.org>
|
|
* SPDX-License-Identifier: GPL-3.0-or-later
|
|
*
|
|
* Calamares is Free Software: see the License-Identifier above.
|
|
*
|
|
*/
|
|
#ifndef CALAMARESCONFIG_H
|
|
#define CALAMARESCONFIG_H
|
|
|
|
#define CMAKE_INSTALL_PREFIX "${CMAKE_INSTALL_PREFIX}"
|
|
#define CMAKE_INSTALL_FULL_LIBEXECDIR "${CMAKE_INSTALL_FULL_LIBEXECDIR}"
|
|
#define CMAKE_INSTALL_LIBDIR "${CMAKE_INSTALL_LIBDIR}"
|
|
#define CMAKE_INSTALL_FULL_LIBDIR "${CMAKE_INSTALL_FULL_LIBDIR}"
|
|
#define CMAKE_INSTALL_FULL_DATADIR "${CMAKE_INSTALL_FULL_DATADIR}/calamares"
|
|
#define CMAKE_INSTALL_FULL_SYSCONFDIR "${CMAKE_INSTALL_FULL_SYSCONFDIR}"
|
|
|
|
/*
|
|
* These are feature-settings that affect consumers of Calamares
|
|
* libraries as well; without Python-support in the libs, for instance,
|
|
* there's no point in having a Python plugin.
|
|
*
|
|
* This list should match the one in CalamaresConfig.cmake
|
|
* which is the CMake-time side of the same configuration.
|
|
*/
|
|
#cmakedefine WITH_PYTHON
|
|
#cmakedefine WITH_QML
|
|
|
|
#endif // CALAMARESCONFIG_H
|