Skip to content

Latest commit

 

History

History
166 lines (118 loc) · 5.74 KB

DEVELOPERS.md

File metadata and controls

166 lines (118 loc) · 5.74 KB

DEVELOPERS

Getting started

This document will help you setup your development environment.

Prerequisites

Before contributing, ensure you have the following tools installed on your development machine:

  • GCC (or another compatible C/C++ compiler)
  • Make
  • Git
  • Valgrind (optional, for memory debugging and profiling)
  • VSCode (or other debugger)

Building the Project

  1. Clone the repository:

    git clone https://github.com/ravachol/kew.git
cd kew

  2. To enable debugging symbols, replace -O2 with -g in the COMMONFLAGS variable, and remove the -s (strip) flag from the LDFLAGS variable in the Makefile:

  3. Build the project:

    make -j$(nproc)  # Use all available processor cores for faster builds

Debugging with Visual Studio Code

To enable debugging in VSCode, you'll need to create a launch.json file that configures the debugger. Follow these steps:

  1. Open your project's folder in VSCode.

  2. Press F5 or go to the "Run and Debug" sidebar (Ctrl+Shift+D on Windows/Linux, Cmd+Shift+D on macOS), then click on the gear icon to create a new launch configuration file.

  3. Select "C++ (GDB/LLDB)" as the debugger type, and choose your platform (e.g., x64-linux, x86-win32, etc.).

  4. Replace the contents of the generated launch.json file with the following, adjusting paths and arguments as needed:

    {
 "version": "0.2.0",
 "configurations": [


     {
         "name": "kew",
         "type": "cppdbg",
         "request": "launch",
         "program": "${workspaceFolder}/kew",
     //"args": ["artist or song name"],
         "stopAtEntry": false,
         "cwd": "${workspaceFolder}",
         "environment": [],
         "externalConsole": true,
         "MIMode": "gdb",
         "setupCommands": [
             {
                 "description": "Enable pretty-printing for gdb",
                 "text": "-enable-pretty-printing",
                 "ignoreFailures": true
             }
         ]
     }
 ]
}

  5. Save the launch.json file.

  6. Create a c_cpp_properties.json file in the same folder (.vscode) with the following contents adjusting paths and arguments as needed:

    {
"configurations": [
    {
        "name": "linux-gcc-x64",
        "includePath": [
            "${workspaceFolder}/**",
            "/usr/include",
            "/usr/include/opus",
            "/usr/include/vorbis",
            "/usr/include/chafa/",
            "/usr/include/glib-2.0/**",
            "/usr/lib/chafa/include/**",
            "/usr/lib/glib-2.0/include/**"
        ],
        "defines": [
            "_POSIX_C_SOURCE=200809L"
        ],
        "compilerPath": "/usr/bin/gcc",
        "cStandard": "${default}",
        "cppStandard": "${default}",
        "intelliSenseMode": "linux-gcc-x64"
    }
],
"version": 4
}

  7. Add the extensions C/C++, C/C++ Extension pack, C/C++ Themes (optional).

  8. Now you can use VSCode's debugger to step through your code, inspect variables, and analyze any issues:

     * Set breakpoints in your source code by placing your cursor on the desired line number, then press `F9`.
 * Press `F5` or click on the "Start Debugging" button (or go to the "Run and Debug" sidebar) to start the debugger.
 * When the execution reaches a breakpoint, VSCode will pause, allowing you to use its built-in features for debugging.

Finding where libs are located

If the paths in c_cpp_properties.json are wrong for your OS, to find the folder where for instance Chafa library is installed, you can use one of the following methods:

  1. Using pkg-config:

    The pkg-config tool is a helper tool used to determine compiler flags and linker flags for libraries. You can use it to find the location of Chafa's include directory. Open your terminal and run the following command:

    pkg-config --cflags chafa

    This should display the -I flags required to include Chafa's headers, which in turn will reveal the installation prefix (e.g., /usr/include/chafa/). The folder containing the library files itself is typically located under lib or lib64, so you can find it by looking for a folder named chafa within those directories.

  2. Using brew (for macOS):

    If you installed Chafa using Homebrew, you can find its installation prefix with the following command:

    brew --prefix chafa

    This will display the installation prefix for Chafa (e.g., /usr/local/opt/chafa).

  3. Manually searching:

    Alternatively, you can search your file system manually for the chafa folder or library files. On Unix-based systems like Linux and macOS, libraries are typically installed under /usr, /usr/local, or within the user's home directory (e.g., ~/.local). You can use the find command to search for the folder:

    find /usr /usr/local ~/.local -name chafa

    This should display the location of the Chafa installation, revealing both the include and library folders.

Valgrind

To use Valgrind for memory debugging and profiling:

  1. Build your project with debug symbols (-g) and position-independent executables (-no-pie):

  2. Run Valgrind on your binary:

    valgrind --leak-check=full --track-origins=yes --show-leak-kinds=all --log-file=valgrind-out.txt ./kew

Editorconfig

  • If you can, use EditorConfig for VS Code Extension. There is a file with settings for it: .editorconfig.

Contributing

For further information on how to contribute, see the file CONTRIBUTING.md.