Code::Blocks

Developer forums (C::B DEVELOPMENT STRICTLY!) => Plugins development => Topic started by: Pecan on October 26, 2005, 11:47:20 pm

Title: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 26, 2005, 11:47:20 pm
C::B RC2,
wxWidgets MSW2.6.1
WinXPsp2

Has anyone had experience compiling the Code::Blocks Plugin Wizard
under RC2 using MSW2.6.1??

The dialog comes up, but all the text is blank and C::B is
hung (hanged??). I have to kill it with windows task manager.

I've put a trap in all the PluginWizarddlg.cpp routines; only
OnUpdateUI is being called.

Any advice would be appreciated.
Thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 27, 2005, 07:23:13 pm
I've traced the problem down to a loop when

       if (dlg.ShowModal() != wxID_OK)
            return -1;

is called in Execute();

GDB loses control at that point and never returns. However,
under GDB, the whole dialog window WITH its text show up.
But C::B, "the wiz", and GDB are hanged.

BTW, is there a way to make GDB regain control from
within a loop??

Am going to generate a BUILD=debug DLL this afternoon and see
if I can drill down any further.

Anyone else seen this problem??

Thanks, Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 27, 2005, 08:06:15 pm
Ok, another step backward,

when I link a plugin (any plugin) with libwxmsw26d.a (BUILD=debug version)
the plugin does not show up in the plugin menu.

It also disappears from the "Configure Plugins" dialog.

Is there something I can do about this??

thanks, Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Urxae on October 27, 2005, 08:44:47 pm
when I link a plugin (any plugin) with libwxmsw26d.a (BUILD=debug version)
the plugin does not show up in the plugin menu.

It also disappears from the "Configure Plugins" dialog.

Is there something I can do about this??

Did you recompile Code::Blocks with the same debug wxWidgets DLL? If not, doing so will likely solve your problem.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 27, 2005, 11:56:46 pm
Thanks Urxae,
I failed to recompile C::B.
I get it, I'll persue debug-compiling C::B tomorrow.

Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 28, 2005, 12:04:21 am
Further inspection.. C::B is *not* in a loop after the
dlg.ShowModal() call. My cpu meter is at 0 (zip, nada).

I now notice that the tab key will move to the first
text entry area of the dialog window, but it will take
no character input.

Building ClassWizard behaves exactly the same as
PluginWizard. Dlg shows, but after {tab} or {enter} all
keys are ignored.

{Enter} will dismiss the dialog, but C::B is still hung.
I have to tskill it.

So.. seems plugins are ignoring me again.

I went back to 2.4.2 and compiled PluginWizard there.
It works fine.

All this has something to do with something not passing key
input to the dlgs.

Is anyone else having any success building the plugins
under wxMSW261 ??

Thanks,
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: rickg22 on October 28, 2005, 12:57:15 am
I usually build the entire sourcecode and plugins.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 28, 2005, 02:41:26 am
Finally, success!

But to get the compiled 2.6.1 PlugInWizard to run, C::B had to be
compiled as well.

But why? If the distributed C::B was built with wxWidgets 2.6.1
and the plugin is compiled with wxWidgets 2.6.1 and linked with ONLY 2.6.1,
why won't the plugin work??

This means that a user HAS to download and compile C::B in
order to contribute/compile a plugin. And, there is no assurance that a plugin
built on my system with wxMSW2.6.1 will work on anyone elses
wxMSW2.6.1

What am I misunderstanding here?

Very confused
Thanks for the help and patience
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: rickg22 on October 28, 2005, 03:41:09 am
Perhaps the wxWidgets DLL you bulit was compiled with a different version of GCC.

There's a current discussion regarding the distribution of wxwidgets libs along with the SDK.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 28, 2005, 10:09:25 am
Perhaps the wxWidgets DLL you bulit was compiled with a different version of GCC.

There's a current discussion regarding the distribution of wxwidgets libs along with the SDK.

Maybe people have missed it (even Rick?), but the SDK download contains libwxmsw26.a that is the import library for the wxmsw26_gcc_cb.dll that is installed with C::B. To build a plugin you should use this import library...
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 28, 2005, 03:35:39 pm
Thanks rickg22 & mandrav

I started from scratch last night by wiping C::B off my system.
I re-downloaded C::Brc2 with _mingw and installed it.
I then re-installed the rc2-sdk

I created a new plugin project.
I copied pluginwizard from the src.tgz file to a folder, included pluginwizard files
into the project and deleted the fake h&cpp created by the wizard.

I then removed all directory references in the project options and reinserted them
as callled for by re-building the project on each err. I made sure that the codeblocks folder and sdk had preference over any wxWidget261 reference.

