Recent Posts

21

Help / Re: Code completion not working on external (GLib) library

« Last post by oBFusCATed on Yesterday at 08:28:22 pm »

Since last version was released 7 years ago, my hopes aren't exactly high, but I'll do my best.

What are you talking about? The last version has been released in December 2017 (January 2018 to be precise) and there is new release in the making.

Should I use CB issue tracker? (https://sourceforge.net/p/codeblocks/tickets/) ?

Yes, thank you.

22

Using Code::Blocks / Re: Debugging projects with some foreign CMakeLists.txt inside

« Last post by oBFusCATed on Yesterday at 08:26:10 pm »

What is the selected target?
My guess is that it is all or install.
There is a chance that it will work if you select the target for the executable.
This is an area of the cmake integration I'm not really sure how to handle well.

23

Plugins development / Re: Keybinder v2 notes/problems

« Last post by oBFusCATed on Yesterday at 08:24:13 pm »

I don't remember, there is a chance I might have used a build from the release-20.xx branch.
Could you do some test with such a build and tell me if I've picked all required commits?

24

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by sodev on Yesterday at 06:21:30 pm »

This same code compiled and ran before I upgraded from wxWidgets 3.1.2 to 3.1.3, and I did not get these warnings.

No. Your original error was that the project used a non-existent compiler / toolchain and failed to execute a missing binary (the compiler). So you did more than "just" upgrade wxWidgets, the previous code also could not be compiled by a missing compiler. Then you did a lot of random changes that did not solve the original error and now you have a huge mess.

Upgrading wxWidgets is quite simple, especially if it's just a patchlevel upgrade, point to the new root directory (if you not simply replaced the contents of the current one) and do a FULL rebuild. That last step is the most "difficult" one, at least in my setup (CodeBlocks + MSVC) a simple Clean + Build / Rebuild in CodeBlocks does NOT remove everything so i manually delete all outputs (which is quite easy for me, because i do an out-of-tree build, i just delete the output folder, all outputs are inside there). Not sure if it works flawless with your setup, but a good candidate to get missed by the Clean step are precompiled headers.

Your warnings don't look like a x86/x64 mismatch, the linker should detect the architecture and spit out a different error / warning message (IIRC gcc does that on Linux). It looks like a static / dynamic mismatch of wxWidgets, you link the static libraries but the project is setup for dynamic libraries or reversed.

Best thing you can do is a fresh checkout of the last known working revision of your project and restart from there. It looks like your orginal project already is quite messy and contains dead settings and i don't know what else, but only upgrading wxWidgets should be an easy task. You should start with that first. And then you can try to switch the compiler and/or architecture, but for that you should better review the current settings and fix them properly.

25

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by stahta01 on Yesterday at 05:12:01 am »

There is no message here about what the error was. Maybe there is a clue in the warning messages. There are 308 warnings. This same code compiled and ran before I upgraded from wxWidgets 3.1.2 to 3.1.3, and I did not get these warnings. The below snippet of them shows only one of each error type. For each line in this snippet there are actually many more of same error.

I do not believe that! You had no idea what compiler you were using!
You do know that switching from an 32 bit to 64 bit compiler can cause issues!
And, switching compiler versions can cause issues!

I give up I will let someone else waste their time trying to help you!

Tim S.

26

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by stahta01 on Yesterday at 05:08:55 am »

Without the Compiler command no one can help you!!

Tim S.

27

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by spflanze on Yesterday at 05:01:38 am »

I re-enabled precompiled headers, and cleaned the project. I only get one error:

Code: [Select]

||=== Build: Debug in TIA Designer (compiler: TDM-GCC-64) ===|
||error: ld returned 1 exit status|
||=== Build failed: 1 error(s), 0 warning(s) (1 minute(s), 41 second(s)) ===|

There is no message here about what the error was. Maybe there is a clue in the warning messages. There are 308 warnings. This same code compiled and ran before I upgraded from wxWidgets 3.1.2 to 3.1.3, and I did not get these warnings. The below snippet of them shows only one of each error type. For each line in this snippet there are actually many more of same error.

Code: [Select]

C:\Engineering_Software\TIA Designer\src\wxComboBoxDataFilePD.cpp|16|warning: 'void wxComboBoxDataFilePD::InitDataPointers(PhotoDiode*)' redeclared without dllimport attribute: previous dllimport ignored [-Wattributes]|
C:\Engineering_Software\TIA Designer\src\wxComboBoxDataFilePD.cpp|141|warning: 'void wxComboBoxDataFilePD::UpdateDisplayFromDataFile()' redeclared without dllimport attribute after being referenced with dll linkage|
C:\Engineering_Software\TIA Designer\TIA_DesignerMain.cpp|1026|warning: cast between incompatible pointer to member types from 'void (TIA_DesignerFrame::*)(wxCommandEvent&)' to 'wxObjectEventFunction' {aka 'void (wxEvtHandler::*)(wxEvent&)'} [-Wcast-function-type]|

28

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by stahta01 on Yesterday at 04:40:41 am »

Without a build log I can not help you.
Edit: Include at most 12 linker error after the linker command.

You are likely missing a library or linking the libraries in the wrong order.

Tim S.

29

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by spflanze on Yesterday at 03:35:27 am »

Changing to  "TDM-GCC-64" in "Project -> Build Options" did it. The compiler is working now.

There still needs to be and adjustment made to the Linker. I get many errors of the form:

Code: [Select]

C:\Engineering_Software\TIA Designer\src\JunctionCap.cpp|332|undefined reference to `__imp__ZN11wxGridfData13UpdateDisplayEii'|

30

Using Code::Blocks / Re: Upgrading to wxWidgets 3.1.3

« Last post by stahta01 on Yesterday at 12:45:08 am »

In "Global compiler settings" the compiler is set for "TDM-GCC-64". Is that the wrong one? I attempted change it to "GNU GCC Compiler". But I find that after I close "Global compiler settings" by clicking on "OK", and then reopen it, that it has, all on its own, reverted to  "TDM-GCC-64". However  "GNU GCC Compiler" does show as the compiler in "Project => Build options..."

When you change the default compiler you need to select the Compiler in Global Settings and click on "Set as Default" button.

Tim S.