Patch #1569 2006-10-18 16:12

takeshimiya

wxWidgets wx-config support in Windows
Download
1569-wxWidgets_wx_c.patch (1.5 KB)
Category
Platform-Specific
Status
Open
Close date
 
Assigned to
 
PATCH HERE: http://wxconfig.googlepages.com/add_wxconfig_support3.zip

From a PM to Yiannis, UPDATED here:

Hi! After long time, and long testing I think my wx-config windows port is ready for usage.

Here you will find: http://wxconfig.googlepages.com/add_wxconfig_support.zip
 - Patches for the current wxWidgets wizard, adding a "wx-config" mode when in Windows. I hope to remove it when everyone will be already using it.
 - New logos for the wizard, don't need to apply if you don't like.
 - wx-config.exe, the only thing really needed.
 - Patch for C::B plugin wizard (cbpluginwizard.patch and codeblocks.pc), not ready for the prime-time due to some C::B missing features (on linux also).
 - Patches for the wxSmith wizard, adding a selectable wx-config mode.


For the source, it is only a single cpp, and it's here: http://wx-config-win.googlecode.com/svn/trunk/

I've put a nice webpage containing the usage documentation here: http://wxconfig.googlepages.com/

May I ask if we can:
 - Apply the patch for the wizard.
 - Put wx-config-win.cpp in trunk. byo suggested to put it in /src/tools.
 - Once you feel comfortable enough, I can adjust the C::B unix.cbp projects to use build scripts. This will mean that only one set of projects will have to be mantained finally :)

wx-config has been tested extensively with MinGW, DMC, VC makefiles and C::B projects, by at least me, eranif, and tiwag, which has given a lot of feedback.
It is being used in MinGW makefiles and C::B projects in the CodeLite project without any major problems.

Regards,
Takeshi Miya
takeshimiya 2006-10-18 16:12

PATCH HERE: http://wxconfig.googlepages.com/add_wxconfig_support3.zip

From a PM to Yiannis, UPDATED here:

Hi! After long time, and long testing I think my wx-config windows port is ready for usage.

Here you will find: http://wxconfig.googlepages.com/add_wxconfig_support.zip

- Patches for the current wxWidgets wizard, adding a "wx-config" mode when in Windows. I hope to remove it when everyone will be already using it.

- New logos for the wizard, don't need to apply if you don't like.

- wx-config.exe, the only thing really needed.

- Patch for C::B plugin wizard (cbpluginwizard.patch and codeblocks.pc), not ready for the prime-time due to some C::B missing features (on linux also).

- Patches for the wxSmith wizard, adding a selectable wx-config mode.

For the source, it is only a single cpp, and it's here: http://wx-config-win.googlecode.com/svn/trunk/

I've put a nice webpage containing the usage documentation here: http://wxconfig.googlepages.com/

May I ask if we can:

- Apply the patch for the wizard.

- Put wx-config-win.cpp in trunk. byo suggested to put it in /src/tools.

- Once you feel comfortable enough, I can adjust the C::B unix.cbp projects to use build scripts. This will mean that only one set of projects will have to be mantained finally :)

wx-config has been tested extensively with MinGW, DMC, VC makefiles and C::B projects, by at least me, eranif, and tiwag, which has given a lot of feedback.

It is being used in MinGW makefiles and C::B projects in the CodeLite project without any major problems.

Regards,

Takeshi Miya

mortenmacfly 2006-10-18 17:29

Not offending, but what makes me suspicious: This patch also changes the wizard(s) in a way not related to the wx-config support, e.g. the following lines:

+ else if (GetCompilerFactory().CompilerInheritsFrom(compilerID, _T("dmc*")))

+ {

+ base.AddCompilerOption(_T("-W3"));

+ }

You should really document what this patch does alltogether. There is no problem with adding more features but they should be documented.

takeshimiya 2006-10-18 17:43

Not offending also, but I think the only changes not related to the wx-config support are the changes in common_functions.script and the wizard' logos.

I don't think any documentation is needed since it's pretty self explaining what it does??

Anyways, this is what it does in common_functions.script in order:

- Fixes warning flags for Digital Mars.

- Fixes optimization flags for Digital Mars.

- Fixes exception flags for Digital Mars.

I don't think that's adding more features, but fixing current ones. I could make a separate patch, but please, let's get the thing forward.