02d97aabf4
The rationale is explained in https://planet.kde.org/friedrich-kossebau-2023-06-28-include-also-moc-files-of-headers/ In case of KDEConnect, it impressively speeds up compilation. Before it took 390 seconds on a clean build and with this change it took 330 seconds. This is due to the mocs_compilation having to include the header files and thus all their headers. Due to the lots of small plugins we have, this means that the same headers must be compiled plenty of times. When we include the moc files directly in the C++ file, they are already available.
43 lines
850 B
C++
43 lines
850 B
C++
/**
|
|
* SPDX-FileCopyrightText: 2013 Albert Vaca <albertvaka@gmail.com>
|
|
*
|
|
* SPDX-License-Identifier: GPL-2.0-only OR GPL-3.0-only OR LicenseRef-KDE-Accepted-GPL
|
|
*/
|
|
|
|
#include "loopbacklinkprovider.h"
|
|
|
|
#include "core_debug.h"
|
|
|
|
LoopbackLinkProvider::LoopbackLinkProvider()
|
|
{
|
|
}
|
|
|
|
LoopbackLinkProvider::~LoopbackLinkProvider()
|
|
{
|
|
}
|
|
|
|
void LoopbackLinkProvider::onNetworkChange()
|
|
{
|
|
LoopbackDeviceLink *newLoopbackDeviceLink = new LoopbackDeviceLink(this);
|
|
Q_EMIT onConnectionReceived(newLoopbackDeviceLink);
|
|
|
|
if (loopbackDeviceLink) {
|
|
delete loopbackDeviceLink;
|
|
}
|
|
|
|
loopbackDeviceLink = newLoopbackDeviceLink;
|
|
}
|
|
|
|
void LoopbackLinkProvider::onStart()
|
|
{
|
|
onNetworkChange();
|
|
}
|
|
|
|
void LoopbackLinkProvider::onStop()
|
|
{
|
|
if (loopbackDeviceLink) {
|
|
delete loopbackDeviceLink;
|
|
}
|
|
}
|
|
|
|
#include "moc_loopbacklinkprovider.cpp"
|