Code::Blocks

User forums => Using Code::Blocks => Topic started by: jjenson on February 09, 2019, 10:36:54 pm

Title: wxsmith plugin, where is it?
Post by: jjenson on February 09, 2019, 10:36:54 pm
Hi,

I'm running Peppermint 9 Linux. I have built codeblocks 17.12 from source I downloaded from sourceforge and successfully installed it on my system and have been using it ever since without issue. Lately, I have become interested in wxwidgets, but when I create a new project, there is no form wizard. If I select the radio button for wxsmith and hit the "next" button, I get "wxsmith plugin not loaded, cannot continue". What gives? Shouldn't wxsmith be included in the source or is there some other download I have to get?

Thanks,
JJ
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 09, 2019, 11:33:08 pm
You have to enable it at configure time see --help or the --with-contrib-plugins option.

Generally the best option is to just build packages. Your distro is debian based, so it should be relatively easy.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 10, 2019, 04:24:31 pm
You have to enable it at configure time see --help or the --with-contrib-plugins option.

Generally the best option is to just build packages. Your distro is debian based, so it should be relatively easy.

Okay, I tried again using ./configure --with-contrib-plugins switch. A lot of checking takes place followed by the following error:

configure: error: Package requirements (hunspell) were not met

No package 'hunspell' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables HUNSPELL_CFLAGS
and HUNSPELL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 12:22:55 am
You have to enable it at configure time see --help or the --with-contrib-plugins option.

Generally the best option is to just build packages. Your distro is debian based, so it should be relatively easy.

Okay, I tried again using ./configure --with-contrib-plugins switch. A lot of checking takes place followed by the following error:

configure: error: Package requirements (hunspell) were not met

No package 'hunspell' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables HUNSPELL_CFLAGS
and HUNSPELL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

IS anyone going to answer this?
Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 11, 2019, 01:16:07 am
Quote
No package 'hunspell' found