When linking, I specifically only allowed reference to the DLL's in the codeblocks folder. It linked.

I then copied the DLL to the ...\codeblocks\plugins folder.

It still hangs. The dlg shows, and you can use the tab or enter key once only.
Then its time to kill codeblocks. No other action is possible.

What gives. Have I mis-stepped somewhere??

Thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: rickg22 on October 28, 2005, 03:41:09 pm
Maybe people have missed it (even Rick?), but the SDK download contains libwxmsw26.a

Ah, sorry. I didn't download the SDK, so I assummed that since the user didn't had it there... :lol:
I guess I need to be more suspicious of users from now on.  :mrgreen:
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 28, 2005, 08:43:07 pm
Linking with the *.a files in the SDK does not work either.

Another wierdness is, the size of the pluginwizard.dll in the
distribution is 339,456 bytes. While the one I link with either
\codeblocks\*.dll or \codeblocks\SDK\lib\*.a is only 191,515 bytes.

Is there a clue there?

I'd really like to figure this one out. If a user cannot compile the
plugins, it means only developers can create them. Secondly, there
is no way that a developer can be assured her/his work will run
with anyone elses C::B.

thanks
Pecan
 
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 28, 2005, 09:20:29 pm
@Pecan: can you post your test project somewhere?
I 'm sure you must be doing something wrong because I 've tried to build a new plugin in a clean environment and worked like a charm.

Test environment:

Win98 (yes I know ;), I just want to test compatibility)
C::B 1.0rc2 (with MinGW)
C::B SDK
wxWidgets-2.6.1 just unpacked, not even built (only the headers are actually needed).
Nothing else. Just a pristine Win98 setup.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Zlika on October 28, 2005, 10:02:58 pm
I have the same problem than Pecan to build my own plugins!
I linked them with the libs contain in the SDK, it compiles OK but crashes C::B when used!
I had not at all this pb with wx2.4.2. If someone please could help me, I want to make some minor changes in the Profiler plugin but I can't test it anymore!  :cry:

Zlika
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: rickg22 on October 28, 2005, 10:29:18 pm
I recall wxWidgets 2.6.1 needing a patch...
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 28, 2005, 11:38:50 pm
Mandrav, thanks for the reply

A *new* test project generated by the wizard works fine.
That's not the problem. The problem is re-compiling the
wizards, such as the pluginwizard, distributed from source
with RC2+SDK. It crashes C::B. No problem with RC1.1

If you mean that you want to see the compiler/linker settings
used to compile the wizards, I'll cut and paste 'em to
this forum shortly.  I have to feed the dog first.

thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 29, 2005, 12:14:46 am
Quote
The problem is re-compiling the
wizards, such as the pluginwizard, distributed from source
with RC2+SDK. It crashes C::B. No problem with RC1.1

