kernel.h issues

[gbowne1]

In my VSCode editor session, looking at the kernel.c file

I am getting this error(s):

Line #5: 'tty.h' file not found [Lexical or Preprocessor Issue] Clang (c-cpp-flylint)

Line #14 puts("kernel_main()\n", term); the word term has red squiggles and says gives the error:
uint16_t *term too many arguments in function call C/C++(140)

Line #27 'puts("enabling paging...\n", term);gives the error:uint16_t *term too many arguments in function call C/C++(140)

I am assuming the Linux configuration for C/C++ and Clang VSCode linter and extension(s) needs to be fixed for this but that may not be the extent of the issues with kernel.c

As I do not use Windows much, I don't know what this configuration would be like for Mac and subsequently Mac.

@EmptyGroceryBag

[gbowne1]

edit: I believe I have solved most of this issue(s) tonight. I will issue a fix here soon especially for those using VSCode.

The VSCode settings as they exist need quite a bit of work so I actually made fixes to the C/C++ extension settings so it turns off all but Clang.

The only other issue I am having is that it keeps calling .c and .h files G-Code (I have the G-Code extension) i.e: vscode-gcode.gcode in the language mode setting in the blue status bar below the editor. So I keep having to switch the language mode for the .c and .h files. I have not found a good way to fix this.

I have been wanting to make a generic global (userland) settings.json (non-Workspace) for those who do not or have not configured their VSCode properly especially for things like C, Assembly, C++, WebDev (HTML, CSS, JS, etc.) . [TODO]

I have not worked on the documented ./build.sh gcc command to see if that has any issues yet.

[gbowne1]

This TODO issue is slresdy complete with the last PR. It cleans up 80% of the current issues.