Jump to content

Welcome, Guest!

Be a part of CinemaVision today! Once registered and logged in, you will have access to public chat and your own private messenger, you can view and contribute guides, collaborate on the forums, review downloads, give reputation to your fellow members, contribute content and so much more. Registering is quick and completely free, so what are you waiting for?
   Sign In    Sign Up

Become a RedCarpet Club Member Today!

   Join Now
Sign in to follow this  

[Kodi News] Windows Developers - Kodi Needs You!

Recommended Posts

Windows Developers - Kodi Needs You!

It will probably come as a surprise to many of you that the active team of Kodi developers is tiny - millions of users and yet only a handful of volunteers spending their spare time to do all the technical stuff at the heart of Kodi. In turn, there is another handful of valuable people providing user support, forum moderation, supervision of the addon repo, and so on. Sometimes, we have a need for specific skills that the team does not currently have. Well, that's what has happened.

You can read all about the switch to Python3 here, an essential upgrade to one of the underlying tools which Kodi uses. This is a breaking change for us, and there is a lot of work that needs to be done to get things functional again. In turn, this has brought the lack of experience of (or even interest in) developing on the Windows platforms in the team to a crisis.

We are currently very short of active developers with in-depth, practical knowledge of developing and deploying C++ applications on Windows platforms, for both the both desktop and UWP versions of Kodi. We especially need people:

  • who know and understand CMake, to bring packaging of Windows dependencies into line with those of our other actively-developed platforms.
  • with knowledge of the UWP API, and an interest in implementing Kodi as a UWP app running on Xbox, etc.

We cannot hold up releases of Kodi just for one or two platforms, no matter how large or active they may be or how many users they have. So there is a real risk that if new blood does not join the team, at least UWP (XBox) will have to be dropped for Kodi v20 and probably even Matrix v19.

Put bluntly, we need Windows developers. If that is you, and you'd be willing and interested to work on a project like Kodi, then we'd love to hear from you. We really want to say that our existing developers would be able to mentor as much as required, and we will certainly assist as much as we can, but in reality you need to be self-reliant and sufficiently experienced to be able to hold your own. Kodi is not a starter project, more a serious mountain that few conquer; it's complex, but very rewarding too. A sense of adventure and enjoyment of unravelling mysteries and puzzles would help a lot.

Bottom line, without developer interest, the likelihood of there being a UWP release for v19 is slim, and v20 would be zero.

Your Kodi needs you!


Footnote: for those who may be interested, Team member Rechi has provided the following technical notes.

The current dependency system is mandatory for compilation on Android, iOS, macOS and tvOS. It can be also used for Linux, but we usually use system libraries (provided by the distribution). The process compiles all libraries needed for Kodi (link) from source, along with some required tools (link).

For Windows, however, pre-compiled libraries (except FFmpeg and libdvd) and executables are downloaded (download-dependencies.bat) and then used to build Kodi. Because some libs depend on other libs, one has to recompile all reverse dependencies to be sure everything is still working. If an issue then shows up within a library, that one has to be compiled again (and maybe also, in turn, its reverse dependencies), packaged and re-uploaded, instead of simply fixing the issue in source code.

Where we're trying to get to with Windows, then, is to have all necessary libraries compiled from source, as an integrated part of the build process, and thus replace the download-dependencies.bat, download-msys2.bat and make-mingwlibs.bat scripts.

The main changes for this can be found here as detailed in this pull request (link). It switches from downloading pre-compiled native executables to building them from source. Target libraries are only switched to compiling from source for x86-windows, arm-windowsstore, x86-windowsstore and x86_64-windowsstore, because it currently contains only required dependencies. This means those platforms will lose some functionality until the libs are added. This can be done one by one and I can guide anyone who is interested. Once all optional libraries are added, x86_64-windows platform can also be switched to this dependency system.


View the full article...

Share this post

Link to post
Share on other sites
This topic is now closed to further replies.
Sign in to follow this  

  • Create New...

Important Information

By using this site, you agree to our Guidelines and Terms of Use.