-
Notifications
You must be signed in to change notification settings - Fork 45
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
Upgrade libtcod to 1.12.3 #290
Conversation
Thanks! And sorry for the conflicts! Updating The CI issues are real. I've rebased this and got to the same issues. The Linux verison is using ANSI C, but this relies on C++ 14. We need to replace this line with Line 65 in 718d8d9
(and similar in build_linux_dynamic, mingw and darwin) That got me to build From the PR message, I'm not sure whether that's where you are (i.e. you're using |
Seems straightforward enough. I'll do it once I pick this up again, I'd guess in a couple of days.
Oops, I'm starting to suspect I'd need to update the root-level |
I think I'm seeing the same issue when I do update the version to |
I've just added
Let's see what CI thinks. If it's sad, I'll then try to reproduce on a proper Linux system. Meanwhile, if it's easy for you to reproduce, it might be good to have a full build output with the errors from your env. |
Huh, rebased to |
Bah, never mind, just messed up the conflict resolution of |
Meh, Travis fails because ... it seems to not know about C++14? I'm having trouble fully believing that, but then https://github.com/libtcod/libtcod/blob/master/.travis.yml is also doing some magic around selecting the compiler. I'm out of time to spend on tracking that down for today, help is appreciated; I will be coming back to this, but no promises on the timeline. On Appveyor I'm seeing one success so far, second build is in progress, so it's starting to smell like a Win / Linux env difference. |
Alright, so all this work got us a working What we learned:
|
We have a goodnews-badnews situation. Good news: I managed to reproduce the issue locally, and found some leads to fixing it. Bad news: I couldn't fix it. Halp! Details! I was almost right: the failure is due to not linking against However! It seems that linking against C++ libraries is not very easy in Rust today. The conversation at https://users.rust-lang.org/t/linking-against-c-dependencies/25099/4 is trying to solve a very similar problem. I've tried So at this point I think the problem is well identified, and I've showed a few "solutions" that don't work; I'm escalating to you all, hopefully at this point someone will go "right, you just need to X". |
Current maintainer of libtcod here. The latest versions of libtcod had their C++ dependencies removed and can now be compiled without any C++ sources. You'll only need C99 support from the tool-chain. |
Closing this in favor of #309 - there's more progress there, some great simplifications, and it also targets a newer |
Things to note:
libtcod
has changed between releases.idea
stuff, sorry about thatlibtcod
, or even FFI definitions