binary release still not compiled for 10.11+ #191
Comments
|
Hello, do You think it is possible to backport current horos (3.0 beta) to 10.11? |
|
I don't think there's a need to backport any code. You only have to make the changes in the project I described in #171 (comment) |
|
Thanks for your advice guys.
This will reviewed before the final release of version 3.0.
We get in touch soon again.
Thanks
Fauze
… On 15 Feb 2018, at 02:55, Helmut K. C. Tessarek ***@***.***> wrote:
I don't think there's a need to backport any code. You only have to make the changes in the project I described in #171 (comment) <#171 (comment)>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#191 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgtbRYTgOytfG4V7vWIi7RHvyrwDzznks5tU7jdgaJpZM4On6wZ>.
|
|
@boskar when I pulled the latest code, I saw that the deployment target was actually set to 10.11. Thus, the version which is available for download should run on 10.11, unless the release team compiled a version which is not the same as the code on github. However, I also compiled a version (not tested though) and put it here: @fvpolpeta after the reorganization of the source tree and project, there are 2 compile errors, because paths are not set correctly by the scripts and Xcode. |
|
Thanks for your feedback. We will be writing building instructions when we conclude the release of version 3.0.
Some pieces are recent and we are still accommodating them. In advance, if you feel comfortable on consolidating the README.md with build instructions and make a pull request, we will be very pleased to accept it and incrementally improve it. That’s the spirit of open source.
Regarding the 10.11 version, we will be investigating that as mentioned. Perhaps, it’s something related to the signing process/archiving of XCode. We will see.
Thanks again.
Fauze
… On 15 Feb 2018, at 15:54, Helmut K. C. Tessarek ***@***.***> wrote:
@boskar <https://github.com/boskar> when I pulled the latest code, I saw that the deployment target was actually set to 10.11.
Thus, the version which is available for download should run on 10.11, unless the release team compiled a version which is not the same as the code on github.
However, I also compiled a version (not tested though) and put it here:
https://evermeet.cx/pub/macosx/Horos/Horos-3.0.0.rc1.zip <https://evermeet.cx/pub/macosx/Horos/Horos-3.0.0.rc1.zip>
@fvpolpeta <https://github.com/fvpolpeta> after the reorganization of the source tree and project, there are 2 compile errors, because paths are not set correctly by the scripts and Xcode. cmake and pkg-config cannot be found. Xcode does not use the user's environment PATH. cmake and pkg-config are not part of macOS, thus they are either in /opt/local/bin (macports) or some other directory for homebrew. In any case, I had to create a symbolic link in /bin for those 2 binaries.
Maybe you should use the README.md file to describe how to compile the project. Especially since the project does not compile out of the box. (also a lot of people don't know how to use git submodules)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#191 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgtbb4xKUj8k6lCRQ8U9UV_oBIuXy_Mks5tVG8_gaJpZM4On6wZ>.
|
Yep, sounds good. Will do. Not sure when I will be able to get around to it though, maybe this weekend.
I'm not sure what you mean by that. You've changed the deployment target already, so there's nothing else you have to do. If you compile the current master, it will run on 10.11 and later. |
|
We haven’t changed the target to anything different than 10.11.
Since we do generate and sign the App via Archive, I will investigate if that may be imposing some change. Not sure.
I will let you know. As said, the idea is to have this resolved before we make the 3.0 the official release.
Cheers
… On 15 Feb 2018, at 16:10, Helmut K. C. Tessarek ***@***.***> wrote:
@fvpolpeta <https://github.com/fvpolpeta>
README.md with build instructions and make a pull request, we will be very pleased to accept it and incrementally improve it.
Yep, sounds good. Will do. Not sure when I will be able to get around to it though, maybe this weekend.
Regarding the 10.11 version, we will be investigating that as mentioned. Perhaps, it’s something related to the signing process/archiving of XCode. We will see.
I'm not sure what you mean by that. You've changed the deployment target already, so there's nothing else you have to do. If you compile the current master, it will run on 10.11 and later.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#191 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKA_jmB3Yz-UWW-s-VuhNP4xZcPspD3Mks5tVHMGgaJpZM4On6wZ>.
|
|
When I opened this issue, the minimum deployment target in the project was 10.12. Now it is not. So you must have changed it from 10.12 to 10.11. ;-) |
|
Oh yeah. It was changed time ago based on the issue you reported. But there are still users complaining about this (not 10.11 compliant).
I will be reviewing all targets and dependencies (and the signing process).
Your help is appreciated.
Thanks
… On 15 Feb 2018, at 16:21, Helmut K. C. Tessarek ***@***.***> wrote:
When I opened this issue, the minimum deployment target in the project was 10.12.
Now it is not. So you must have changed it from 10.12 to 10.11. ;-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#191 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgtbTYdE1xo5qXb3uEHRsZFA1Q7bSqxks5tVHWvgaJpZM4On6wZ>.
|
|
Ah, I didn't know that people still had an issue with 10.11. It compiles perfectly (there are a few deprecation warnings for NSForm), but other than that this project has no warnings - which is remarkable btw. I've already upgraded to High Sierra, but I still have a backup of my 10.11 on an external disk, which I can boot up at any time. You can always add me to a ticket by mentioning me. e.g.: /cc @tessus |
|
@tessus sorry, I didn’t explain myself properly. The issue I mean is the fact I have been building for 10.11 but the binary version built and signed requires recent versions of macOS.
…Sent from my iPhone
On 15 Feb 2018, at 16:38, Helmut K. C. Tessarek ***@***.***> wrote:
Ah, I didn't know that people still had an issue with 10.11. It compiles perfectly (there are a few deprecation warnings for NSForm), but other than that this project has no warnings - which is remarkable btw.
I've already upgraded to High Sierra, but I still have a backup of my 10.11 on an external disk, which I can boot up at any time.
(I compile other stuff for 10.9 and above, so that's not really an issue.)
You can always add me to a ticket by mentioning me. e.g.: /cc @tessus
In this case I can follow the 10.11 issues...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Hmm, this makes no sense. If you build for 10.11 it has to run on 10.11, otehrwise there's a bug in Xcode. Signing should be OS version agnostic. Very strange, I hope you can figure out what the problem is. |
please see #273 |
I've just noticed that the binary release is still only available for 10.12, which makes really no sense.
You only have to make the changes I've mentioned in #171 (comment)
In any case, I've created a binary for 10.11+ for anyone who needs it:
https://evermeet.cx/pub/macosx/Horos/Horos-2.2.0.zip
The text was updated successfully, but these errors were encountered: