User forums > General (but related to Code::Blocks)
Building CB - bleeding edge - gcc49 wxW30
digifuzzy:
--- Quote from: stahta01 on May 04, 2014, 02:09:10 am ---
--- Quote from: digifuzzy on May 03, 2014, 11:45:03 pm ---It seems that trunk is the wxW_3_0_0 branch at the moment.
--- End quote ---
I just am very surprised that CB does NOT require wx 2.8 compatible mode to be on; I have NOT seen that many wxWidgets 3.0 patches submitted to fix all the places in CB that assumed wx 2.8 compatible mode.
Edit: But, its been about 5 months since I last tried wx trunk; I stopped about one month after the 3.0 branch started.
Edit2: I am using WX_3_0_BRANCH and it is still wxWidgets 3.0.1.0 in wx/version.h.
Tim S.
--- End quote ---
So is this something that needs attention? Find wx28/wx26 code in CB and update?
If a patch were submitted, how much effort to maintain reverse-compatibility?
Would there be a need to have #if/#else preprocessor statement to check wx version?
stahta01:
--- Quote from: digifuzzy on May 04, 2014, 08:46:41 am ---So is this something that needs attention? Find wx28/wx26 code in CB and update?
If a patch were submitted, how much effort to maintain reverse-compatibility?
Would there be a need to have #if/#else preprocessor statement to check wx version?
--- End quote ---
To find the places is NOT that much effort; but, to fix the places requires research and testing.
And, it would require #if/#else preprocessor statement to check wx version in most places.
But, Jens seems to think that the fixes has been done.
The first thing to do is to build wxWidgets 3.0.0.0 without 2.8 compatible mode (IIRC, it defaults to being enabled).
Then, build CB against that; this would verify the issues are fixed or NOT in CB.
Tim S.
digifuzzy:
--- Quote from: stahta01 on May 04, 2014, 03:00:21 pm ---The first thing to do is to build wxWidgets 3.0.0.0 without 2.8 compatible mode (IIRC, it defaults to being enabled).
Then, build CB against that; this would verify the issues are fixed or NOT in CB.
--- End quote ---
Strange, I didn't enable wx28 compatibility. Configure returned the info below (snipped)
--- Code: ---Configured wxWidgets 3.1.0 for `x86_64-unknown-linux-gnu'
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.8 no
wxWidgets 3.0 yes
--- End code ---
Okay...having already seen a couple of deprecated messages in the build. I think I know where to start.
Thanks, TIm.
stahta01:
--- Quote from: digifuzzy on May 04, 2014, 04:48:46 pm ---
--- Quote from: stahta01 on May 04, 2014, 03:00:21 pm ---The first thing to do is to build wxWidgets 3.0.0.0 without 2.8 compatible mode (IIRC, it defaults to being enabled).
Then, build CB against that; this would verify the issues are fixed or NOT in CB.
--- End quote ---
Strange, I didn't enable wx28 compatibility. Configure returned the info below (snipped)
--- Code: ---Configured wxWidgets 3.1.0 for `x86_64-unknown-linux-gnu'
What level of wxWidgets compatibility should be enabled?
wxWidgets 2.8 no
wxWidgets 3.0 yes
--- End code ---
Okay...having already seen a couple of deprecated messages in the build. I think I know where to start.
Thanks, TIm.
--- End quote ---
Can you NOT tell the difference between 3.1 and 3.0?
Edit: Do realize that 3.1 is a development build while 3.0 is a production build?
For this reason, it is NOT likely the CB team will accept patches for 3.1 at this time.
While patches for wx 3.0 without compatibility for 2.8 will likely be accepted.
Edit2: From wx/setup_inc.h WX_3_0_BRANCH svn 76442
Edit3: Never edit wx/setup_inc.h unless you are making or testing a patch to submit to the wxWidgets dev team!
--- Code: ---// This setting determines the compatibility with 2.8 API: set it to 0 to
// flag all cases of using deprecated functions.
//
// Default is 1 but please try building your code with 0 as the default will
// change to 0 in the next version and the deprecated functions will disappear
// in the version after it completely.
//
// Recommended setting: 0 (please update your code)
#define WXWIN_COMPATIBILITY_2_8 1
--- End code ---
Tim S.
stahta01:
I am building CodeBlocks linking against wxWidgets 3.0 branch without 2.8 compat mode.
It appears to be working without any error.
So, I think Jens is completely right and there are no remaining 2.8 wx compat mode issues for the core CB project.
Edit: I am doing a second rebuild and then will test the exe under windows 7 32 bit.
Tim S.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version