Skip to content

Instantly share code, notes, and snippets.

View enetheru's full-sized avatar

Samuel Nicholas enetheru

View GitHub Profile
___ _ _ ___ _ _ _ ___ _
/ __| |___ __ _ _ _ ___ __| | | _ )_ _(_) |__| | / __|___ _ __ _ __ __ _ _ _ __| |___
| (__| / -_) _` | ' \/ -_) _` | | _ \ || | | / _` | | (__/ _ \ ' \| ' \/ _` | ' \/ _` (_-<
\___|_\___\__,_|_||_\___\__,_| |___/\_,_|_|_\__,_| \___\___/_|_|_|_|_|_\__,_|_||_\__,_/__/
[ godot-cpp\w64.scons.msys2-ucrt64.template_release\test\compile_commands.json ]
-- Config: w64 scons msys2-ucrt64 template_release
-- Compile
* Output
- -o src\godot.windows.template_release.x86_64.o
@enetheru
enetheru / godot-cpp.docs.txt
Created March 4, 2025 03:49
godot-cpp documentation idea
I was reformatting my cmake comments, and updating the doc/cmake.rst and I had this
idea but I dont know how feesible it is.
What if.. We create and maintain documentation for godot-cpp in doc/...
In exactly the format of the main godot docs, such that it could be copied over.
Stuff that is only available in godot-cpp like specialised macros, snippets, examples
deprecated warnings, and compatibility duplication stuff.
And have select portions of that synchronised to the official documentation repo