tmk usb_usb how to #define?

[tokyo]

I am newbie to C programming.
I read about various #defines for example:
tmk_core/doc/build.md

I am compiling under tmk_keyboard-master/converter/usb_usb/
But am not sure where to put those.
For example:
Makefile
config.h
keymap.c

I put them in keymap.c and it does not seem to work.

Code: [Select]

#include "keymap_common.h"
#include "action_layer.h"  //for layer_on functions

//disable debug since I have no idea how to debug my usb2usb
#define CONSOLE_ENABLE = no
#define COMMAND_ENABLE = no
#define NO_DEBUG
#define NO_PRINT
#define SLEEP_LED_ENABLE = yes
//maybe these need to be commented out somewhere? instead of define to no

//todo: mimic a generic one, google didn't get one
#define VENDOR_ID       0xFEED
#define PRODUCT_ID      0x005B
#define DEVICE_VER      0x0814
#define MANUFACTURER    Dell
#define PRODUCT         USB keyboard
#define DESCRIPTION     USB keyboard


#define TAPPING_TERM    300   
#define TAPPING_TOGGLE 5

#define ONESHOT_TIMEOUT 400

const uint8_t keymaps[][MATRIX_ROWS][MATRIX_COLS] PROGMEM = {
    /* 0: plain Qwerty without layer switching


[suicidal_orange]

Makefile is used to tell the compiler how to compile the firmware so it shouldn't be mentioned in any file, while a #define is used to store a value with a meaningful name for use later - either you're very confused or I'm reading this completely wrong, both are equally likely )

What are you trying to do and what error are you getting when you do it?

[tokyo]

I am trying to place "#define" properly but not sure the correct way.
  for example: before the "#include"?
     in make file?
I am new to C programming and TMK.

Hope that clears up confusion.

[suicidal_orange]

The answer to your question is #define goes in .c and .h files, not make makefiles.  You have to #define the NAME before you can refer to it to get the VALUE so they are often right at the top of the code but don't have to be.  The format is:

Code: [Select]

#define NAME VALUE
Includes are the same - you can't refer to something in the included file until after the #include line, so they too are usually at the top (but don't have to be). 

If in doubt put them all at the top, the order doesn't much matter.

Does that help?

[tokyo]

Thanks for help!

I wonder if "#define" should be put in config.h or keymap.c 
before or after "#include"

[Darkshado]

See where the defines are used and go from there... Instinctively I'd say pretty high in the config.h file, but I haven't looked at the TMK code yet.

[tokyo]

about undef
#undef CONSOLE_ENABLE
#undef COMMAND_ENABLE
#undef SLEEP_LED_ENABLE

Hasu said it might work in the config.h, it does not.

[hasu]

about undef
#undef CONSOLE_ENABLE
#undef COMMAND_ENABLE
#undef SLEEP_LED_ENABLE

Hasu said it might work in the config.h, it does not.

Because those macros are  not used in source code You are confused with Makefile(build script) and config.h(code).