Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B
C::B and wxWidgets 2.9.5 under Windows
mojca:
Since the thread is about wxWidgets 2.9.5 support: may I please request looking into fixes for Mac as well (even if there is no Mac developer in the team as I was told recently)?
See:
* http://trac.macports.org/browser/trunk/dports/devel/codeblocks/files
* https://trac.macports.org/ticket/40390or some patches/reports on the tracker.
wxWidgets 2.8 cannot be compiled on a recent Mac OS X (other than via wxGTK using X11), so it's particularly important to get the version 2.9 working for a smooth user experience.
stahta01:
--- Quote from: mojca on September 29, 2013, 11:10:08 pm ---wxWidgets 2.8 cannot be compiled on a recent Mac OS X (other than via wxGTK using X11), so it's particularly important to get the version 2.9 working for a smooth user experience.
--- End quote ---
I suggest working on the Building/testing of CB and wxWidgets 2.9/3.0 under Mac OS X.
The CB Team will NOT even think of supporting wxWidgets 2.9 as the primary wxWidgets; so, 3.0 needs to be released.
And, people need to test CB using the yet to be released wxWidgets 3.0.
I foresee wxWidgets being released in October or November of this year (only 1 to 2 months past last posted schedule).
[FYI: The wxWidgets trunk already is using version number 3.0; so, it likely less than two week before trial builds.]
Tim S.
mojca:
Maybe I need to clarify. I successfully built Code::Blocks 12.11 on Mac OS X (10.7) against both wxGTK 2.8.12 and wxOSX 2.9.5. I had to add some patches, but the majority of these patches works with both wxWidgets 2.8 and 2.9/3.0. I would like to request from the Code::Blocks team to review those patches and to apply them to trunk, so that next version of Code::Blocks could be compiled out-of-the-box without additional patches. I assume that wxWidgets 3.0 might be released before the next version of Code::Blocks?
I created most patches myself and only later realized that some of those have already been applied to trunk.
The program now runs, but there are still some minor issues (some pop-up windows with warnings for example), some of which have probably already been fixed in trunk (like in r9362 as mentioned above).
I'm not requesting to make Code::Blocks work with wxWidgets 2.9 only, but to apply the patches that are needed to compile Code::Blocks with version 2.9/3.0.
These are the patches that I needed to compile Code::Blocks 12.11: http://trac.macports.org/browser/trunk/dports/devel/codeblocks/files and there are a bunch of bug reports/patches in the tracker. Some patches might need modifications, but such cases all include additional notes.
stahta01:
--- Quote from: mojca on September 30, 2013, 04:44:07 pm ---Maybe I need to clarify. I successfully built Code::Blocks 12.11 on Mac OS X (10.7) against both wxGTK 2.8.12 and wxOSX 2.9.5. I had to add some patches, but the majority of these patches works with both wxWidgets 2.8 and 2.9/3.0. I would like to request from the Code::Blocks team to review those patches and to apply them to trunk, so that next version of Code::Blocks could be compiled out-of-the-box without additional patches. I assume that wxWidgets 3.0 might be released before the next version of Code::Blocks?
I created most patches myself and only later realized that some of those have already been applied to trunk.
The program now runs, but there are still some minor issues (some pop-up windows with warnings for example), some of which have probably already been fixed in trunk (like in r9362 as mentioned above).
I'm not requesting to make Code::Blocks work with wxWidgets 2.9 only, but to apply the patches that are needed to compile Code::Blocks with version 2.9/3.0.
These are the patches that I needed to compile Code::Blocks 12.11: http://trac.macports.org/browser/trunk/dports/devel/codeblocks/files and there are a bunch of bug reports/patches in the tracker. Some patches might need modifications, but such cases all include additional notes.
--- End quote ---
So, your patches are NOT against either wxWidgets trunk or CB trunk; I know I do NOT have the time to fix the patches.
Tim S.
mojca:
--- Quote from: stahta01 on September 30, 2013, 05:44:11 pm ---So, your patches are NOT against either wxWidgets trunk or CB trunk; I know I do NOT have the time to fix the patches.
--- End quote ---
These patches are not for wxWidgets themselves, they are all for CB. Yes, the patches on the link are meant to be applied against 12.11, but those that haven't been applied already mostly apply without a problem and I have no problem doing minor modifications to them so that they could go straight to trunk (as long as someone plans to commit the changes soon rather than waiting until the patch would become incompatible with trunk again).
I have no problem migrating patches to the trunk, but I need to point out that I'm unable to compile the complete CB from trunk (http://developer.berlios.de/bugs/?func=detailbug&bug_id=19114&group_id=5358) which is why I kept patching the released version first.
What exactly should I do to get the patches applied? Just as an example, here's a report where I can still submit a patch (adding a single include), but it's not likely that doing it would mean any less work anyone involved:
http://developer.berlios.de/bugs/?func=detailbug&bug_id=19113&group_id=5358
I would be grateful if someone would at least replied to the tickets with at least some kind of comment like "this looks ok to me, please create a patch against trunk and I will commit it" or "this doesn't look acceptable to me for this or that reason, we need to find another way to solve the problem", just to make sure that it won't be just hours of extra work for me without any developer actually looking into it later.
Please advise.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version