Strange CONFIG file error message with Proffie 6.7

ProffieOS
1

Hello there! I’m new here, but I’ve been programming sabers with Proffie for a while now.

So, I have a proffie saber that was running on 5.9, and when I heard about the cool options in 6.0, I thought I’d try to upgrade my saber. So I downloaded 6.7, put in my CONFIG file, and went into Arduino, opened Proffie 6.7, and clicked Verify. Now, I put the config file location in the code, so I don’t understand the error messages I’m getting:

Arduino: 1.8.19 (Windows 10), Board: "Proffieboard V2, Serial + Mass Storage + WebUSB, SDCARD (SPI), 80 MHz, Smallest Code"

ProffieOS:51:2: error: #error Please set CONFIG_FILE as shown above.

   51 | #error Please set CONFIG_FILE as shown above.

      |  ^~~~~

ProffieOS:55:10: error: #include expects "FILENAME" or <FILENAME>

   55 | #include CONFIG_FILE

      |          ^~~~~~~~~~~

ProffieOS:218:10: fatal error: common/common.h: No such file or directory

  218 | #include "common/common.h"

      |          ^~~~~~~~~~~~~~~~~

compilation terminated.

exit status 1

#error Please set CONFIG_FILE as shown above.

If anyone has an idea of what I did wrong, I would really appreciate it.

2

Do this in ProffieOS.ino, it means you didn’t set you config in Arduino before trying to upload.

3

I swear I did that. This is what the ProffieOS.ino code says:

// #define CONFIG_FILE "config/CONFIG.h"

CONFIG.h is my config file for all my saber fonts. It worked just fine in versions before 6.0

4

you have to remove the // in front

1 Like
5 
/*---------------------- ProffieOS:6.x ----------------------------*\
|  You can have multiple configuration files, and specify which one |
|  to use here by removing the two slashes at the beginning.        |
|  **NOTE** Only ONE line should be left uncommented at a time!     |
|  Add the slashes to any that you are not using.                   |
\*-----------------------------------------------------------------*/


// #define CONFIG_FILE "config/YOUR_CONFIG_FILE_NAME_HERE.h"
6

hey man were you able to solve it i have the same issue

7

no it still game me the same issue.