Recent Posts

11

Using Code::Blocks / Re: make: *** No rule to make target `Debug'. Stop.

« Last post by BlueHazzard on Yesterday at 12:02:55 am »

What are the rules of your makefile?

12

Using Code::Blocks / Re: Can't get it to run on Debian Buster missing libwx_gtk2u_richtext-2.8.so.0

« Last post by dfatcb on June 24, 2022, 05:18:34 pm »

Need to build 32 bit apps that run on all platforms and the main custom linux environment (which needs to run in limited memory) has the 32 bit libraries.  If they wouldn't have went with 32bit wchar and 64bit longs the transition would be much easier like on windows.   There is well over a million lines of code that would need to be reviewed and change.

But what is the debian package I need to install?  is it apt-get install wxWidgets ?

13

Using Code::Blocks / Re: make: *** No rule to make target `Debug'. Stop.

« Last post by Eli_A on June 24, 2022, 03:43:51 pm »

Hi,

I have the same problem.

I included the pcapplusplus.mk at my makefile:
include C:\Eli\Projects\dRDI\dRD_parser\mk\PcapPlusPlus.mk

Set the address at the PcapPlusPlus.mk as below:

PCAPPLUSPLUS_HOME := C:\pcapplusplus\pcapplusplus
MINGW_HOME := C:/MinGW/bin
PCAP_SDK_HOME := C:/WpdPack/include

Also, check the Custom make file and the make commands are as below:

$make -f $makefile $target
$make -f $makefile $file
$make -f $makefile clean$target
$make -q -f $makefile $target

But I get the below error:

mingw32-make.exe: *** No rule to make target 'Debug'.  Stop.

Can someone pls help me to solve this problem?

14

Using Code::Blocks / Re: Can't get it to run on Debian Buster missing libwx_gtk2u_richtext-2.8.so.0

« Last post by Commaster on June 24, 2022, 11:50:17 am »

20.03_i386_stable.tar.xz

Why i386? Is your Debian 32-bit and not 64-bit? Do you have 32-bit wxWidgets libraries installed?

15

Using Code::Blocks / Can't get it to run on Debian Buster missing libwx_gtk2u_richtext-2.8.so.0

« Last post by dfatcb on June 24, 2022, 08:31:59 am »

Hi,

I was using Debian Jessie with, I believe, Code::Blocks 17.12.  I upgraded to stretch then buster.  When done, Code::Blocks wouldn't run.  I then looked for updates and found the https://www.fosshub.com/Code-Blocks.html?dwl=codeblocks_20.03_i386_stable.tar.xz which is supposed to be made for Debian 10 (Buster).   

I extracted the file, change to that directory and ran sudo dpkg -i *.deb followed by sudo apt-get install -f (which didn't update or change anything - just ran it because instructions I found for install said to).    Anyway, once done the icon still wouldn't launch so I ran "codeblocks" from terminal and it says:

 codeblocks: error while loading shared libraries: libwx_gtk2u_richtext-2.8.so.0: cannot open shared object file: No such file or directory

So I'm stuck, I can't see to find that file anywhere and the only package I found it listed was for SID.

What do I need to do for code::blocks to run on Debian Buster?

16

Plugins development / Re: LLDB debugger low level interface investigation results

« Last post by AndrewCot on June 24, 2022, 06:04:22 am »

Eran,

I have just successfully modified my local C::B for the following:a) Created a debugger_WXDAP.dll that is the dap dll and right now is in the same directory as the codeblocks.exe.
b) Created a new debugger plugin debugger_dap.dll that is wired in like the other debuggers (GDB and GDB/MI).
c) The changes worked enough and I have wired up enough so that when I run a program to debug it in the C::B GUI the connection through the debugger_WXDAP.dll works and I get debug output on the lldb-vscode.exe. I have only wired up the connection and the events only log to the debug log on the C:B gui.

There is still a huge amount of work to do and it will take a while to go from where I am to

If I find anything I will create issues and/or PR's against the github repo.

Thanks very much for your help and advice on the DAP and the DLL.

17

Using Code::Blocks / Re: How to add compiler information

« Last post by Miguel Gimenez on June 23, 2022, 10:05:51 am »

If you add __WINDOWS_DS__ to the project, it will be defined in every compilation command.
If you define it in a file, it will be defined only during current compilation command.

Read about preprocessing elsewhere, this is OT here.

18

Using Code::Blocks / Re: How to add compiler information

« Last post by Psyclone on June 23, 2022, 02:13:26 am »

Thanks so much.

One more question, I'm guessing this is how it works...

if I write a #defines  __WINDOWS_DS__  at the top of a file it will add the following code to the file. 

The "#if defined" below is asking if I wrote the "#defines" above? Thanks again for you help.

CODE....
#if defined(__WINDOWS_DS__) // Windows DirectSound API

// Modified by Robin Davies, October 2005
// - Improvements to DirectX pointer chasing.
// - Bug fix for non-power-of-two Asio granularity used by Edirol PCR-A30.
// - Auto-call CoInitialize for DSOUND and ASIO platforms.
// Various revisions for RtAudio 4.0 by Gary Scavone, April 2007
// Changed device query structure for RtAudio 4.0.7, January 2010

#include <windows.h>
#include <process.h>
#include <mmsystem.h>
#include <mmreg.h>
#include <dsound.h>
#include <assert.h>
#include <algorithm>

#if defined(__MINGW32__)
  // missing from latest mingw winapi
#define WAVE_FORMAT_96M08 0x00010000 /* 96 kHz, Mono, 8-bit */
#define WAVE_FORMAT_96S08 0x00020000 /* 96 kHz, Stereo, 8-bit */
#define WAVE_FORMAT_96M16 0x00040000 /* 96 kHz, Mono, 16-bit */
#define WAVE_FORMAT_96S16 0x00080000 /* 96 kHz, Stereo, 16-bit */
#endif

#define MINIMUM_DEVICE_BUFFER_SIZE 32768

19

Using Code::Blocks / Re: How to add compiler information

« Last post by BlueHazzard on June 23, 2022, 01:29:35 am »

you have
precompiler defines:

Code

-D__WINDOWS_DS__

compiler flags:

Code

-Wall

and linker libraries

Code

-lole32 -lwinmm -ldsound

Pre compiler commands:
Project->Build options->Select the project name on the left->compiler settings->#defines
add "__WINDOWS_DS__" without the -D

Compiler commands:
Project->Build options->Select the project name on the left->compiler settings->compiler flags
search for Wall in the list
or
Project->Build options->Select the project name on the left->compiler settings->other compiler flags
add "-Wall"

Linker libraries
Project->Build options->Select the project name on the left->Linker settings->link libraries
press the "Add" button at the bottom and enter the libraries without "-l" so for your example

Code

ole32
winmm
dsound

for each library you have to press the add button

if you have a problem: https://wiki.codeblocks.org/index.php?title=FAQ-Compiling_(general)#Q:_How_do_I_report_a_compilation_problem_on_the_forums.3F

hope this helped

20

Using Code::Blocks / How to add compiler information

« Last post by Psyclone on June 22, 2022, 10:09:58 pm »

Greetings, I have successfully compiled a program at the command but would like to compile it in code blocks. The following is the command line I used...

g++ -Wall -D__WINDOWS_DS__ -o audioprobe audioprobe.cpp RtAudio.cpp -lole32 -lwinmm -ldsound

Where do I enter this information in codeblocks to get the project to compile?

Thanks in advance, sorry if its an obvious or nonsensical question.