Getting debug output to the compiler console..

[Lindon]

@d-healey -- and "Main" is where in HISE?

[d.healey]

My guess is mainController.cpp is doing the same thing that main usually does.

[Lindon]

@d-healey - yep that was my guess too so I put this in there:

/** The entire HISE codebase


*/
namespace hise { using namespace juce;

#if HI_RUN_UNIT_TESTS
bool MainController::unitTestMode = false;
#endif

DBG("in here at the start");

MainController::MainController() :

	sampleManager(new SampleManager(this)),
	javascriptThreadPool(new JavascriptThreadPool(this)),
	expansionHandler(this),
	allNotesOffFlag(false),
	maxBufferSize(-1),
	cpuBufferSize(0),
...
...
...

Compiled a release version and ran it -----

nothing showed up in the output window, so - its looking like a. (I dont know what I'm doing, not surprising...)

Where does DBG send statements to?

more research shows this:

DBG( "message" );
messages only show up in the output window in your IDE in debug builds, not release builds.
If you want to know how it works, right click on it, “Go to definition” and look at the source code. it’s just a macro.

use breakpoints. Xcode and Visual Studio have great support for breakpoints and debugging.

[d.healey]

@Lindon

Where does DBG send statements to?

I work in the terminal so that's where I see the output. Someone else was asking me about debugging in VS a while ago, I suggested they search YouTube and find some proper instructions for debugging - I'll be doing this too when I do my next Windows build - they seemed to find it helpful.

[Lindon]

@d-healey well I built another debug image - and still nothing is showing up... so youTube might be my next port of call...

• is this any easier in MacOS?

[d.healey]

@Lindon I'm a GNU/Linux guy :) You can debug on Windows and MacOS using the terminal though. Make a debug build and run it from the terminal.

[Christoph Hart]

The DBG call must be inside a function body and is only available in Debug builds (hence the name). In your example you‘ve put it into global namespace which is basically a vacuum in C++.

[Lindon]

@Christoph-Hart - yep I worked that out so I put it in the function...still I'm not seeing any output....:-(

[Bob Stuck]

@Christoph-Hart Sent you a message.

[Orvillain]

Hey apologies for the bump. But I got this to work by putting:
JUCE_LOG_ASSERTIONS=1

into the preprocessor definitions and then rebuilding. I get data from my custom c++ node printing to the visual studio log:

It wasn't working until I did that.