Author Topic: wxsmith plugin, where is it?  (Read 1939 times)

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #30 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.

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #31 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.
« Last Edit: February 12, 2019, 08:41:40 pm by jjenson »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11654
    • Travis build status
Re: wxsmith plugin, where is it?
« Reply #32 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...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #33 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/

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11654
    • Travis build status
Re: wxsmith plugin, where is it?
« Reply #34 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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #35 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

« Last Edit: February 13, 2019, 04:33:18 am by jjenson »

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11654
    • Travis build status
Re: wxsmith plugin, where is it?
« Reply #36 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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #37 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?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11654
    • Travis build status
Re: wxsmith plugin, where is it?
« Reply #38 on: February 13, 2019, 07:59:24 pm »
Why don't you use the packages that you have build yourself?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #39 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.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11654
    • Travis build status
Re: wxsmith plugin, where is it?
« Reply #40 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.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #41 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.

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #42 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?

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2300
Re: wxsmith plugin, where is it?
« Reply #43 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?

Offline jjenson

  • Multiple posting newcomer
  • *
  • Posts: 29
Re: wxsmith plugin, where is it?
« Reply #44 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.