Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
Help / Re: Stripping debug info from output tree
« Last post by wtfisgoingoff on March 09, 2025, 03:47:09 am »
Using an MSYS2 UCRT64 bash shell on my Windows 10 setup, I see that I have:
$ where strip
C:\msys64\ucrt64\bin\strip.exe
C:\msys64\usr\bin\strip.exe
$ pacman -Qo /ucrt64/bin/strip.exe
/ucrt64/bin/strip.exe is owned by mingw-w64-ucrt-x86_64-binutils 2.44-1
$ pacman -Qo /usr/bin/strip.exe
/usr/bin/strip.exe is owned by binutils 2.44-1

If you feed tentative shell commands through something like
$(TARGET_COMPILER_DIR)..\usr\bin\env MSYSTEM=UCRT64 CHERE_INVOKING=1 /usr/bin/bash -lc

you can let MSYS2 find the best version to use. In the above instance, it will use an /ucrt64/bin version if exists; otherwise it will look for what essentially is a Cygwin based version in /usr/bin. If that also fails, it will then look for a system version.
$ where xcopy
C:\Windows\System32\xcopy.exe

Unfortunately, syntax for Windows xcopy is:
xcopy <Source> [<Destination>] [/w] [/p] [/c] [/v] [/q] [/f] [/l] [/g] [/d [:MM-DD-YYYY]]   [/s [/e]] [/t] [/k] [/r] [/h] [{/a | /m}] [/n] [/o] [/x] [/exclude:FileName1[+[FileName2]][+[FileName3]]] [{/y | /-y}] [/z]  [/j] [/compress]

Note, all options come after file specifiers, not before! It's easy enough to make a version of things with the xcopy options flipped to after all file specifiers. These command files like never change.
I got 4 strip.exe
D:\MSYS2\usr\bin\strip.exe
D:\MSYS2\ucrt64\bin\strip.exe
D:\MSYS2\ucrt64\x86_64-w64-mingw32\bin\strip.exe
D:\MSYS2\usr\x86_64-pc-msys\bin\strip.exe
This one [D:\MSYS2\usr\x86_64-pc-msys\bin\strip.exe] didn't show those
'output32_64\*.exe': No such file   'output32_64\*.dll': No such file   'output32_64\share\CodeBlocks\plugins\*.dll': No such file   

But none stripping was done. Every file should be stripping  is  still very large.
52
Help / Re: Code completion doesn't show up for some wxWidgets
« Last post by Pecan on March 09, 2025, 12:54:13 am »
I have prepared and attached simple demo. Created it from wxwidgets template project. You must change compiler settings, linker settings and search directories in debug mode to your own because I have wxwidgets installation in custom home directory. Problematic variables are: mListCtrlSources and thisNOTwork (I already started they with -> )

Thanks for the example code.
I have verified that the legacy CodeCompletion plugin will not produce completion choices for the code you indicated.
Code
    wxStaticBoxSizer * staticBoxSource = new wxStaticBoxSizer(wxHORIZONTAL, this, "Source dirs && files");
    wxListCtrl* mListCtrlSources = new wxListCtrl(this, -1);
    mListCtrlSources->

... and others ..

In order to produce completions for your code, you will have to use the Clangd_client plugin instead.

Info:
The instuctions for using the Clangd_client language server protocol (LSP):
https://wiki.codeblocks.org/index.php/CB_Clangd_Client

If clangd is already installed on your Linux system, you need only disable the CodeCompletion plugin, enable the Clangd_client plugin, and restart CodeBlocks.

Go to the Settings/Clangd_client/ and enter the address of your Clang executable.


53
Help / Re: Code completion doesn't show up for some wxWidgets
« Last post by Dibo on March 08, 2025, 12:36:55 pm »
I have prepared and attached simple demo. Created it from wxwidgets template project. You must change compiler settings, linker settings and search directories in debug mode to your own because I have wxwidgets installation in custom home directory. Problematic variables are: mListCtrlSources and thisNOTwork (I already started they with -> )
54
Help / Re: Code completion doesn't show up for some wxWidgets
« Last post by Pecan on March 08, 2025, 07:21:53 am »
Can you give us some examples or a 1,2,3 type do this then that kind of instructions so we can have something to work with that causes the problem?

