-
Notifications
You must be signed in to change notification settings - Fork 84
Update plan? #51
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
Comments
Thanks for the report. Branch We could create patched-8 based on the latest release, do you have time to do so ? |
I just made a pull request (#52) consisting of just the bare patches from r445 to r455 (r444 seemed to have already been included), which could be the basis of a new patched-8 branch. The patches all applied cleanly but unfortunately there's still a lot of work to do to make it compile on my system. That's not the fault of the new patches though - I can't compile the new default patched-7 branch either. Since the new upstream release (which includes up to r455) builds OK here, I guess the problem lies with the cmake stuff which I'm not really conversant with. Hopefully someone more knowledgeable can work on that. |
I resolved the build problems I had with patched-7 and the proposed patched-8 - there were two things to fix:
I notice that upstream's latest release 3.2 has no generated files for any qt4 version i.e. no support for qt4. Not having to deal with both qt45 and qt5 could simplify CMakeLists.txt somewhat (but that's a bigger job for someone who understands cmake a bit better than I do). |
Looks like (from README) latest code is based on r403 at sourceforge repo. I see they have just released a version 3.2 which seems to include up to r455.
Is there any plan to update code here to include the other sourceforge commits (r404 - r455)?
The text was updated successfully, but these errors were encountered: