[Kstars-devel] Windows Packaging problems

Jasem Mutlaq mutlaqja at ikarustech.com
Sun May 22 06:36:59 UTC 2016


Hi Raphael,

I believe I found the reason why KDevelop 'emerge --package kdevelop'
works. As I suspected earlier, it has to do with the CMakelists.txt. Go
clone kdevelop and check out its CMakelists.txt, note on line 114. This is
where the magic happens, or so I *suspect*

Now, I don't know all the details, but it looks like CMake is resolving
dependencies for the package. It's not only in CMakelists.txt but there are
external files like KDevelopConfig.cmake.in

At any rate, your task now is to replicate this in KStars with changes as
necessary, then run emerge kstars and emerge --package kstars and let's see
what happens.

Please COMMIT any changes you make to your GSoC branch. Your GSoC branch
hasn't seen any activity, you need to show some activity on the branch for
public visibility (i.e. your work). Don't forget to sync with master first
(I already applied your Windows compile fix).

-- 
Best Regards,
Jasem Mutlaq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20160522/50352e00/attachment.html>


More information about the Kstars-devel mailing list