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

wxWidgets 3.0 and Code::Blocks files question?

(1/5) > >>

stahta01:
I have a question about wxWidgets 3.0 and Code::Blocks files.

Are we going to create CodeBlocks_wx30.cbp CB project; when wxWidgets 3.0 are released?

Are we going to remove the *_wx29.cbp project files or rename them to *_wx30.cbp at that time?

I am currently using modified *_wx29.cbp project files to build against wxWidgets 3.0 in wxWidgets trunk.

Do you want the patches to change the *_wx29.cbp project files or instead ones adding *_wx30.cbp project files?

Tim S.

oBFusCATed:
I'd vote for patches to modify the wx29 files. There is no need to clutter the tree with another set of files.

ouch:
Agreed, 2.9 was never an official version anyway.

Jenna:
On windows we already need to set the global wx-variable, why not use it to provide the version-number as well ?
We could provide two sets of project-files one for stable wx (or better for fully supported wx) and one for development wx (or if wx30 is official stable for not fully supported wx). We would need two wx-variables: e.g. wx and wx-dev or similar). At the moment we already have wx and wx29.

On linux it would make sense to have a similar  set of global variables, at the moment I use patched wx29 project-files to make use of my own build of wx-trunk.

With global variables there would be one place to change and not many project-files (with different custom variables, as we have now).

stahta01:

--- Quote from: jens on October 07, 2013, 10:23:52 pm ---On windows we already need to set the global wx-variable, why not use it to provide the version-number as well ?
We could provide two sets of project-files one for stable wx (or better for fully supported wx) and one for development wx (or if wx30 is official stable for not fully supported wx). We would need two wx-variables: e.g. wx and wx-dev or similar). At the moment we already have wx and wx29.

On linux it would make sense to have a similar  set of global variables, at the moment I use patched wx29 project-files to make use of my own build of wx-trunk.

With global variables there would be one place to change and not many project-files (with different custom variables, as we have now).

--- End quote ---

This sounds like a good third choice to me. I have decided to create a patch that updates the wx29 project-files to use a Global Var called wx_dev.
I plan to do only the 32-bit windows wx29 project-files and the update29.bat files.

Tim S.

Navigation

[0] Message Index

[#] Next page