In that case, check the flags (mainly #defines) used in codeblocks*.cbp for PluginWizard. The PluginWizard-generated wizards *don't* have the same flags, IIRC.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 12:44:32 am
Thanks mandrav

Here are the settings used by the project to re-compile the pluginwizard
(same for ClassWizard). I used absolute paths in an attempt to get
control of the problem (and to simplify).

Code: [Select]
[Project PluginWizard]
  sources
    enterinfodlg.cpp
    pluginwizard.cpp
    pluginwizarddlg.cp
  Headers
    enterinfodlg.h
    pluginwizard.h
    pluginwizarddlg.h

[Selected Compiler
  GNU GCC Compiler

[Compiler]
  Policy: blank
  Compiler Flags
    Enable all compiler warnings(overrides...)
  Other options
    blank
  #defines
    __GNUWIN32__
    WXUSINGDLL
    BUILDING_PLUGIN
[Linker]
  Link libraries:
    C:\Usr\CodeBlocks\codeblocks.dll
    C:\Usr\CodeBlocks\wxscintilla.dll
    C:\Usr\CodeBlocks\exchndl.dll
    C:\Usr\CodeBlocks\wxmsw26_gcc_cb.dll
[Directories]
  Compiler
    C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\include
    C:\Usr\codeblocks\codeblocks-1.0rc2-sdk\include\wxscintilla\include
    C:\Usr\Proj\wxWidgets261\include           <--wx/wxprec.h
    C:\Usr\Proj\wxWidgets261\lib\gcc_dll\msw   <--wx/setup.h
  Linker
    blank
  Resource Compiler
    blank
Commands
  blank
Custom variables
  blank

Thanks, Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 01:02:40 am
Ok, I cut this out of codeblocks.cbp from the rc2 src file.
Note that it was linked with 2.4.2. Is this what we should do?
I'm willing, I'm able. I'll do it if that's what it takes. BUT....


Code: [Select]
</Target>
<Target title="plugin_PluginsWizard">
<Option output="devel\share\CodeBlocks\plugins\pluginwizard.dll"/>
<Option working_dir="."/>
<Option object_output=".objs"/>
<Option deps_output=".deps"/>
<Option external_deps=""/>
<Option type="3"/>
<Option compiler="0"/>
<Option projectLinkerOptionsRelation="1"/>
<Option projectIncludeDirsRelation="2"/>
<Option projectLibDirsRelation="2"/>
<Compiler>
<Add option="-DBUILDING_PLUGIN"/>
<Add option="-D_WINDLL"/>
<Add directory="sdk"/>
</Compiler>
<Linker>
<Add option="-Wl,--enable-auto-image-base"/>
<Add option="-Wl,--add-stdcall-alias"/>
<Add library="libcodeblocks.a"/>
<Add library="libwxscintilla.a"/>
<Add library="libwxxrc.a"/>
<Add library="wxmsw242"/>
<Add directory="devel"/>
</Linker>
</Target>

thanks, Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 01:11:48 am
wups, or is this the right one ???
Code: [Select]
</Target>
<Target title="plugin_PluginsWizard">
<Option output="devel\share\CodeBlocks\plugins\pluginwizard.dll"/>
<Option working_dir="devel\share\CodeBlocks\plugins"/>
<Option object_output=".objs\2.6"/>
<Option deps_output=".deps"/>
<Option type="3"/>
<Option compiler="0"/>
<Option projectLinkerOptionsRelation="1"/>
<Option projectIncludeDirsRelation="2"/>
<Option projectLibDirsRelation="2"/>
<Compiler>
<Add option="-DBUILDING_PLUGIN"/>
<Add directory="sdk"/>
</Compiler>
<Linker>
<Add option="-Wl,--enable-auto-image-base"/>
<Add option="-Wl,--add-stdcall-alias"/>
<Add library="libcodeblocks.a"/>
<Add library="libwxscintilla.a"/>
<Add library="C:\Usr\Proj\wxWidgets261\lib\gcc_dll\wxmsw26_gcc_cb.dll"/>
<Add directory="devel"/>
</Linker>
</Target>


Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 29, 2005, 01:15:23 am
Code: [Select]
[Linker]
  Link libraries:
    C:\Usr\CodeBlocks\codeblocks.dll
    C:\Usr\CodeBlocks\wxscintilla.dll
    C:\Usr\CodeBlocks\exchndl.dll
    C:\Usr\CodeBlocks\wxmsw26_gcc_cb.dll

WHAT'S THIS?
You 're linking the DLLs directly?  :shock: :?
Remove those and link the following:

Code: [Select]
libcodeblocks.a
libwxscintilla.a
libwxmsw26.a
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 01:48:33 am
Thanks mandrav

Here is my attempt to translate the src codeblocks.cbp to re-compiling
pluginwizard as a project:
Code: [Select]
?xml version="1.0"?>
<!DOCTYPE CodeBlocks_project_file>
<CodeBlocks_project_file>
<FileVersion major="1" minor="1"/>
<Project>
<Option title="PluginWizard"/>
<Option makefile="Makefile"/>
<Option makefile_is_custom="0"/>
<Option compiler="0"/>
<Build>
<Target title="default">
<Option output="pluginwizard.dll"/>
<Option working_dir="."/>
<Option object_output=".objs"/>
<Option deps_output=".deps"/>
<Option type="3"/>
<Option compiler="0"/>
</Target>
</Build>
<Compiler>
<Add option="-Wall"/>
<Add option="-D__GNUWIN32__"/>
<Add option="-DBUILDING_PLUGIN"/>
<Add directory="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\include"/>
<Add directory="c:\Usr\codeblocks\codeblocks-1.0rc2-sdk\include\wxscintilla\include"/>
<Add directory="C:\Usr\Proj\wxWidgets261\include"/>
<Add directory="C:\Usr\Proj\wxWidgets261\lib\gcc_dll\msw"/>
</Compiler>
<Linker>
<Add option="-Wl,--enable-auto-image-base"/>
<Add option="-Wl,--add-stdcall-alias"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libcodeblocks.a"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libwxscintilla.a"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libwxmsw26.a"/>
</Linker>
<Unit filename="enterinfodlg.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="enterinfodlg.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizard.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizard.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizarddlg.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizarddlg.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
</Project>
</CodeBlocks_project_file>


These are the err I get:
Code: [Select]
roject   : PluginWizard
Compiler  : GNU GCC Compiler (called directly)
Directory : C:\Usr\Proj\plugnwiz\
--------------------------------------------------------------------------------
Switching to target: default
Compiling: pluginwizard.cpp
Compiling: pluginwizarddlg.cpp
Compiling: enterinfodlg.cpp
Linking dynamic library: pluginwizard.dll
Info: resolving _wxEmptyString by linking to __imp__wxEmptyString (auto-import)
Info: resolving wxStringBase::npos       by linking to __imp___ZN12wxStringBase4nposE (auto-import)
Info: resolving _wxDefaultPosition by linking to __imp__wxDefaultPosition (auto-import)
Info: resolving vtable for wxMessageDialogby linking to __imp___ZTV15wxMessageDialog (auto-import)
Info: resolving wxDialog::sm_eventTable       by linking to __imp___ZN8wxDialog13sm_eventTableE (auto-import)
Info: resolving vtable for wxDialogby linking to __imp___ZTV8wxDialog (auto-import)
Info: resolving vtable for wxDialogBaseby linking to __imp___ZTV12wxDialogBase (auto-import)
Info: resolving vtable for wxTopLevelWindowby linking to __imp___ZTV16wxTopLevelWindow (auto-import)
Info: resolving vtable for wxTopLevelWindowMSWby linking to __imp___ZTV19wxTopLevelWindowMSW (auto-import)
Info: resolving _wxEVT_UPDATE_UI by linking to __imp__wxEVT_UPDATE_UI (auto-import)
Info: resolving _wxEVT_COMMAND_BUTTON_CLICKED by linking to __imp__wxEVT_COMMAND_BUTTON_CLICKED (auto-import)
Info: resolving _wxEVT_COMMAND_TEXT_UPDATED by linking to __imp__wxEVT_COMMAND_TEXT_UPDATED (auto-import)
Info: resolving _wxEVT_NULL by linking to __imp__wxEVT_NULL (auto-import)
.objs\pluginwizard.o:pluginwizard.cpp:(.text$_ZN15wxMessageDialogD1Ev[wxMessageDialog::~wxMessageDialog()]+0xb): variable 'vtable for wxMessageDialog' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN8wxDialogC2Ev[wxDialog::wxDialog()]+0x4c): variable 'vtable for wxDialog' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN12wxDialogBaseD2Ev[wxDialogBase::~wxDialogBase()]+0xb): variable 'vtable for wxDialogBase' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN12wxDialogBaseC2Ev[wxDialogBase::wxDialogBase()]+0x4c): variable 'vtable for wxDialogBase' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN16wxTopLevelWindowD2Ev[wxTopLevelWindow::~wxTopLevelWindow()]+0xb): variable 'vtable for wxTopLevelWindow' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN16wxTopLevelWindowC2Ev[wxTopLevelWindow::wxTopLevelWindow()]+0x4c): variable 'vtable for wxTopLevelWindow' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
.objs\pluginwizarddlg.o:pluginwizarddlg.cpp:(.text$_ZN19wxTopLevelWindowMSWC2Ev[wxTopLevelWindowMSW::wxTopLevelWindowMSW()]+0x4c): variable 'vtable for wxTopLevelWindowMSW' can't be auto-imported. Please read the documentation for ld's --enable-auto-import for details.
collect2: ld returned 1 exit status
Process terminated with status 1 (0 minutes, 11 seconds)
0 errors, 0 warnings
 


