So since you modified the cmakelists, if you do a git pull and nobody changes that file, then you are fine and it will merge with the other changes. But if somebody edits cmakelists,txt, you might have to undo your change or delete the file, or reset the repo before doing the git pull. You will know that it is a problem because it will refuse to git pull in that case.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 15 hours 14 minutes ago

Probably not too much. I always do. I only run into problems when things get too far out of date on either system or when somebody breaks something

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 15 hours 38 minutes ago

So whether it is forked-build or just build depends on how you configured it in build-env.sh. One complexity there is that I changed it a lot in the last few days and a couple of times I pushed without remembering to reset the options.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 16 hours 28 minutes ago

Ok, I will try to limit links to 5 or less in a post. Thanks!

Also, do you know why it didn't give me some sort of error message? it also didn't give me one when I entered the wrong password.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 16 hours 58 minutes ago

Oh I see, do you know what that limit is?

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 17 hours 29 minutes ago

For anybody who was waiting for it, the OS X build error in INDI with endian.h was just fixed by the author of the change, so it should be all good now

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 19 hours 39 minutes ago

Right Jerry, the reason I made the repo and script is because it is incredibly hard to get everything all set up and working starting from scratch, a huge uphill battle. So the idea is that I set up the script so that you can run it, all the hard parts of the setup are done for you, and then you can follow the instructions in the repo to setup qt creator to go ahead and use it. That way you can get all setup to make useful contributions to KStars and INDI without having to deal with all the setup crap.

Based on what you posted, if you are trying to follow my instructions in qt creator to get it set up, I expect you didn’t select the build directory where it is already all setup for you.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 20 hours 4 minutes ago

Sorry, that was in 4 parts, but I tried posting it so many times and it didn't work. For some reason, all of it worked when I split it up?????? Not sure.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 20 hours 5 minutes ago
Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 20 hours 6 minutes ago

Part 3:
For building KDE based programs such as KStars on Windows and Mac, because many linux executables and libraries are not available on Mac or Windows, we use the the craft build system. We used to use homebrew for Mac builds of KStars, but while homebrew was really great for the more basic software packages, I found it to be rather unstable for building the more advanced KDE libraries. So a couple of years ago, I spent a lot of time transitioning to the Craft build system since it is designed for the task. So for the main KStars build, we use the craft build system. If you want to find out more about that, there is a lot of documentation here: community.kde.org/Craft . Just note that currently there are a bunch of programs that we need for KStars and INDI that the current craft recipes do not make, and there are a few more that don't make the libraries with the options that we need and I had to change the recipe. So, I did write a whole bunch of recipes for them and keep them in a separate repo. I am hoping that they eventually get integrated into the main craft recipes repo, but for now, they are separate until we can get somebody to look at what I did and work with me on perfecting them. But for now it works. My kstars-on-osx build script makes use of those alternate recipes.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 20 hours 6 minutes ago

Part 2:
If you are referring to Qt documentation for libraries, functions, etc, then I think the best place is here: doc.qt.io . Although I will say that when I have a question about an object or method, such as if I am working with a QLabel and I'm wondering what methods it has, or descriptions of its methods, or examples of using it, I just do a google search. Usually the google search comes back to the QT docs, but not always.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. 20 hours 7 minutes ago

I am not sure why my post is not posting, but I will try to separate it to see if that helps. Part 1:

So, I wouldn't probably call QT a build system as much as I would call it a library of cross platform functions, objects, and methods. The great benefit of QT is that we can do something on one operating system and it will mostly work on another out of the box. This is true of the entire program, from the methods to the system functions to even the user interface. Also, its great because it is free as long as you are doing open source. QT creator is also a very nice IDE, in a number of ways it is better than Xcode.

Read More...

Tom, I think I agree with Jerry, the first issue is probably that your system probably ran out of available memory or something similar. Do you have the zram option enabled and is zram running? How many GB of ram do you have?

For the rpicam issue, when I first saw your post, I suspected that it was a recent change in 3rd party that caused the failure. I thought maybe rpicam had been recently added or recently changed to cause the issue, but I took a look and it hasn't been changed in about 2 months. So I am not sure I understand why it would have the wrong symbols. What system are you using, is it armhf, arm-64 or something else? I would think the best solution would be to submit a bug report to either the author or rpicam or to the 3rd party INDI drivers repo so that whatever issue there is with that driver, it can get fixed.

My script by default builds all 3rd party drivers based on this cmakelists: github.com/indilib/indi-3rdparty/blob/master/CMakeLists.txt . If you want to turn off the building of any particular driver, you can either edit the cmakelists.txt file, or you can change the cmake build command in the script to turn off the driver(s) you don't want.

Read More...

Rob Lancaster replied to the topic 'Kstars 3.5.0 OSx' in the forum. yesterday

So the answer to this is slightly complicated. The sounds in KStars come from a library called Phonon (the VLC based version), which was originally supposed to be a cross platform sound system. But I found it to be incredibly hard to build the vlc backend for it on OSX. A couple of years ago, I managed to get it built after several hours of hard work, but the changes I had to make were in a number of different places in libraries owned by different people. I very carefully saved the binaries, and now in the DMG build I just copy them in from a zip file. The sounds do work just fine in the distributed version of KStars, but not in the development versions. So you might ask, why don't we just copy them in to the app bundle here, wouldn't they work here too? Well yes, it does work, I tried it, but the issue is that the phonon files I am referring to reside in the plugins in the app bundle, but since everyone is using a different version of QT, the plugins on your system might be different, so really we should be using the plugins directory from QT, not an internal plugins directory in the app bundle. There could potentially be issues or conflicts with file versions if we do that. So you might think, well what if we copied it into the plugins folder on the user's system in QT? Well I don't think I should copy files into people's QT directory from my script first, but also, the libraries in the vlc folder and the phonon backend are linked to the libraries in the app bundle. I am not sure they would work in the QT directory. Maybe with a bunch of work they could.

So it's complicated. And from my perspective, I am a volunteer working on a hobby project, this isn't my full time job, and just getting KStars to work on OS X in the first place and then to keep it working and fix all the issues that pop up is difficult enough. And this year I just decided to develop a cross platform plate solving library called StellarSolver. These things do take a lot of time, but they are really interesting and they do make a difference in the world, so I do have to pick my battles. The sound issue is not really at the top of my list. But other folks like yourself helping out would greatly help the cause and allow more of these sorts of issues along with many others to get fixed. That is one really big reason that the KStars-INDI-Mac-Dev Repo has been a priority of mine, so that I can get new folks started and helping out. Because we all benefit from this open source collaboration that we are undertaking here. Last year, I got somebody started coding on KStars and INDI using this repo and he started small and then started working on bigger projects. He is now one of our main contributors, though he did decide to move to coding for KStars on Linux because of the challenges on OS X, but he hasn't stopped, and thats the important part! I am hoping though, to get this repo to a state where it is good enough that people enjoy using it just as much.

Read More...