Thanks
55
Help / Re: Stripping debug info from output tree
« Last post by everSome on March 07, 2025, 12:17:14 pm »
Using an MSYS2 UCRT64 bash shell on my Windows 10 setup, I see that I have:
$ where strip
C:\msys64\ucrt64\bin\strip.exe
C:\msys64\usr\bin\strip.exe
$ pacman -Qo /ucrt64/bin/strip.exe
/ucrt64/bin/strip.exe is owned by mingw-w64-ucrt-x86_64-binutils 2.44-1
$ pacman -Qo /usr/bin/strip.exe
/usr/bin/strip.exe is owned by binutils 2.44-1

If you feed tentative shell commands through something like
$(TARGET_COMPILER_DIR)..\usr\bin\env MSYSTEM=UCRT64 CHERE_INVOKING=1 /usr/bin/bash -lc

you can let MSYS2 find the best version to use. In the above instance, it will use an /ucrt64/bin version if exists; otherwise it will look for what essentially is a Cygwin based version in /usr/bin. If that also fails, it will then look for a system version.
$ where xcopy
C:\Windows\System32\xcopy.exe

Unfortunately, syntax for Windows xcopy is:
xcopy <Source> [<Destination>] [/w] [/p] [/c] [/v] [/q] [/f] [/l] [/g] [/d [:MM-DD-YYYY]] [/u] [/i] [/s [/e]] [/t] [/k] [/r] [/h] [{/a | /m}] [/n] [/o] [/x] [/exclude:FileName1[+[FileName2]][+[FileName3]]] [{/y | /-y}] [/z] [/b] [/j] [/compress]

Note, all options come after file specifiers, not before! It's easy enough to make a version of things with the xcopy options flipped to after all file specifiers. These command files like never change.
56
Help / Re: Code completion doesn't show up for some wxWidgets
« Last post by Dibo on March 06, 2025, 10:16:44 pm »
In plugins manager I have this one:

Code completion 1.0
/usr/lib/codeblocks/plugins/libcodecompletion.so
This plugin provides a symbols browser for your projects and code-completion inside the editor.
57
Help / Re: Code completion doesn't show up for some wxWidgets
« Last post by stahta01 on March 06, 2025, 09:45:46 pm »
See if the Code::Blocks (CB) you have has the clang based code completion (CC) plugin and if yes maybe someone can tell you what else to install to get it to work. The old CC is not very good, so someone created the new clang LSP based one. The new CC is still lacking a few features of the old CC.

Tim S.

58
Help / Code completion doesn't show up for some wxWidgets
« Last post by Dibo on March 06, 2025, 07:50:38 pm »
Hi,
I'm newbie in CodeBlocks and wxWidgets. Started writting some app and noticed that some wxWidgets doesn't have code completion, just nothing popup after -> or forced by CTRL+SPACE (sometimes I see hint that parsers is still working). So far these are problematic classes: wxListCtrl and wxSearchCtrl. I have code blocks 20.03+svn13046-0.3build2 (standard installation from Linux Mint repo). Tried everything found by google like disabling SmartSense (this result with hint that result is too big and start typing first letter but nothing happens). Also in C++ parser changed one parser per workspace, didn't help neither. Found also similar issue 10 years ago:
https://forums.codeblocks.org/index.php?topic=20175.0

Notice that I have wxWidgets installation in custom folder but CodeBlocks compiler, linker and search directory is configured fine because everything is compiling and debugging works too. Also, code completion for these classes in Visual Studio Code works fine
59
Help / Re: Problem writing in forum
« Last post by stahta01 on March 06, 2025, 12:34:46 am »
FYI: Sometimes it is possible for an invisible character to be the cause of these types of problems.
I have no idea if that has happened on this website or not.
On this website, the few times I have remembered had all been some type of quote.

Tim S.
60
Help / Re: Problem writing in forum
« Last post by Miguel Gimenez on March 05, 2025, 06:11:10 pm »
All reported cases have been caused by non-ASCII characters...
Pages: 1 2 3 4 5 [6] 7 8 9 10