Install the hunspell development package
Title: Re: wxsmith plugin, where is it?
Post by: ollydbg on February 11, 2019, 02:39:24 am
This post (http://forums.codeblocks.org/index.php/topic,22439.msg154685.html#msg154685) may help you.
Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 11, 2019, 02:56:09 am
This post http://forums.codeblocks.org/index.php/topic,23096.0.html (http://forums.codeblocks.org/index.php/topic,23096.0.html) is more likely to help you than ollydbg post.

Tim S.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 03:59:58 pm
I built and installed hunspell and did the configure again.

It complained that I needed gamin.

I installed gamin

did the config again

it completed successfully. I ran make and i get the following:

collect2: error: ld returned 1 exit status
Makefile:838: recipe for target 'libcodeblocks.la' failed
make[3]: *** [libcodeblocks.la] Error 1
make[3]: Leaving directory '/home/JJ/Downloads/codeblocks-17.12/src/sdk'
Makefile:998: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/JJ/Downloads/codeblocks-17.12/src/sdk'
Makefile:527: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/JJ/Downloads/codeblocks-17.12/src'
Makefile:660: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1


What now?
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 11, 2019, 06:38:07 pm
...
What now?
Post the actual error message. The part of the error you've posted is not enough.

Also I guess you've ignored my post, so I have to repeat it:

Generally the best option is to just build packages. Your distro is debian based, so it should be relatively easy.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 07:22:37 pm

Post the actual error message. The part of the error you've posted is not enough.

Also I guess you've ignored my post, so I have to repeat it:

Generally the best option is to just build packages. Your distro is debian based, so it should be relatively easy.

Oh, but I didn't ignore your post.

I've been building everything I could.

I built the hunspell package. The gamin package I didn't have to build; I just installed it.

After that it configured nicely, but then when I went to make it, I got what you just saw.

The dump is too big for me to post here; it's even too big to put in an attachment (217kb).

What is this error supposed to look like? I did a grep for "err" ignoring case and all I got was what I posted. There are a lot of undefined references; as if it just can't find something.

Some of them are "undefined reference to" wxTrap(), wxTranslations(), wxBaseArrayInt(), wxCommandEvent(), etc.
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 11, 2019, 07:39:03 pm
Oh, but I didn't ignore your post.

I've been building everything I could.
I see. You have not understood it.

Here is a link you could use: https://www.debian.org/doc/manuals/maint-guide/build.en.html

But I'm not sure you'll be able to clean up your messed up system...
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 08:40:50 pm

But I'm not sure you'll be able to clean up your messed up system...

How is my system messed up?

When I do a dpkg-buildpackage -us -uc I get the following:

dpkg-buildpackage: info: source package codeblocks
dpkg-buildpackage: info: source version 17.12
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Jens Lody <jens@odeblocks.org>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build codeblocks-17.12
dpkg-checkbuilddeps: error: Unmet build dependencies: cdbs libbz2-dev libhunspell-dev
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 11, 2019, 09:06:10 pm
http://lmgtfy.com/?q=dpkg-checkbuilddeps%3A+error%3A+Unmet+build+dependencies%3A
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 10:40:31 pm
I used mk-build-deps debian/control

it generated ./codeblocks-build-deps_17.12_all.deb

This package is supposed to install all dependencies. So I installed it.

After that I ran: sudo dpkg-buildpackage -us -uc

it rolled for over 12 minutes and settled in with the errors:

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libwx_gtk2u_core-3.1.so.2 (used by debian/codeblocks/usr/bin/cb_share_config)
Hint: check if the library actually comes from a package.
dh_shlibdeps: dpkg-shlibdeps -Tdebian/codeblocks.substvars debian/codeblocks/usr/lib/codeblocks/plugins/libdefaultmimehandler.so debian/codeblocks/usr/lib/codeblocks/plugins/libabbreviations.so debian/codeblocks/usr/lib/codeblocks/plugins/libopenfileslist.so debian/codeblocks/usr/lib/codeblocks/plugins/libautosave.so debian/codeblocks/usr/lib/codeblocks/plugins/liboccurrenceshighlighting.so debian/codeblocks/usr/lib/codeblocks/plugins/libcodecompletion.so debian/codeblocks/usr/lib/codeblocks/plugins/libtodo.so debian/codeblocks/usr/lib/codeblocks/plugins/libprojectsimporter.so debian/codeblocks/usr/lib/codeblocks/plugins/libscriptedwizard.so debian/codeblocks/usr/lib/codeblocks/plugins/libclasswizard.so debian/codeblocks/usr/lib/codeblocks/plugins/libdebugger.so debian/codeblocks/usr/lib/codeblocks/plugins/libAstyle.so debian/codeblocks/usr/lib/codeblocks/plugins/libcompiler.so debian/codeblocks/usr/bin/cb_share_config debian/codeblocks/usr/bin/cb_console_runner debian/codeblocks/usr/bin/codeblocks returned exit code 255
dh_shlibdeps: Aborting due to earlier error
/usr/share/cdbs/1/rules/debhelper.mk:335: recipe for target 'binary-predeb-IMPL/codeblocks' failed
make: *** [binary-predeb-IMPL/codeblocks] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

I'm not sure what to make of this.  Can you help?
Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 11, 2019, 10:49:52 pm
You need to uninstall the manually installed libraries this build method complains about.

This is what I had to do when I tried this method about 2 to 4 years, ago.

Tim S.
Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 11, 2019, 10:52:30 pm
Is there a real reason you do not wish to try the pre-build Ubuntu binaries?

Tim S.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 10:56:13 pm
You need to uninstall the manually installed libraries this build method complains about.

This is what I had to do when I tried this method about 2 to 4 years, ago.

Tim S.

I would if I knew how.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 11:03:06 pm
Is there a real reason you do not wish to try the pre-build Ubuntu binaries?

Tim S.

They never work for me.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 11:19:19 pm
To recap, I'm now able to do

sudo ./configure --with-contrib-plugins=all

everything configures fine.

then I do a:

sudo make

and it completes without any errors.

then I do a:

sudo make install

runs until I get the following:

libtool: install: error: cannot install `libAstyle.la' to a directory not ending in /usr/lib/codeblocks/plugins

What does that even mean? I looked in that directory and didn't see a libAstyle.la. I looked in the directory I'm building from and it exists. I even tried copying into that directory and tried again and still get that same error. WTF?
Title: Re: wxsmith plugin, where is it?
Post by: sodev on February 11, 2019, 11:36:03 pm
Not sure if this is the cause of the error, but do not run configure and make as root! Only the final make install must be run as root.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 11, 2019, 11:50:03 pm
if I run configure without sudo I get:

./configure: line 2442: config.log: Permission denied
./configure: line 2452: config.log: Permission denied


Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 11, 2019, 11:53:13 pm
if I run configure without sudo I get:

./configure: line 2442: config.log: Permission denied
./configure: line 2452: config.log: Permission denied

That is because you ran it as root in the past; you should run make uninstall as root to try to undo some of the damage.
Then, delete the folder and start over.

Edit: If using SVN you can just delete all the files except for the svn folder and then as a normal user run svn update to restore the files.

Tim S.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 12:00:17 am
if I run configure without sudo I get:

./configure: line 2442: config.log: Permission denied
./configure: line 2452: config.log: Permission denied

That is because you ran it as root in the past; you should run make uninstall as root to try to undo some of the damage.
Then, delete the folder and start over.

Edit: If using SVN you can just delete all the files except for the svn folder and then as a normal user run svn update to restore the files.

Tim S.

Okay, I did sudo make uninstall, deleted the folder and started again. Seems to be running so far.

I was able to do the config without sudo and I am in the middle of compiling.

I have a decades of experience in programming ASM. C and C++, but I have less than a years experience using linux; so bear with me. I just dumped Windows about six months back and have been running Peppermint 9 ever since.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 12:57:15 am
Okay, I was able to completely compile and install with no errors. Apparently, me using sudo had caused much of the problems.

However, when I started codeblocks, I got a message that popped up with the following:

One or more plugins were not loaded

This usually happens when a plugin is built for a different version of code::blocks SDK

Check the application log for more info.

List of failed plugins:

libwsmithcontribitems.so
libwxsmith.so
libwxSmithAui.so


Of course they don't tell you where this application log is stored, so I couldn't get more info.

I tried to start a project using wxsmith and like before I got the same message "wxsmith not loaded, cannot continue."

What do I do now?
Title: Re: wxsmith plugin, where is it?
Post by: ollydbg on February 12, 2019, 01:02:14 am
@jjenson
Can you show all the log message or code/command in the code tag?
like below:
Code: [Select]
code/command/log message put in code tag
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 01:09:32 am
@jjenson
Can you show all the log message or code/command in the code tag?
like below:
Code: [Select]
code/command/log message put in code tag

Pardon my ignorance as I'm not exactly sure what you mean. If I start codeblocks from the commandline, I get the following:

~/Downloads $ codeblocks
Starting Code::Blocks Release 17.12  rev 11256 Feb 11 2019, 18:14:39 - wx3.1.2 (Linux, unicode) - 64 bit
Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading menubar...
Valgrind: loaded
cbDragScroll: loaded
lib_finder: loaded
EditorTweaks: loaded
FilesExtensionHandler: loaded
Abbreviations: loaded
EditorConfig: loaded
RegExTestbed: loaded
Profiler: loaded
AutoVersioning: loaded
OpenFilesList: loaded
EnvVars: loaded
Autosave: loaded
HexEditor: loaded
IncrementalSearch: loaded
OccurrencesHighlighting: loaded
BrowseTracker: loaded
Cscope: loaded
BYOGames: loaded
ToolsPlus: loaded
CodeCompletion: loaded
SpellChecker: loaded
ToDoList: loaded
Cccc: loaded
MouseSap: loaded
CppCheck: loaded
ReopenEditor: loaded
ProjectsImporter: loaded
ScriptedWizard: loaded
SmartIndentHDL: loaded
DoxyBlocks: loaded
ClassWizard: loaded
CodeStat: loaded
FileManager: loaded
HelpPlugin: loaded
SmartIndentPython: loaded
HeaderFixup: loaded
ThreadSearch: loaded
SmartIndentCpp: loaded
SmartIndentLua: loaded
ProjectOptionsManipulator: loaded
SmartIndentXML: loaded
SmartIndentFortran: loaded
CB_Koders: loaded
Debugger: loaded
NassiShneidermanPlugin: loaded
AStylePlugin: loaded
CodeSnippets: loaded
copystrings: loaded
SmartIndentPascal: loaded
Compiler: loaded
Exporter: loaded
SymTab: loaded
cbKeyBinder: loaded
Valgrind plugin activated
DragScroll plugin activated
Library finder plugin activated
Editor Tweaks plugin: Building menu
Editor Tweaks plugin: making the menu 15
Editor Tweaks plugin: Folding menu
EditorTweaks plugin activated
Files extension handler plugin activated
Abbreviations plugin activated
EditorConfig plugin for Code::Blocks plugin activated
Regular expressions testbed plugin activated
Code profiler plugin activated
AutoVersioning plugin activated
Open files list plugin activated
Environment variables plugin activated
Autosave plugin activated
HexEditor plugin activated
IncrementalSearch plugin activated
OccurrencesHighlighting plugin activated
BrowseTracker plugin activated
Cscope plugin activated
BYO Games plugin activated
ToolsPlus plugin activated
Detected dict path: /usr/share/hunspell
Detected thes path: /usr/share/myspell/dicts
Found dictionary: es_ES
Found dictionary: es_PY
Found dictionary: en_AU
Found dictionary: de_DE
Found dictionary: en_GB
Found dictionary: es_EC
Found dictionary: it_IT
Found dictionary: en_ZA
Found dictionary: es_CU
Found dictionary: es_PE
Found dictionary: fr_CA
Found dictionary: es_CL
Found dictionary: es_CO
Found dictionary: es_GT
Found dictionary: it_CH
Found dictionary: es_CR
Found dictionary: de_DE_frami
Found dictionary: es_SV
Found dictionary: es_HN
Found dictionary: es_US
Found dictionary: de_AT_frami
Found dictionary: ru_RU
Found dictionary: es_PR
Selected dictionary: en_US
Found dictionary: en_US
Found dictionary: fr_CH
Found dictionary: de_CH_frami
Found dictionary: fr_BE
Found dictionary: es_NI
Found dictionary: pt_PT
Found dictionary: es_VE
Found dictionary: de_CH
Found dictionary: fr_FR
Found dictionary: es_BO
Found dictionary: es_AR
Found dictionary: de_AT
Found dictionary: es_PA
Found dictionary: es_DO
Found dictionary: fr_LU
Found dictionary: es_UY
Found dictionary: pt_BR
Found dictionary: fr
Found dictionary: es_MX
Found dictionary: fr_MC
Found dictionary: en_CA
Detected bitmap path: /usr/local/share/codeblocks/SpellChecker
Detected bitmap path: /usr/local/share/codeblocks/SpellChecker
SpellChecker plugin activated
Todo List plugin activated
Cccc plugin activated
MouseSap plugin activated
CppCheck plugin activated
ReopenEditor plugin activated
Foreign projects importer plugin activated
Project wizard added for 'Empty project'
Project wizard added for 'Fortran application'
Project wizard added for 'Fortran library'
Project wizard added for 'Fortran DLL'
Project wizard added for 'Console application'
Project wizard added for 'D application'
Project wizard added for 'FLTK project'
Project wizard added for 'GLFW project'
Project wizard added for 'GLUT project'
Project wizard added for 'GTK+ project'
Project wizard added for 'Irrlicht project'
Project wizard added for 'Java application'
Project wizard added for 'Lightfeather project'
Project wizard added for 'Matlab project'
Project wizard added for 'OpenCV project'
Project wizard added for 'OpenGL project'
Project wizard added for 'Ogre project'
Project wizard added for 'Code::Blocks plugin'
Project wizard added for 'QT4 project'
Project wizard added for 'QT4 (shared) project'
Project wizard added for 'QT5 project'
Project wizard added for 'SDL project'
Project wizard added for 'SDL2 project'
Project wizard added for 'SFML project'
Project wizard added for 'Static library'
Project wizard added for 'Shared library'
Project wizard added for 'wxWidgets project'
Build-target wizard added for 'Console'
Build-target wizard added for 'Static library'
Build-target wizard added for 'wxWidgets'
Project wizard added for 'Arduino Project'
Project wizard added for 'ARM Project'
Project wizard added for 'AVR Project'
Project wizard added for 'MSP430 Project'
Project wizard added for 'TriCore Project'
Project wizard added for 'PowerPC Project'
Project wizard added for 'MCS51 Project'
File(s) wizard added for 'Empty file'
File(s) wizard added for 'C/C++ source'
File(s) wizard added for 'D source'
File(s) wizard added for 'C/C++ header'
File(s) wizard added for 'Fortran source'
File(s) wizard added for 'Java source'
Scripted wizard plugin activated
SmartIndentHDL plugin activated
DoxyBlocks plugin activated
Class wizard plugin activated
Code statistics plugin activated
FileManager plugin activated
Help plugin plugin activated
SmartIndentPython plugin activated
Header Fixup plugin activated
ThreadSearch plugin activated
SmartIndentCpp plugin activated
SmartIndentLua plugin activated
Project options manipulator plugin activated
SmartIndentXML plugin activated
SmartIndentFortran plugin activated
Koders query plugin activated
Debugger plugin activated
NassiShneidermanPlugin plugin activated
Code snippets plugin activated
Copy Strings to clipboard plugin activated
SmartIndentPascal plugin activated
Added compiler "GNU GCC Compiler"
Added compiler "Intel C/C++ Compiler"
Added compiler "GDC D Compiler"
Added compiler "GNU Fortran Compiler"
Added compiler "G95 Fortran Compiler"
Added compiler "GNU GCC Compiler for ARM"
Added compiler "GNU GCC Compiler for TriCore (HighTec)"
Added compiler "*No Compiler*"
Added compiler "Tiny C Compiler"
Added compiler "Digital Mars D Compiler"
Added compiler "GNU GCC Compiler for MSP430 (HighTec)"
Added compiler "GNU GCC Compiler for Blackfin"
Added compiler "GNU GCC Compiler for LM32"
Added compiler "GNU GCC Compiler for PowerPC EABI"
Added compiler "GNU GCC Compiler for AVR"
Added compiler "LLVM Clang Compiler"
Added compiler "GNU GCC Compiler for Android"
Added compiler "GNU GCC Compiler for PowerPC (HighTec)"
Added compiler "GNU GCC Compiler for LM8"
Added compiler "GNU GCC Compiler for ZPU"
Added compiler "LLVM D Compiler"
Added compiler "Small Device C Compiler"
Added compiler "PGI Fortran Compiler"
Compiler plugin activated
Source Exporter plugin activated
Symbol Table Plugin plugin activated
Keyboard shortcuts plugin activated
Loading toolbar...
Initializing plugins...
KeyBinder failed UpdateById on[919][Backup_failsafe]
KeyBinder failed UpdateById on[920][backup_latest_beta]

(codeblocks:29248): Gtk-CRITICAL **: 19:06:06.068: IA__gtk_tree_model_iter_nth_child: assertion 'n >= 0' failed
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 03:25:48 pm
(http://forums.codeblocks.org/index.php?action=dlattach;topic=23104.0;attach=9509)

Here is a screenshot of what I was getting every time I started codeblocks. That little yellow warning box would pop up for a few seconds and then disappear. Codeblocks would then function fine, but I still couldn't use the wxsmith plugin.

The message states that this is usually caused when a plugin is built for a different version of codeblocks; but all the plugins and the main program itself was built from the same archive. So I figured the only thing it could be is that some parts of another version of codeblocks that was installed using apt-get was still installed; so I did a 'sudo apt-get purge codeblocks'. Not much happened, but I followed that with 'sudo apt-get autoremove' to remove libraries that weren't needed. I then tried starting codeblocks and it wouldn't start; so I figured, I would start fresh. I did a 'sudo make uninstall' to completely remove what was there and followed that with 'sudo make clean'. I then deleted the folder and extracted a new folder and went through the ./configure, make, make install routine. Now every time I start codeblocks, I get the following:
(http://forums.codeblocks.org/index.php?action=dlattach;topic=23104.0;attach=9511)

I click continue as two more appear with each click exactly the same and then codeblocks starts and this time wxsmith works correctly. That assertion I get has something to do with wrong size images being loaded into imagelists. Can someone please tell me how to fix this problem?
Title: Re: wxsmith plugin, where is it?
Post by: BlueHazzard on February 12, 2019, 04:07:18 pm
Can you expand the Backtrace in the error message window and post it here? I was thinking that obfuscated fixed this error some time ago...
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 05:04:39 pm
Can you expand the Backtrace in the error message window and post it here? I was thinking that obfuscated fixed this error some time ago...

ASSERT INFO:
./src/generic/imaglist.cpp(85): assert "bitmapSize == m_size" failed in Add(): All bitmaps in wxImageList must have the same size

BACKTRACE:
[1] wxGenericImageList::Add(wxBitmap const&)
[2] wxsResourceTree::LoadImage(wxString const&)
[3] wxsAutoResourceTreeImage::wxsAutoResourceTreeImage(wxString const&, bool)
[4] wxsRegisterItem<wxsStaticBitmap>::wxsRegisterItem(wxString, wxsItemType, wxString, long, bool)
[5] _dl_catch_exception
[6] _dl_catch_exception
[7] _dl_catch_error
[8] dlopen
[9] wxDynamicLibrary::RawLoad(wxString const&, int)
[10] wxDynamicLibrary::Load(wxString const&, int)
[11] PluginManager::LoadPlugin(wxString const&)
[12] PluginManager::ScanForPlugins(wxString const&)
[13] wxEntry(int&, wchar_t**)
[14] __libc_start_main
Title: Re: wxsmith plugin, where is it?
Post by: BlueHazzard on February 12, 2019, 06:49:52 pm
sadly this does not tell us what plugin causes the error...
Do you start codeblocks through the command line?
If you stop codeblocks with this error message, what plugin is the last that was loaded?


I do not get this error...
Can it be that there are some old resources still left from the old codeblocks installation?
Have you deleted the ~/.config/codeblocks folder?
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 08:18:31 pm
sadly this does not tell us what plugin causes the error...
Do you start codeblocks through the command line?
If you stop codeblocks with this error message, what plugin is the last that was loaded?


I do not get this error...
Can it be that there are some old resources still left from the old codeblocks installation?
Have you deleted the ~/.config/codeblocks folder?

I deleted that folder just now and started codeblocks. The same thing happened. Are there any other folders I should try deleting?

Here is what my commandline looks like when started at the terminal:

~ $ codeblocks
Starting Code::Blocks Release 17.12  rev 11256 Feb 11 2019, 22:15:17 - wx3.1.2 (Linux, unicode) - 64 bit
Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading menubar...
Valgrind: loaded
cbDragScroll: loaded
lib_finder: loaded
EditorTweaks: loaded
FilesExtensionHandler: loaded
Abbreviations: loaded
EditorConfig: loaded
RegExTestbed: loaded
Profiler: loaded
AutoVersioning: loaded
OpenFilesList: loaded
EnvVars: loaded
Autosave: loaded
HexEditor: loaded
./src/generic/imaglist.cpp(85): assert "bitmapSize == m_size" failed in Add(): All bitmaps in wxImageList must have the same size


It happens right after HexEditor loaded. The incrementalSearch is supposed to load next according to one of my previous posts.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 08:39:36 pm
I went into the manage plugins dialog and matched all entries to what I have seen on the commandline in an older post. Every one of them had been accounted for except the one called KeyBinder. It's the only one that is not in the list and in an older post it said that KeyBinder failed. So I think KeyBinder is the culprit.

Nope, I looked again. Keybinder is in the list under the name Keyboard Shortcuts.
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 12, 2019, 08:47:17 pm
Uninstall every package related to codeblocks. Then go to /usr and /usr/local and inspect them for files related to codeblocks. Delete those files. Reinstall the packages...
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 12, 2019, 09:17:09 pm
Uninstall every package related to codeblocks. Then go to /usr and /usr/local and inspect them for files related to codeblocks. Delete those files. Reinstall the packages...

After an uninstall, all I see if a bunch of empty directories.

/usr/local/lib/wx/config/ contains a program called gtk2-unicode-3.1

Is this program specifically for wxwidgets? or is it needed by the system. There's also a file called setup.h in /usr/local/lib/wx/include/gtk2-unicode-3.1/wx/
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 13, 2019, 12:34:07 am
The system stuff is not stored in /usr/local. If you've not installed anything else from source it is probably the best idea to delete everything from this folder.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 13, 2019, 04:27:39 am
Should the following be deleted? Or better yet removed with package manager?

/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_baseu_xml-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_baseu_xml-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_baseu_xml-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_aui-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_gl-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_gl-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_gl-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_media-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_media-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_media-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_propgrid-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_propgrid-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_propgrid-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_qa-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_qa-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_qa-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_ribbon-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_ribbon-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_ribbon-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_richtext-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_richtext-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_richtext-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_stc-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_stc-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_stc-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_xrc-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_xrc-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_xrc-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_adv-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_aui-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_gl-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_gl-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_gl-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_html-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_media-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_media-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_media-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_propgrid-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_propgrid-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_propgrid-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_qa-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_qa-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_qa-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_ribbon-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_ribbon-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_ribbon-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_richtext-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_richtext-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_richtext-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_stc-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_stc-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_stc-3.0.so.0.4.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_xrc-3.0.so
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_xrc-3.0.so.0
/usr/lib/x86_64-linux-gnu/libwx_gtk3u_xrc-3.0.so.0.4.0

Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 13, 2019, 09:23:53 am
If you've added the files with a manual compilation command then yes, if the files are owned by a package then no.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 13, 2019, 02:30:15 pm
Here is what I did after completely cleaning up my system. I downloaded the prebuilt packages for debian on the sourceforge site. The packages in my repository are old and out of date which is why I opted to build them in the first place. So I opened the archive codeblocks_17.12-1_amd64_stable.tar.xz and started installing the packages.

I was able to install all but the codeblocks-contrib_17.12-1_amd64.deb

It gave me the following error:

dpkg: dependency problems prevent configuration of codeblocks-contrib:
 codeblocks-contrib depends on libhunspell-1.4-0; however:
  Package libhunspell-1.4-0 is not installed.


My system already has libhunspell-1.6-0 installed. Shouldn't it still work with the newer version of hunspell?

At this point, if I start codeblocks, it starts up fine, but a little yellow warning pops up to tell me that libSpellChecker.so failed. All of the other plugins appear to have installed. If I fire up synaptic package installer, it will tell me I have a broken package, naming codeblocks-contrib_17.12-1_amd64.deb. So if I uninstall that and fire up codeblocks, it starts up with no warnings, but I can see that most of the plugins are not installed.

Where do I go from here? I'd like to have all those plugins working on my copy of codeblocks, but how will I do that if the package demands an old outdated library? Is there a way I can rebuild that particular package so it will accept the newer hunspell?
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 13, 2019, 07:59:24 pm
Why don't you use the packages that you have build yourself?
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 13, 2019, 08:40:07 pm
Why don't you use the packages that you have build yourself?

Well, first of all, the packages I built myself have similar problems which isn't going anywhere. I did not give up on them, I just wanted to test and see what happens with prebuilt packages first; because I know I could always just uninstall them afterwards and bring me right back to where I was. So the fact is there is DEFINITELY something wrong with the plugins so far as compatibility. I would definitely work with someone on this issue to get it resolved so other people aren't impacted by the same problems I'm having. If I could put together a package that will work in my distribution, I'd sign it and submit it to the repository to replace the old outdated codeblocks they currently have.
Title: Re: wxsmith plugin, where is it?
Post by: oBFusCATed on February 13, 2019, 08:52:41 pm
If you make this command
Code: [Select]
dpkg-buildpackage -us -uc
to succeed you'll have the same packages you download from the site, but they'll have the proper dependencies and they will work on your system.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 13, 2019, 11:20:10 pm
If you make this command
Code: [Select]
dpkg-buildpackage -us -uc
to succeed you'll have the same packages you download from the site, but they'll have the proper dependencies and they will work on your system.

When I do that I get:

rmdir --ignore-fail-on-non-empty .
rmdir: failed to remove '.': Invalid argument
/usr/share/cdbs/1/class/autotools.mk:64: recipe for target 'makefile-clean' failed
make: [makefile-clean] Error 1 (ignored)


which continues with what looks like productive compiling, followed by a lot of checking and then a lot of creating which looks like the completion of a config.

then make is invoked with /usr/bin/make -C . -j8

followed by x86_64-linux-gnu-g++
 
Then this fatal error pops up.

In file included from ./sdk_precomp.h:13:0:
./sdk_common.h:37:10: fatal error: wx/wxprec.h: No such file or directory
 #include <wx/wxprec.h>


I checked; there actually is a wxprec.h file in /usr/include/wx-3.0/wx/

..but for some reason, it can't find it. Like I said before, I have decades of programming experience, but I've only a few months experience working in a Linux environment, so a lot of this stuff is new to me; however, I am more than willing to learn if someone can help me out and point me in the right direction.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 14, 2019, 04:12:46 pm
I deleted a bunch of empty file trees and ran the command again; didn't realize that empty directories would interfere with a build. This time it started building packages.

It built:

codeblocks-common_17.12_all.deb
codeblocks-contrib-common_17.12_all.deb
codeblocks-headers_17.12_all.deb
codeblocks-wxcontrib-headers_17.12_all.deb
wxsmith-headers_17.12_all.deb

then I get:

dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libhunspell-1.7.so.0 (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/libSpellChecker.so)
Hint: check if the library actually comes from a package.

and finally:

recipe for target 'binary-predeb-IMPL/codeblocks-contrib' failed
make: *** [binary-predeb-IMPL/codeblocks-contrib] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2

I'm getting so close! Anyone know what I can try next to alleviate the problem?
Title: Re: wxsmith plugin, where is it?
Post by: BlueHazzard on February 14, 2019, 04:44:08 pm
I am fascinated how many problems your have xD, and more that you still stick to it! My compliment for your endurance!
for me it was always more or less a configure and make....

Have you installed libhunspell via packet manager or by compiling by yourself?
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 14, 2019, 06:27:58 pm
I am fascinated how many problems your have xD, and more that you still stick to it! My compliment for your endurance!
for me it was always more or less a configure and make....

Have you installed libhunspell via packet manager or by compiling by yourself?

I could now do a configure, make and install and it installs and runs codeblocks with all plugins with no errors or warnings. However, I just can't build all the packages if I go the route of 'dpkg-buildpackage -us -uc'.

I could just call it a day and move on, but my curiosity keeps me determined to find out why I can't build the packages the way I should be able to. I'd prefer installing from packages if I could build them. Understanding what the problem is will pay off the next time I have to build from source. It's odd though how I could make them now, but get stuck at that error when I try to build the packages.
Title: Re: wxsmith plugin, where is it?
Post by: stahta01 on February 14, 2019, 07:47:23 pm
From where are you getting the debian src packages for Code::Blocks?

I always did a src package build using a repo of one of the CB Team or Developer.

Tim S.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 14, 2019, 08:19:21 pm
From where are you getting the debian src packages for Code::Blocks?

I always did a src package build using a repo of one of the CB Team or Developer.

Tim S.

The source I get from here http://sourceforge.net/projects/codeblocks/files/Sources/17.12/codeblocks_17.12.tar.xz. (http://sourceforge.net/projects/codeblocks/files/Sources/17.12/codeblocks_17.12.tar.xz.)
Title: Re: wxsmith plugin, where is it?
Post by: osdt on February 14, 2019, 09:21:26 pm
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libhunspell-1.7.so.0 (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/libSpellChecker.so)
Hint: check if the library actually comes from a package.

Your package depends on the self-built libhunspell, which is not allowed for good reasons. Remove it from your system, install libhunspell-dev provided by your distribution.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 14, 2019, 10:16:02 pm
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libhunspell-1.7.so.0 (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/libSpellChecker.so)
Hint: check if the library actually comes from a package.

Your package depends on the self-built libhunspell, which is not allowed for good reasons. Remove it from your system, install libhunspell-dev provided by your distribution.

I have the libhunspell provided by my distribution. I installed it with sudo apt-get install libhunspell-dev
Title: Re: wxsmith plugin, where is it?
Post by: osdt on February 14, 2019, 10:44:11 pm
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libhunspell-1.7.so.0 (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/libSpellChecker.so)
Hint: check if the library actually comes from a package.

Your package depends on the self-built libhunspell, which is not allowed for good reasons. Remove it from your system, install libhunspell-dev provided by your distribution.

I have the libhunspell provided by my distribution. I installed it with sudo apt-get install libhunspell-dev
The error message above clearly states that libSpellChecker.so was linked against /usr/local/lib/libhunspell-1.7.so.0 which is not provided by any package installed on your system.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 14, 2019, 11:16:18 pm
dpkg-shlibdeps: error: no dependency information found for /usr/local/lib/libhunspell-1.7.so.0 (used by debian/codeblocks-contrib/usr/lib/codeblocks/plugins/libSpellChecker.so)
Hint: check if the library actually comes from a package.

Your package depends on the self-built libhunspell, which is not allowed for good reasons. Remove it from your system, install libhunspell-dev provided by your distribution.

I have the libhunspell provided by my distribution. I installed it with sudo apt-get install libhunspell-dev
The error message above clearly states that libSpellChecker.so was linked against /usr/local/lib/libhunspell-1.7.so.0 which is not provided by any package installed on your system.

Yes, I know; it's something that has me perplexed.

if I type 'sudo apt install libhunspell-dev'

Reading package lists... Done
Building dependency tree       
Reading state information... Done
libhunspell-dev is already the newest version (1.6.2-1).

It shows I have libhunspell v1.6 installed; which is the one listed in the package manager.

The libhunspell v1.7 I tarred the files before deleting them from /usr/lib and I tried building the packages and it failed immediately because of a dependency on libhunspell; particularly that one (v1.7), even though I have v1.6 installed on my system. I even uninstalled and reinstalled v1.6 but I got the same results. There is something on my system that's telling it where to find libhunspell and it is pointing to the v1.7 one in usr/lib. If I can find where that is, I could fix this problem. So I restored the v1.7 for the tar file to the /usr/lib directory and I was able to make the code; even though I still can't build packages.
Title: Re: wxsmith plugin, where is it?
Post by: jjenson on February 15, 2019, 12:47:37 am
I fixed the problem. I did a 'grep -r libhunspell' in the build folder and it came back with a lot of references to the libhunspell-1.7 library. After deleting the folder and creating a new one, I tried the grep on the new folder and it came back with a lot of references to the outdated libhunspell-1.3 library; I guess that's the default.

When I deleted the libhunspell-1.7 files, I deleted the folder which holds the source and created a new one, but I didn't realize that when you run the build, it creates an archive one folder up from the current directory and I think that archive contains info from the previous build that interfered with the next build. I also thought about the possibility that some environmental variables were created during the build that carried over when I did the build again because I was using the same terminal window. So I made sure to not only delete the archive, but to also create a new terminal window before doing the build.

The build completed, created all the deb packages and I installed them without issue. Everything works well now. I'd like to thank everyone who had patience with me and helped me in one way or another.