-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Magnum hunter #298
Magnum hunter #298
Conversation
…Lists package/hunter ├── .gitignore # ignore HunterGate.cmake ├── HunterFetchDeps.cmake # Fetch SDL, corrade and glfw ├── HunterGate.cmake # main hunter scripts (ignored in git) └── HunterInit.cmake # entry point
Codecov Report
@@ Coverage Diff @@
## master #298 +/- ##
=======================================
Coverage 52.89% 52.89%
=======================================
Files 323 323
Lines 16583 16583
=======================================
Hits 8771 8771
Misses 7812 7812 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
To save your time, I tried to find answers to my questions by reading Hunter docs. It was overwhelming but I think I got most of the answers from there. I'm still not sure about one thing, see below.
Hi, some updates about hunter CI: Corrade Hunter CIWe will soon have green lights on corrade in the CI
Magnum Hunter CII rebased all my code onto your last commits
|
Re the Re Ubuntu 14 vs 16: it's about this, right? https://travis-ci.org/pthom/hunter/jobs/462782227#L1290 I'll be switching to Ubuntu 16 soon anyway, so unless this is a critical issue for Hunter, I'm not sure we should bother too much with it. |
I think too !
Exactly, the error message is strange, given that the corrade code seems to do what is appropriate
I hope the maintainer of hunter will bare with me for I changed from travis to xenial. Having a package like magnum is probably worth it ! |
I just pushed mosra/corrade@c09a22e which is hopefully a better workaround for the EDIT: it's on |
Hum, it would be too long with travis. If I use ubuntu 14.04 diff --git a/Docker/ubuntu/Dockerfile b/Docker/ubuntu/Dockerfile
index abc754c..eecd979 100644
--- a/Docker/ubuntu/Dockerfile
+++ b/Docker/ubuntu/Dockerfile
@@ -1,7 +1,7 @@
-FROM ubuntu:16.04
+FROM ubuntu:14.04 And then inside the docker container I try to build corrade I have the error: > ./TLDR_hunter.py test-build corrade gcc-7-cxx14
/sources_docker/corrade/src/Corrade/Utility/FileWatcher.cpp:59:14: error: function ‘Corrade::Utility::FileWatcher& Corrade::Utility::FileWatcher::operator=(Corrade::Utility::FileWatcher&&)’ defaulted on its redeclaration with an exception-specification that differs from the implicit exception-specification ‘’
FileWatcher& FileWatcher::operator=(FileWatcher&&) then I fetch your modif
And inside the container, it works ! > ./TLDR_hunter.py test-build corrade gcc-7-cxx14
SUCCESS What is your opinion: do you prefer that I reverse the travis builds to travis ? |
Awesome! :) It's on master now. |
Here is my checklist in order to finish this. What do you think of it? I will need your input concerning the releases url and sha1 :-) Corrade hunter package / v2018.10 => DONE: see ruslo/hunter#1646
Corrade hunter package / v2018.12
Magnum hunter package
Magnum (optional steps)
|
Not really sure what this means, sorry 😅
I'm planning to have a 2018.12 release, but that will happen later this month (around Dec 30th I think) as I still have quite a few important features I want to finish before tagging another version. Would it be possible to use a temporary tag on your fork in the meantime? Once 2018.12 is out, I can switch the packages to the "upstream" tag.
Yes, definitely. I can do that once Magnum is available in Hunter, I also wanted to play with it a bit to get a feeling how it's used. For the rest of the |
I need to discuss this directly with Ruslan Baratov (maintainer of hunter)
There is no hurry.
Not on my fork. If we want to publish a release before the 2018.12 release, I would need to place my fork inside https://github.com/hunter-packages/ (which I did not).
Of course, this is the good way to go. |
One question that is abolutely not related.
Did I miss a setting? It does work on windows, though. |
No, you didn't. it's a known bug in macOS 10.14. Shake the window, minimize/maximize it or click into it to make the contents appear. Related info for SDL is here: https://discourse.libsdl.org/t/macos-10-14-mojave-issues/25060 (so far I'm not aware of a new version fixing this :/ ...), more info (and some workarounds) here in a GLFW issue: glfw/glfw#1334 |
This is the funniest workaround I have heard off :-) It does not work on my side because I cannot resize the example app window. It is not important at all, though: I can work on linux / windows. |
Yes, it's quite annoying. Not related to Magnum at all, but rather to how the underlying toolkits (SDL/GLFW) manage the GL context. I hope the fixed versions of SDL / GLFW get released soon. For the release tag: so is it okay to have the release delayed until I get 2018.12 out? I really don't want to be blocking you from getting your work done :) Oh, but Corrade (2018.10) could get packaged as-is already so we can tick at least some boxes, right? Then, once that's done, the hunter URL here could get updated to an upstream version of Hunter that contains Corrade and then this PR could get merged without any TODOs left. Is that a reasonable path forward? |
Ok, let's try to tick some boxes for corrade : Here is the first PR out of two : ingenue/hunter#300 |
Hi, This version should pass, as it disables the hack for corrade-rc. For the future release of corrade on hunter, we have two options :
Do you have a preference? |
@pthom thank you! I would leave it as-is, for now. With other cross-compilation packages I'm usually adding a dependency to native Corrade installation (so e.g. ArchLinux |
Target version of package depends on host build of same package. So there is a dependency.
Yes, it can be, see comments: |
@ruslo right, thanks, sorry that you had to repeat everything again 😅 Yes, now I think I know how this could be done (as a next step after the native packages are done). Since I still had some problems with e.g. |
corrade is merged into hunter ! |
Great! I'll reference it in the building documentation. Is there anything I should mention besides "Corrade is available in Hunter" and linking to https://docs.hunter.sh/en/latest/packages/pkg/corrade.html ? Can you update the Hunter release URL here? I'll merge this PR right after. |
I think just link should be enough, user have to read basic Hunter documentation anyway. By the way you can add it as a badge: https://docs.hunter.sh/en/latest/creating-new/create/cmake.html#badge |
Yay, badge! Of course :) Done in mosra/corrade@a4c4fe6, updated docs here. |
@mosra : thanks for the update! Please do contact me when you release the version, I'll try to help! |
Hi,
As discussed, here is the PR for the hunter related modifications.
Cheers