Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
Nightly builds / Re: The 18 February 2023 build (13215) is out.
« Last post by Miguel Gimenez on Today at 09:29:46 am »
The DLL and the unzip instructions are only for Windows, use just the DMG file (I do not know how a DMG is used, but should be straightforward).
2
Nightly builds / Re: The 18 February 2023 build (13215) is out.
« Last post by boojai2 on Today at 06:04:37 am »
Hi everyone,

I am absolute newbie here and trying to learn C and C++. I'm using mac OS and having a hard time getting codeblocks working on my computer.
I am using OSX 13.2.1.
I was following this post and trying to get nighty C::B working on my computer. I have tried the MacPorts way but C::B was not functioning properly (reversed colour).

From what I am reading, I need to download CB_20230218_rev13215_macOS-11.6_x64-wx3.1.6.dmg, CB_20230218_rev13215_wx32_win64.7z from the google drive below. And wxWidge dll, Mingw64 dll from the first post.

And now I'm confused about the next steps.
1) unzip the CB nightly in some directory - the dmg that I can download does not need to be unzipped??
2) unzip both ddl's into the same directory where I unzipped the nighty.

Can someone please help me with my first step in learning C and C++?  :'(

Thanks in advance!


Hi.

OS X version of this rev can be downloaded from my Google Drive.
There is only a macOS-11.6 version.
Note that it is not a notarized version of the application.

32 bits version for Windows can also be found in the same place.

Debian Buster and Bullseye (32 and 64 bits) can be installed from my repo.

Regards
Xav'
3
Announcements / Re: Remote Debugging: "Interrupting debugger failed :("
« Last post by ollydbg on Yesterday at 04:52:10 pm »
I'm not fully understand the code change in rev https://sourceforge.net/p/codeblocks/code/11858/

If I remember correctly, many years ago, under C::B, I can use gdb.exe to connect with gdbserver.exe, and use gdbserver.exe to debug(control) a local exe file.

Many embedded development need remote debugging feature, so this is a big regression.
4
FYI:

I modify the Code::Blocks' opencv project wizard to linking msys2's opencv library(currently, its opencv4)

I put the wizard.script here: https://gist.github.com/asmwarrior/93c3f6f0efa8a826c206446632d856f1

Also, the source code should be updated like below:

Code
#include <opencv2/core/core.hpp>
#include <opencv2/imgproc/imgproc.hpp>
#include <opencv2/highgui/highgui.hpp>
using namespace cv;

int main(int argc, char *argv[])
{
    Mat img = imread("arnold_schwarzenegger.jpg", IMREAD_COLOR);
    if(img.empty())
       return -1;
    namedWindow("arnold_schwarzenegger", WINDOW_AUTOSIZE );
    imshow("arnold_schwarzenegger", img);
    waitKey(0);
    return 0;
}

The IMREAD_COLOR and WINDOW_AUTOSIZE is new options for opencv4. Our old wizard using the opencv2 options.
5
You mean:

Menu->File->New?

There is a plugin named "File Manager", you can right click on the folder(in the folder navigation panel), and in the context menu, click the "New File".

6
In vs code it is easy to create new files in a folder, there is a sidebar given to us for that. Is there a plugin that's able to do that in code blocks?
7
Help / Re: CodeBlocks starts really slow
« Last post by Pecan on Yesterday at 07:12:58 am »
No, no - Compiler itself works fine - when it finally starts up :)

We are talking about fire it up. When You want the application to start. On my computer I have to wait a bit less than 2min.

You just click in icon in Windows named Codeblock and wait...wait...wait...after 2min Codeblocks appears and then You can work normally.

How fast can You start it on Your computer?

He still has not told us what OS he's running, has he?
I had the same problem on both Win 10 and Win 11. But the fix was different for each.

Please, what OS are you running?
8
Help / Re: CodeBlocks starts really slow
« Last post by BlueHazzard on March 25, 2023, 11:54:26 pm »
20 sec, but i have some failed plugins that take some time...

Ok, now that we finally know what is going on, lets work on the problem.
First step to try is to open codeblocks go to menu Plugins->Manage plugins->Select all plugins from the list (you can select the first, then press shift key and select the last, to select all)->Disable
Restart codeblocks and look if it is still slow.

If it is not slow, you can make a bisection search for the plugin that slows codeblocks down.
For this enable the first half of the plugins and start codeblocks again. If it is still fast, disable the plugins again.
Then repeat the algorithm with the second half. Disable the half plugins of the half that slows down codeblocks. This goes on until one plugin is left. At the end you should have a plugin that is the culprit from the slow down.

If codeblocks starts also slow without plugins we have to make things a bit more complicated...
9
Help / Re: CodeBlocks starts really slow
« Last post by stdstringclass on March 25, 2023, 11:21:50 pm »
No, no - Compiler itself works fine - when it finally starts up :)

We are talking about fire it up. When You want the application to start. On my computer I have to wait a bit less than 2min.

You just click in icon in Windows named Codeblock and wait...wait...wait...after 2min Codeblocks appears and then You can work normally.

How fast can You start it on Your computer?
10
Help / Re: How to configure CodeBlocks for an Arduino project
« Last post by BlueHazzard on March 25, 2023, 10:06:16 pm »
Sadly the arduino wizard is broken... I do not think there is an easy fix...
Pages: [1] 2 3 4 5 6 ... 10