-
Notifications
You must be signed in to change notification settings - Fork 12
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
Memory access violation #29
Comments
Might be an upstream issue, that should be fixed by now. |
@jbrwn Is there any chance you will release new version any time soon? Current is based on the year-old mapnik-win-sdk-14.0-x64-v3.0.0-rc1-1158-g73dbec3.7z. Many bugs were fixed by now for sure. |
@rouen-sk unfortunately, I have not been working on a new release. I just haven't had the time or motivation. That being said, if you want to keep plugging away at I would more than willing to help out when I can and provide support.
c++ can be cold bitch sometimes. The new version of mapnik sdk likely has a handful (or more) of api changes that are causing things to break. Let me know if you want to keep hacking at it and I can get a branch going, a CI job on appveyor, and/or anything else you need. |
I also would like to help with developing C# bindings of mapnik and maybe use the new .NET Core. PS. I also am not a C/C++ developer, but maybe I can find a friend to help us. |
Yes, most definitely. If the interest is there and folks are willing to contribute then i am game to get the ball rolling.
I agree that this is the best path forward. Unfortunately, this project is currently written in c++/cli which will probably never be compatible with .NET Core - dotnet/coreclr#659. To target .NET Core we would need to re-write everything using p/invoke references to the native mapnik SDK. Even then, there still may be challenges as referencing native libraries from the .NET Core is still a work in progress - aspnet/dnx#402. To be honest, this is biggest reason why i lost motivation with this project last year. I was pretty bummed when i realized what it would take to make the project cross-platform and .NET Core compatible. That being said, .NET Core has matured quite a bit in the last year, and i feel more optimistic about the re-write after taking another look just now. Ok, Here are the potential options/milestones i see for future development:
I am not super excited about option 1 but i do realize it is the probably the quickest way to ship a new release. I would support that kind of effort if someones else takes the lead but i am not very likely to put in a lot of my own dev time. Option 2 is a lot more appealing to me. I could see myself putting in a good amount my own time towards a re-write. What do you guys think? |
Hi, @jbrwn . I also don't have much free dev time to spend, but the NET-Mapnik is something that I will use in future projects. So I am willing to help, as much as I can and even more. Finally, I have no experience p/invoke references for C#, but I am willing to learning all about that. |
Hi guys, nice to see it is not entirely dead here. I am in fact part of the company and we are evaluating NET-Mapnik as a part of our product. So I got a c++ capable colleague working on "option 1". I will let you know as soon as possible. |
When I am debugging my tile server based on NET-Mapnik, it happens quite often that debugger stop on Render() with the following exception. However, after continuing, the tile in fact is generated OK.
The text was updated successfully, but these errors were encountered: