Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Patches to compile and link C::B against wxWidgets 2.8.0

<< < (9/25) > >>

stahta01:

--- Quote from: SharkCZ on December 15, 2006, 11:10:59 pm ---Is it possible to build current C::B with wxWidgets 2.8, any patches required? Fedora Extras Development moved to WX 2.8 today, so I would like to be able to rebuild C::B with it in the near future.

--- End quote ---

Just the ones mentioned in the first message in this thread, note none of these have been tested under Linux, but some were tested under Mac by afb. These patches need testing, so if you have problems reply in this thread on it. And, I will look into it.

Tim S

SharkCZ:
I have looked at the first page and there are only patches for C::B, no patching of wxGTK is required. That´s good.

David Perfors:
But without the patches, codeblocks will not compile, that's no good...

stahta01:

--- Quote from: mispunt on December 16, 2006, 10:59:08 pm ---But without the patches, codeblocks will not compile, that's no good...

--- End quote ---

Correct, the patches are to get codeblocks to compile and link against wxWidgets 2.8. It runs and compiles itself, I can't say it does more than that. I have fixed the issues I found except for the fact it gives about 75 to 110 warnings.

Tim S

killerbot:
Hello all you wx 2.7.x and 2.8.x folks.

I am going to apply patches (one at a time) to get it to build for wx, only if they meet the following conditions (if those are acceptable conditions) :
1) all wx 2.7.x patches should be considered not existing [2.7.x are development series, not official release series]
 -> so please adjust all your patches for 2.8 and remove all references to 2.7.x, I'd prefer not to look at any 2.7 patch at berlios and like to close it without looking at it. I'd prefer not tp spend time on them and then in the end find out that a little thing might have changed in the official 2.8
2) as a result of 1), I'd like to see all ifdef constructs referring to 2.7.x removed, I think we should not ifdef polute our code on unofficial versions, and certainly not versions we won't support, don't take this as an insult, I am very thankful for all the hard work, but in the end all that research will pay back in the "official 2.8 patches" ;-)
3) all patches should describe what they are doing :
 a) how comes it does not work without the patch (so what did 2.8 break) [== the why]
 b) a little explanation how wx 2.8 now does it
 c) whatever information you can give to make our life easier to understand and apply the patches without doing the research ourself from scratch

4) OPEN QUESTION : I guess most linux distros are now already somewhere in the 2.6.x line [x can still be 1 or 2 or 3 !!!], can we kick out 2.4.x specific things ?

5) unfortunately we can't use anything yet of the new functionalities of wx 2.8 since probably it will take 6 months to 1 year until the major linux distros come with a newer version [some example : I think they have new about boxes or so ...]


Let me stress one thing : many many thanks to all of you who already sorted things out on what happened with wx ;-) , now it's just a little documentation step and cleaning.

Navigation

[0] Message Index

[#] Next page

[*] Previous page