Usage: make [config=name] [target]
To be honesty, i really don't know what's the different or detail about the combination of config and target. Are there some doc talk about it?
The config options have been mentioned many times on those forum and are described in the README file.
The targets are:
orx: orx's launcher, usually not used anymore as stand alones are now easier to create than launcher + plugin
orxLIB: orx itself
Bounce: my playground where I test & develop all the features for orx
Scroll: another test that I don't really maintain and will probably remove at some point. Not to be confused with the separate C++ thin layer of the same name.
If the core(orx itself) are build with embedded_dynamic_debug64 then the tutorial can't be build as release64, i don't know the combination about orx core and the app(android/ios/linux tutorial or demo).
There's nothing complex, if you use a debug version of orx, you should define __orxDEBUG__ (which is defined in the debug version of the tutorials).
Debug goes with debug, release with release, it's rather a no-brainer.
As for learning, I'd recommend the tutorials, the official ones as well as the community ones, all available on the wiki.
That used to be the first way of using orx and remained easier than stand alones for quite a while but it's not the case anymore.
All tutorial used to be written that way too but I changed that last year in favor of the stand alone approach.