Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Plug-in Issues

<< < (2/3) > >>

Avan:
Excerpt from my monitor:


--- Code: ---                        Code::Blocks is built with the GNU GCC compiler and links to
                        the monolithic unicode wxWidgets DLL.
                        This means that you must have exactly this setup to be able to
                        build the generated plugin.
                        You must also have defined two global variables:

--- End code ---


Hi Miguel,

The wizzard on my 12292 shows no further than the colon. Like I quoted it above. You got your exerpt from source code but that's not how it ends up.

Also, I find the concept of a 'base dir' rather confusing. As do others, I think I once read a convoluted recipe that made me set ../sdk as the base dir.

Any toughts on the warning I mentioned in my initial post?

(You beat me to it by minutes ;o)

Miguel Gimenez:
When you say
--- Quote ---When I open the virgin plug-in in C::B
--- End quote ---
are you referring to opening the created source code in the editor or loading the compiled plugin in C::B?

EDIT: what kind of plugin are you generating (generic/tool/MIME handler/wizard) and which options?

Avan:

--- Quote from: Miguel Gimenez on February 17, 2021, 11:50:24 am ---When you say
--- Quote ---When I open the virgin plug-in in C::B
--- End quote ---
are you referring to opening the created source code in the editor or loading the compiled plugin in C::B?

EDIT: what kind of plugin are you generating (generic/tool/MIME handler/wizard) and which options?

--- End quote ---

The created source code, as that is the wizard's default action after Finish.

- Tool
- No configuation dialog
- wxWidgets 3.1.x
- GNU GCC Compiler

Now I press Finish and the wxWidgets Debug Alert follows immediately (stdvararg.h(451)) and I have to click Ok 9 times to get the plugin loaded.

Miguel Gimenez:
Can't reproduce here, but I am using wx3.1.4 (32 bits, with default debug level 1). From About -> Information:


--- Code: ---Name             : Code::Blocks
Version          : svn-r12293
SDK Version      : 2.6.0
Scintilla Version: 3.7.5
Author           : The Code::Blocks Team
E-mail           : [email protected]
Website          : http://www.codeblocks.org

wxWidgets Library (wxMSW port)
Version 3.1.4 (Unicode: wchar_t, debug level: 1),
compiled at Jul 23 2020 11:26:42

Runtime version of toolkit used is 6.1.

--- End code ---

EDIT: looks like C::B code uses %d to print a long. In 32 bits int and long have the same length, but not in 64 bits, hence the assertion. Can you get a stack trace?

Avan:

--- Code: ---                        "   1. $(#cb) pointing to Code::Blocks base dir (where CodeBlocks.cbp is)\n" +
                        "   2. $(#wx) pointing to wxWidgets base directory\n\n\n");


--- End code ---

I have set cb pointing to the folder trunk\src where codeblocks.cbp resides.
I have set wx, wx31 and wx31_64 pointing to \wxWidgets.

Now I create a clean Tool Plugin with a name I never used before and move to Project | Build Options | Search Directories (the plugin does not compile as is).

Search Directories | Compiler | default shows:
$(#wx31.include)
$(#wx31.lib)\gcc_dll\mswu

Search Directories | Linker | default shows:
$(#wx31.lib)\gcc_dll
$(#cb)\devel30

I change the latter to $(#cb)\devel31_64 and it builds.

The only thing realy wrong here seems the "$(#cb)\devel30" string as I have installed wx31_64.

The other issues here vanished when I had all wx-variables point to the same folder. I had figured wrongly that 'wx' was the generic variable which was going to make our lives easier when new wxWidgeds come along. I'll have to change all projects Build Options each time that happens. Bummer!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version