Recent Posts

Pages: 1 2 [3] 4 5 6 7 8 ... 10
21
Help / Completion suddenly stopped working
« Last post by questionderby on Yesterday at 08:30:16 pm »
Hi! So I'm a beginner programmer, trying to learn C, and I picked Code::Blocks for this purpose. I'm on Void Linux, using Code::Blocks 20.03

I don't really understand the IDE yet, I'm trying to learn it. So I was trying to change the GTK theme to something dark so my eyes can rest. I changed $GTK_THEME for this purpose to Yaru:dark on my shell.

Code
GTK_THEME=Yaru:dark codeblocks

Just right after I launched codeblocks with this(and it worked btw, it was a dark theme), code completion suddenly stopped working. I looked around in the settings(editor, environment and whatnot) and couldn't find much about it. I also searched around a little on the internet, still no solutions :/

How do I go about fixing this little issue? Sorry if it's a simple thing and I wasted time on it, thanks for reading
22
The https://www.codeblocks.org/downloads/binaries/ page references CB 13.12 for mac with the following Sourceforge link:
https://sourceforge.net/projects/codeblocks/files/Binaries/13.12/MacOS/CodeBlocks-13.12-mac.zip

BUT on Sourceforge in the https://sourceforge.net/projects/codeblocks/files/Binaries/17.12/Mac/ directory is the  following file:
codeblocks-17.12_OSX64.dmg

So is there a CB 12.12 for the mac or not? If there is then the download page

I am not a mac user/dev and only know that a DMG file is usually a mac osx installer package/file.
23
Development / Re: RFC: Backticks
« Last post by ollydbg on Yesterday at 12:09:25 pm »
FYI:

I recently found that msys2 has a nice tool named pkg-config, which is located in msys2_root/mingw64/bin/pkg-config.exe

Now, I see in code::blocks, it can support many libraries. For example, if you want to link opencv library.

You just have to add one line in compiler options in C::B build option

Code
`pkg-config --cflags opencv4`

and in library options in C::B build option

Code
`pkg-config --libs opencv4`

Really nice feature, also, I think it should also work under Linux. :)
24
Embedded development / Re: C::B for Microchip MCUs?
« Last post by stahta01 on Yesterday at 03:35:41 am »
FYI: The SDCC only supports a very small sub-set of Microchip MCUs.

Tim S.
25
Embedded development / Re: C::B for Microchip MCUs?
« Last post by AndrewCot on Yesterday at 01:55:54 am »
A google search on "codeblocks PIC compiler" returned the following pages that should help you out configuring CB with SDCC for use with PIC uControllers:

https://wiki.codeblocks.org/index.php/Using_the_Code::Blocks_IDE_with_SDCC_on_PIC_MCUs
http://www.iearobotics.com/wiki/index.php?title=CodeBlock_IDE_and_PIC_microcontrollers

If you do not know what SDCC is then have a look at the following main SDCC page:
http://sdcc.sourceforge.net/

You can search the CB forums for "SDCC" or the compiler you want to use to see if there are details on configuring it for use with CB.
26
I am really me and I am here ... definitely "slowandsteady"

Give me 18 months, and in return I give you a competent C++ programmer.
27
Embedded development / Re: C::B for Microchip MCUs?
« Last post by oBFusCATed on June 22, 2021, 03:28:27 pm »
What support do you need?
It should currently be possible to do this if you do these steps:
1. Install the compiler
2. Set it up inside codeblocks
3. Create empty project which uses this compiler
4. Add files
5. Setup build options for your device
6. Add post build commands to do firmware gathering or/and upload in your environment.
7. enjoy

If you need to do these steps often you can write a wizard template script which automates the stuff above and then provide a patch for inclusion in the C::B releases.
28
Embedded development / C::B for Microchip MCUs?
« Last post by knivd on June 22, 2021, 12:12:31 pm »
I quite like the Code Blocks environment and was wondering, is it not possible to include support for the PIC families in it? I can see a lot of other platforms are already there.
Thanks!
30
Development / Re: RFC: Backticks
« Last post by ollydbg on June 22, 2021, 05:50:56 am »
You don't need them there. wx-config works fine on linux as it is now.

The good news is that eranif's wx-config-msys2 tool also works well with our C::B's backtick system.

I try to add those lines in the "Other linker options"
Code
`wx-config-msys2 --libs --prefix=$(TARGET_COMPILER_DIR)`

And I got the final result of the linke command:

Code
-LF:\code\msys2-64\mingw64\\lib -pipe -Wl,--subsystem,windows -mwindows -lwx_mswu_xrc-3.1 -lwx_mswu_html-3.1 -lwx_mswu_qa-3.1 -lwx_mswu_core-3.1 -lwx_baseu_xml-3.1 -lwx_baseu_net-3.1 -lwx_baseu-3.1

The only issue is that for C::B, we have $(TARGET_COMPILER_DIR) translated to "F:\code\msys2-64\mingw64\", while, wx-config-msys2 expect there is no ending backslash for the path, so you see double backslashes in the generated command line.
Pages: 1 2 [3] 4 5 6 7 8 ... 10