KDEConnect/Build Windows: Difference between revisions
Line 88: | Line 88: | ||
We are only human! There are many questions that we face commonly, during DevSprints and during the onboarding of new contributors. Just skim through all the commonly asked questions so you don't have to ask around like others had to. | We are only human! There are many questions that we face commonly, during DevSprints and during the onboarding of new contributors. Just skim through all the commonly asked questions so you don't have to ask around like others had to. | ||
# '''I don't get the notification buttons, and the application name in the notifications is weird (something like <code>kdeconnect.daemon</code>. How do I fix it?''' | # '''I don't get the notification buttons, and the application name in the notifications is weird (something like <code>kdeconnect.daemon</code>. How do I fix it?''' | ||
#:Just run this command: | |||
Just run this command: | #:<syntaxhighlight lang="dosbatch"> | ||
<syntaxhighlight lang="dosbatch"> | |||
C:\CraftRoot\bin\SnoreToast.exe -install "KDE Connect DEV" "C:/CraftRoot/bin/kdeconnectd.exe" "kdeconnect.daemon" | C:\CraftRoot\bin\SnoreToast.exe -install "KDE Connect DEV" "C:/CraftRoot/bin/kdeconnectd.exe" "kdeconnect.daemon" | ||
</syntaxhighlight> | </syntaxhighlight> | ||
#:A detailed explanation is available [https://taskmaster9001.wordpress.com/2019/06/07/gsoc19-milestone-1/ here] and also in the code of Windows 10 backend for KNotifications [https://github.com/KDE/knotifications/blob/master/src/notifybysnore.cpp#L33 here]. | |||
A detailed explanation is available [https://taskmaster9001.wordpress.com/2019/06/07/gsoc19-milestone-1/ here] and also in the code of Windows 10 backend for KNotifications [https://github.com/KDE/knotifications/blob/master/src/notifybysnore.cpp#L33 here]. | |||
# '''How can I contact the KDE Connect team? I'd like to talk to the team about an issue/ suggestion.''' | # '''How can I contact the KDE Connect team? I'd like to talk to the team about an issue/ suggestion.''' | ||
#: | |||
#:* Telegram: You can find a link to our Telegram group [https://community.kde.org/Telegram here]. | |||
#:* IRC on Libera Chat: #kdeconnect | |||
#:* Mailing List: [https://mail.kde.org/mailman/listinfo/kdeconnect https://mail.kde.org/mailman/listinfo/kdeconnect] | |||
#:* email ID: [email protected] | |||
''Be sure to let us know if you got stuck somewhere in the process of setting up the developer environment. You can [mailto:[email protected] mail us]. Yes, we read the mails!'' | |||
''Be sure to |
Revision as of 07:18, 21 July 2021
KDE Connect works quite well on Windows, with all plugins ported over from the OG Linux app.
Get a compiler
The environment for KDE Connect on Windows simply consists of two parts- A compiler of choice and a build system. While we do have a couple of options for the compiler, our recommended build system is Craft. This is a comprehensive build guide. However, you should definitely refer to Craft's documentation for further information on using the build system in your development environment!
Choose your compiler
MSVC (full-support) | minGW (partial support)
Right now, MSVC does the best job as a compiler for KDE Connect for Windows.
MSVC
- Install Visual Studio 2019 (Community) from here and select Desktop development with C++.
- Install these packages.
minGW
- Install MinGW-w64 through the GUI installer located here.
- While installing Craft, select Mingw-w64 as your compiler.
Note that due to the lacking of some definitions in the minGW headers, some plugins could not be compiled with all functions on Windows using MinGW. Patches are certainly welcome!
Install Craft
- Call the following commands in a Powershell window with Administrator Privileges
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/KDE/craft/master/setup/install_craft.ps1'))
- During command 2, select Visual Studio 19 if you chose MSVC earlier, otherwise Mingw-w64 as your compiler.
- When the installation is done, note the Environment variables to match the ones in the top of this image:-
Build KDE Connect
Craft has automated most of the redundant parts of the build process and exposed just the really useful parameters like which version to build, where to install et al.
- Open Craft CraftRoot from search (in taskbar).
Once you have the terminal open, head over to this link for further instructions.
[OPTIONAL] Build a redistributable installer
- Open
CraftRoot/etc/CraftSettings.ini
- To make an EXE installer, set
PackageType
toNullsoftInstallerPackager
.
- TO make an AppX installer, set
PackageType
toAppxPackager
.
- TO make an AppX installer, set
- Now you can use the
--package
flag to build to instruct Craft to build an installer.craft --package kdeconnect-kde
Note: The output files are saved in: CraftRoot/tmp/
FAQs : FREQUENTLY ASKED QUESTIONS
We are only human! There are many questions that we face commonly, during DevSprints and during the onboarding of new contributors. Just skim through all the commonly asked questions so you don't have to ask around like others had to.
- I don't get the notification buttons, and the application name in the notifications is weird (something like
kdeconnect.daemon
. How do I fix it? - How can I contact the KDE Connect team? I'd like to talk to the team about an issue/ suggestion.
-
- Telegram: You can find a link to our Telegram group here.
- IRC on Libera Chat: #kdeconnect
- Mailing List: https://mail.kde.org/mailman/listinfo/kdeconnect
- email ID: [email protected]
-
Be sure to let us know if you got stuck somewhere in the process of setting up the developer environment. You can mail us. Yes, we read the mails!