I smell "nearly" success again, after 4 days. An' that's pretty smelly  :D

thanks, Pecan

Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 29, 2005, 09:59:33 am
Where's WXUSINGDLL?
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Zlika on October 29, 2005, 10:33:55 am
rickg22, which patch do you speak about?  :oops:
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 03:34:07 pm
mandrav

Thanks for the suggestion
I put WXUSINGDLL into the #defines. Pluginwizard compiled and
linked ok. But it still hangs C::B. the size of the dll is 191,515 bytes if
thats any importance. Here is the latest .cbp
Code: [Select]
<?xml version="1.0"?>
<!DOCTYPE CodeBlocks_project_file>
<CodeBlocks_project_file>
<FileVersion major="1" minor="1"/>
<Project>
<Option title="PluginWizard"/>
<Option makefile="Makefile"/>
<Option makefile_is_custom="0"/>
<Option compiler="0"/>
<Build>
<Target title="default">
<Option output="pluginwizard.dll"/>
<Option working_dir="."/>
<Option object_output=".objs"/>
<Option deps_output=".deps"/>
<Option type="3"/>
<Option compiler="0"/>
</Target>
</Build>
<Compiler>
<Add option="-Wall"/>
<Add option="-D__GNUWIN32__"/>
<Add option="-DBUILDING_PLUGIN"/>
<Add option="-DWXUSINGDLL"/>
<Add directory="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\include"/>
<Add directory="c:\Usr\codeblocks\codeblocks-1.0rc2-sdk\include\wxscintilla\include"/>
<Add directory="C:\Usr\Proj\wxWidgets261\include"/>
<Add directory="C:\Usr\Proj\wxWidgets261\lib\gcc_dll\msw"/>
</Compiler>
<Linker>
<Add option="-Wl,--enable-auto-image-base"/>
<Add option="-Wl,--add-stdcall-alias"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libcodeblocks.a"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libwxscintilla.a"/>
<Add library="C:\Usr\CodeBlocks\codeblocks-1.0rc2-sdk\lib\libwxmsw26.a"/>
</Linker>
<Unit filename="enterinfodlg.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="enterinfodlg.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizard.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizard.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizarddlg.cpp">
<Option compilerVar="CPP"/>
<Option target="default"/>
</Unit>
<Unit filename="pluginwizarddlg.h">
<Option compilerVar=""/>
<Option compile="0"/>
<Option link="0"/>
<Option target="default"/>
</Unit>
</Project>
</CodeBlocks_project_file>

thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 03:45:44 pm
Zlika,
I found this at www.wxwindows.org/patch/htm
But I dont know that it has anything to do with
the problem.
If applied, I think you'd have to re-compile C::B. That
would fix the problem alright. But it doesnt solve the
current hang with the distributed C::B.
You can re-compile C::B now (without the patch) and the
problem goes away too.
BUT... it does not guarentee that any plugin you write under
the re-compiled C::B will work for anyone else who is using
the distributed C::B RC2 package.

Pecan

Patches for 2.6.1

Various wxMSW fixes

    This patch fixes the following problems on Windows:

        * Crash on exit when destroying wxCHMHelpController in wxApp::OnExit.
        * wxListBox, wxCheckListBox scrolling glitch when Windows effects are enabled.
        * Wrong area sometimes being refreshed after a window is resized.
        * Notebook refreshing the wrong area when resized.
        * Problem for non-VC++ compilers where some toolbar tooltips cause a crash.
        * An eVC++ 3 compile error.

    Please download wxWidgets-2.6.1-Patch01.zip and unarchive from the top level of your wxWidgets tree.
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: mandrav on October 29, 2005, 04:17:01 pm
Pecan,

we have a two pages long topic here for you trying to build the pluginwizard outside c::b. May I know what this is for?!?
You already said tha plugins generated by the wizard work ok for you...
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 05:35:29 pm
mandrav

I am not building pluginwizard outside C::B. I'm trying
to re-compile it *inside* C::B.

The purpose? I think the best way to learn is to read the
experts code. The C::B plugins use both the facilities of
C::B code and the wxWidgets code. What better way to
learn.

I wanted to learn to  modify the pluginwizard to generate
.cbp's that point to the locations/folders on my system.
I wanted to use GDB on pluginwizard to walk the code.
I wanted to learn and contribute.

So.. I tried to compile the pluginwizard. And that's when
it all started....

thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: killerbot on October 29, 2005, 05:51:18 pm
I am having alike problems, freezing CB, also by 'trying' to rebuild an existing plug-in (see my post about class wizard in Plugins devlopment section), I did not try this with RC1.1, only with RC2. I wonder if the problems might be related.

Lieven
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 06:03:19 pm
killerbot

I did go back to RC1-1 and re-compiled the plugins within
C::B using pluginwizard to generate the .cbp's. They compiled
and ran just fine.

thanks
Pecan
Title: Re: Building Code::Blocks Plugin Wizard w/MSW
Post by: Pecan on October 29, 2005, 11:35:33 pm
Resolution:

I applied the patches for wxWidgets 2.6.1 Now all is working well.
I also re-compiled PluginWizard and ClassWizard, and they
all work fine with the patches.

wxWidgets Patches
Patches for 2.6.1. Various wxMSW fixes. This patch fixes the following problems
... Please download wxWidgets-2.6.1-Patch01.zip and unarchive from the top ...
www.wxwindows.org/patch.htm - 6k - Cached - Similar pages

ftp://biolpc22.york.ac.uk/pub/2.6.1/wxWidgets-2.6.1-Patch01.zip

I noticed that some of the headers (window.h etc) are used
all over the place.

Thanks
Pecan