When we have questions, would there be a good way to contact you? We have tried using the KDE-Windows discussion group and that has not always been successful. We have also emailed folks like Hannah Von Reth in the past, but she was not an expert in MacOS.
Ok this sounds very good. We can start looking into it and try to clean things up over the next couple of months. We can definitely use your changes here as a guide and a starting point to revisions and see what else can be improved. Thank you for your help.
Hi there Julius,
Thank you very much for looking into things and providing feedback. This looks like a lot of changes to the build scripts. I worked on getting KStars to build on MacOS a few years ago and it took me many months to get it all working. When I did all this work there were a number of problems in craft with the build including packages that seemed to install, but they were linked improperly due to rpath issues so that later in the build issues would crop up and things would not work. There were issues with packages that did not work for MacOS and I had to make custom recipes to get them to install properly with the features we needed. I had to write a number of custom scripts to get everything to work due to all kinds of issues. I know that it is certainly true that there probably are better ways to do things than what I did in many places, but it was sometimes a challenge to get help with the work I was trying to do and I did what seemed to work relying heavily on already existing examples. I am sure that in the last couple of years craft has come a long way and many things I had to add may no longer be required. As an example, one particularly difficult thing was getting dbus to work properly for KStars on MacOS. I had gotten it working after a decent amount of work. More recently, some work was done in craft that would make it work in a similar way to what I had done, so I was able to remove the custom code I had needed and could just rely on craft to do it at that point. So yes, the build probably needs to be revised to find more things like this and simplify the scripts and recipes. Unfortunately I have been rather busy recently since I am working on a Master's degree and I have been very busy with work too, so I have not had much time to work on KStars or INDI. In a couple of months this situation should improve and I should be able to work on it again, probably in a month or two. But in the meantime, we do need to make sure to have a working build of KStars for MacOS users.
Before anything gets merged, I think we need to make sure these changes allow a working KStars to be built. We already had a couple of problems which really hurt users in the last few months. The binary server, which was providing daily builds of the latest KStars and INDI code to Mac users, was disconnected. Then more recently there was an issue with either QT or craft where there is an incompatibility with some binary craft files that were built for macOS Sonoma that are definitely not compatible with older MacOS versions. So right now the DMG I posted the other day does not work for anyone running anything other than the latest MacOS. If we merge in more changes that may break the KStars build then neither I nor anyone else will be able to build a working KStars for MacOS users until they get fixed. Right now, my craft recipes and build scripts are really the only way for either developers or users to get it running.
I do really appreciate you taking the time to look into things and trying to improve it. I also would like to see if we can get daily builds running again with the new system. But right now I do not even have time to test your changes and verify that it still works. What is the timeline for which you would want to merge these changes? If I can have a few weeks to look into it, then that could work.
Thanks,
Rob
Robert Lancaster (3d9d377b) at 26 Jan 04:33
Robert Lancaster (3d9d377b) at 26 Jan 04:29
Fixing craft issue with os
Robert Lancaster (e281283b) at 26 Jan 04:27
Disable libavif dependency for Android builds
... and 780 more commits
Robert Lancaster (a8574a9e) at 18 Aug 05:30
Robert Lancaster (a8574a9e) at 18 Aug 03:54
stellarsolver2.5
Robert Lancaster (d9967869) at 18 Aug 03:51
[kdewebkit] not available on mac arm since qtwebkit isn't
... and 397 more commits
I think I probably mentioned this to you Jasem a couple of years ago, but I don't remember if I did, so I would not blame you if you forgot.
Yes, this is correct. When I was testing all the different options and comparing them two years ago (or so), this is one of the ones I set up. I personally found it to be much better than uploading an image file because then you are not uploading large amounts of info and using data. But, really that was not the bottleneck that slows down the online solver. The main thing that slows it down is waiting for the online solver to get to your job in the queue.
I did all the work on the recipes for building KStars and INDI on craft almost 5 years ago now. At the time, I had a bunch of issues with libraries getting the rpath wrong and linking improperly. I don't know if you recall those issues, but it took awhile to get it all working. At the time, I believe this was part of how I had resolved it and I just had put this in each recipe that I had made to make sure it worked. It is possible that Craft has resolved the issues that I was correcting with that code and that now it can be removed. I should test it thoroughly first, however.
Ok no problem. If you think this is a better way to do it, then I have no problem with that. This was an argument that I had added to many of my MacOS recipes with the intent to get the rpaths properly set.
Robert Lancaster (4dae07d9) at 02 Mar 02:13
Improving argument setting
Robert Lancaster (cfec9db2) at 25 Feb 18:34
Robert Lancaster (de030a0a) at 25 Feb 16:56
Adding LibXisf
Robert Lancaster (d55917d8) at 25 Feb 16:35
Revert frei0r to before commit causing crash in frei0r curves effetc
... and 11 more commits