mirror/oot

mirror of https://github.com/zeldaret/oot.git synced 2024-12-25 22:26:12 +00:00

Introduce extracted/VERSION, with text extracted there (#1730 )

* Introduce assets/_extracted/VERSION, with text extracted there

* move to `extracted/text/`

* Update gitignore s

* rework args for msgenc.py

* put mkdir with others, until theyre all moved at once

* move 0xFFFC back to being extracted, making it use specific macro `DEFINE_MESSAGE_NES` to handle its special behavior

* prettier gitignore

* Move messages 0xFFFC, 0xFFFD to committed message_data.h

2024-03-01 22:09:57 -05:00

3.1 KiB

Raw Blame History

VSCode

A lot of people on this project use VSCode as their coding environment.

Extensions

There are a number of useful extensions available to make work more efficient:

C/C++ IntelliSense
Clang-Format
HexInspector (hover on numbers for float and other info)
NumberMonger (convert hex to decimal and vice versa)
Better MIPS Support

Useful keyboard shortcuts

Ctrl + Alt + Up/Down (on Windows, on Linux it's Ctrl + Shift + Up/Down or Shift + Alt + Up/Down) gives multicursors across consecutive lines. If you want several cursors in a more diverse arrangement, middle clicking works, at least on Windows.
Alt + Up/Down moves lines up/down.
Shift + Alt + Up/Down (Linux: Ctrl + Shift + Alt + Up/Down) copies lines up/down.
Ctrl + P offers a box to use to search for and open files.
Ctrl + Shift + P offers a box for commands like editing settings or reloading the window.
Make use of VSCode's search/search-and-replace features.
- Ctrl + Click goes to a definition.
- Ctrl + F for search in current file
- Ctrl + H for replace in current file
- Ctrl + Shift + F for search in all files
- Ctrl + Shift + H for replace in all files
- F2 for Rename symbol

Many of VS Code's other shortcuts can be found on its getting started page, which also has links to OS-specific PDFs.

C/C++ configuration

You can create a .vscode/c_cpp_properties.json file with C/C++: Edit Configurations (JSON) in the command box to customise how IntelliSense reads the repository (stuff like where to look for includes, flags, compiler defines, etc.) to make VSCode's IntelliSense plugin better able to understand the structure of the repository. This is a good default one to use for this project's repository:

{
    "configurations": [
        {
            "name": "N64 oot-gc-eu-mq-dbg",
            "compilerPath": "${default}", // Needs to not be "" for -m32 to work
            "compilerArgs": [
                "-m32" // Removes integer truncation warnings with gbi macros
            ],
            "intelliSenseMode": "${default}", // Shouldn't matter
            "includePath": [ // Matches makefile's includes
                "include",
                "include/libc",
                "src",
                "build/gc-eu-mq-dbg",
                ".",
                "extracted/gc-eu-mq-dbg"
            ],
            "defines": [
                "_LANGUAGE_C", // For gbi.h
                "OOT_DEBUG=1" // If targeting a debug version
            ],
            "cStandard": "gnu89", // C89 + some GNU extensions from C99 like C++ comments
            "cppStandard": "${default}" // Only ZAPD uses C++, so doesn't really matter
        }
    ],
    "version": 4
}

Settings

Add the following to (or create) the .vscode/settings.json file for VSCode to search the gitignored asset files by default:

{
    "search.useIgnoreFiles": false,
    "search.exclude": {
        "**/.git": true,
        "baseroms/**": true,
        "build/**": true,
        "expected/**": true,
    },
}

3.1 KiB Raw Blame History