×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

How to build KStars for Windows

  • Posts: 187
  • Thank you received: 28
I am looking for documentation on how to build KStars for Windows.
Can someone please tell me where to find it?
I want to run KStars under a debugger and investigate its bugs.
8 months 3 weeks ago #94523

Please Log in or Create an account to join the conversation.

  • Posts: 362
  • Thank you received: 114

Replied by nou on topic How to build KStars for Windows

AFAIK you should use craft community.kde.org/Craft that is official way that KStars is build for windows.
The following user(s) said Thank You: tkakura
8 months 3 weeks ago #94524

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
Thank you for the information.
I'm going to try a build next weekend.
8 months 3 weeks ago #94525

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
I was able to create a craft environment on Windows and investigate the cause of the following Issue.
www.indilib.org/forum/ekos/13635-capture...ount-up.html?start=0

There is one problem. I cannot watch some variables because the source code is compiled with optimization.
Is there a suitable way to suppress optimization in craft?

Or should I just build again with "BuildType=Debug" in /CraftRoot/etc/CraftSettings.ini?
8 months 3 weeks ago #94688

Please Log in or Create an account to join the conversation.

Yes that would work though it would require many dependent packages to be rebuilt again as Debug.
The following user(s) said Thank You: tkakura
8 months 3 weeks ago #94689

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
Thanks !
I will try it later.
8 months 3 weeks ago #94690

Please Log in or Create an account to join the conversation.

Great, please let us know if you can fix the regular expression issues on Windows. Would be great to get a confirmed fix from you regarding this.
8 months 2 weeks ago #94728

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
I do not understand the object structure of KStars.

Can you tell me the class name of the object that is suitable for storing the signatures and the member function that is called at the appropriate time?
I am guessing that it is a member function that is called when the Directory and Format are set to a sequence in the Capture module.
8 months 2 weeks ago #94729

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
I investigated it today.
Maybe I can fix it.
8 months 2 weeks ago #94738

Please Log in or Create an account to join the conversation.

  • Posts: 1187
  • Thank you received: 370
In the Capture module, the signature is checked in
CaptureProcess::prepareJob(SequenceJob * job)
.
The frame counts per signature are stored in
CaptureModuleState::m_capturedFramesMap

The Scheduler has its own counting. A good starting point is
uint16_t Scheduler::calculateExpectedCapturesMap(const QList<SequenceJob *> &seqJobs, QMap<QString, uint16_t> &expected)

HTH
Wolfgang
The following user(s) said Thank You: tkakura
8 months 2 weeks ago #94740

Please Log in or Create an account to join the conversation.

  • Posts: 187
  • Thank you received: 28
Thanks, I will check it later.

By the way, could you please enlighten me on the following two points in your development in Craft?

Q1.
Can I switch to my forked repository by following these steps?
cd <cloned directory of my forked kstars repository>
cs kstars

Q2.
Can you tell me how to compile only kstars with Optimize Option Og?
I tried "craft buildtype=Debug kstars" but it fails, because some libraries do not seem to support "buildtype=Debug".
8 months 2 weeks ago #94757

Please Log in or Create an account to join the conversation.

You don't need to clone just yet. You can always make a git diff and submit later. For the buildType=Debug, I also got this issue and left it as ReleasewithDebInfo which was sufficient for most debugging purposes. If you're using Visual Studio to debug, you need Qt Debug Helpers
The following user(s) said Thank You: tkakura
8 months 2 weeks ago #94759

Please Log in or Create an account to join the conversation.

Time to create page: 1.079 seconds