List of preprocessor definitions

[dhealey]

Is there a list of all the JUCE_ extra pre-processor definitions and their purpose?

[daniel]

It can be found in the module headers per module.
You can recognise them because the comment starts with Config:. This is the magic word for Projucer to show it as configurable option, e.g. here:

juce-framework/JUCE/blob/master/modules/juce_core/juce_core.h#L79

A curated list over all modules would be helpful, since it’s not always clear where to look for them. But that’s something the JUCE team usually avoids. A little stretch of the DRY argument

[chkn]

Here is a method to can generate a list (but without explanations)

Projucer Macro Overview

Here is shell one-liner to find all JUCE_ Macros find . -type f \( -name "*.h*" -o -name "*.cpp" -o -name "*.mm" \) -exec grep -o -E '\w+' {} \; | grep '^JUCE_' | sort -u -f And this is the output: (without _INCLUDED Macros ) JUCE_ JUCE_32BIT JUCE_64BIT JUCE_64BIT_ATOMICS_UNAVAILABLE JUCE_AAX_LIB JUCE_AAX_LIB_PATH JUCE_AAX_LIB_SUFFIX JUCE_ALIGN JUCE_ALLOW_STATIC_NULL_VARIABLES JUCE_ALSA JUCE_ALSA_FAILED JUCE_ALSA_LOG JUCE_ALSA_LOGGING JUCE_ALSA_MIDI_INPUT_NAME JUCE_ALSA_MIDI_OUTPUT…

[daniel]

I just checked the doxygen docs. If there was a way to exclude filenames from the search, then searching for “JUCE_” could help a lot. Sadly the filenames follow the same naming convention, so it’s hard to spot the macro you are looking for.

Maybe SHOW_FILES=NO would do the trick?

EDIT: I just tried that locally, it removes clutter, but most config options are not included in the doxygen search.

[Mrugalla]

i would like to support this as a feature request to JUCE’ documentation. it’s already pretty good with all that doxygen stuff. but there should be even more. an extra page that has a sub page only for this, a list of all preprocessordefines and their main usecases as example. also a list of all component types with little screenshots or gifs or videos (yeah probably videos!) to explain their function