🍩 A XMake integration in Visual Studio Code

Overview

xmake-vscode

A XMake integration in Visual Studio Code

Introduction

A XMake integration in Visual Studio Code.

You need install xmake first and a project with xmake.lua.

Please see xmake-github and website if you want to known more about xmake.

Features

  • Quickstart
  • Colorization
  • Completion Lists
  • StatusBar
  • Commands
  • Configuration
  • Build
  • Run and Debug
  • Record and Playback
  • Problem

Quickstart

Colorization and Completion Lists

StatusBar

statusbar

Commands

Configuration

Build

Run and Debug

Record and Playback

Problem

IntelliSense

xmake-vscode will generate .vscode/compile_commands.json file, so you need only add it to .vscode/c_cpp_properties.json to enable IntelliSense.

for example (.vscode/c_cpp_properties.json):

  "configurations": [
    {
      "compileCommands": ".vscode/compile_commands.json",
    }
  ],
}

How can I generate c_cpp_properties.json?

These configuration settings are stored in your project's c_cpp_properties.json file. To edit this file, in VS Code, select C/C++: Edit Configurations (UI) from the Command Palette (⇧⌘P):

Please see IntelliSense for cross-compiling

Global Configuration

{
    "configuration": {
        "type": "object",
        "title": "XMake configuration",
        "properties": {
            "xmake.executable": {
                "type": "string",
                "default": "xmake",
                "description": "The xmake executable name / path"
            },
            "xmake.logLevel": {
                "type": "string",
                "default": "normal",
                "description": "The Log Level: normal/verbose/minimal",
                "enum": [
                    "verbose",
                    "normal",
                    "minimal"
                ]
            },
            "xmake.buildLevel": {
                "type": "string",
                "default": "normal",
                "description": "The Build Output Level: normal/verbose/warning/debug",
                "enum": [
                    "verbose",
                    "normal",
                    "warning",
                    "debug"
                ]
            },
            "xmake.buildDirectory": {
                "type": "string",
                "default": "${workspaceRoot}/build",
                "description": "The Build Output Directory"
            },
            "xmake.installDirectory": {
                "type": "string",
                "default": "",
                "description": "The Install Output Directory"
            },
            "xmake.packageDirectory": {
                "type": "string",
                "default": "",
                "description": "The Package Output Directory"
            },
            "xmake.workingDirectory": {
                "type": "string",
                "default": "${workspaceRoot}",
                "description": "The Project Working Directory with the root xmake.lua"
            },
            "xmake.androidNDKDirectory": {
                "type": "string",
                "default": "",
                "description": "The Android NDK Directory"
            }
        }
    }
}
Comments
  • Cannot debug when using liburing

    Cannot debug when using liburing

    Xmake 版本

    2.7.1

    操作系统版本和架构

    Ubuntu 22.04 on Win10 WSL

    描述问题

    xmake.lua

    add_rules("mode.debug", "mode.release")
    set_languages("c++17")
    set_toolchains("clang")
    set_warnings("all")
    
    add_requires("liburing")
    add_packages("liburing")
    
    target("demo")
      set_kind("binary")
      add_files("src/main.cpp")
    

    main.cpp

    #include <iostream>
    int main() {
        std::cout << "1234\n";
    }
    

    可以运行,可以命令行调试(xmake run -d),但是不能在vscode里调试(即点击状态栏调试按钮或按F5)

    .../demo/build/linux/x86_64/debug/demo: error while loading shared libraries: liburing.so.2: cannot open shared object file: No such file or directory
    

    相关:

    $ ls ~/.xmake/packages/l/liburing/2.1/2e6104ac1acb47ddb318f33dd2d128ee/lib
    liburing.a  liburing.so  liburing.so.2  liburing.so.2.1.0  pkgconfig
    

    settings.json

    "xmake.customDebugConfig": {
            "type": "lldb",
            "request": "launch",
            "name": "Debug",
        }
    

    期待的结果

    可以调试

    工程配置

    No response

    附加信息和错误日志

    No response

    bug 
    opened by fonqL 26
  • Windows: debugger not found on MinGW

    Windows: debugger not found on MinGW

    Describe the bug

    When attempting to debug a program using the xmake Debug button in the VS Code extension, we get an error message popup.

    Error output

    Unable to start debugging. Launch options string provided by the project system is invalid. Unable to determine path to debugger. Please specify the “MIDebuggerPath” option.

    Info

    The line that is causing the issue is:

    https://github.com/xmake-io/xmake-vscode/blob/master/src/debugger.ts#L116

    Putting the full path to gdb.exe in that field, eg:

    miDebuggerPath: "C:/dev/msys64/mingw64/bin/gdb.exe",

    ... fixes it.

    I do not know at this stage how to get the MinGW root from xmake in this extension so that we can append /bin/gdb.exe to it.


    • xmake vscode version: 1.4.3
    • os: Win10
    • target platform: MinGW
    enhancement 
    opened by paul-reilly 19
  • 无法调试

    无法调试

    test.cpp

    #include <iostream>
    
    int main()
    {
        std::cout << "Hello, world!" << std::endl;
        return 0;
    }
    

    用工具栏操作,点击编译和运行都可以,但是点击调试不行(无限等待),截图: 2020-05-19_23-14

    Version Info

    • XMake (vscode plugin): 1.3.4
    • VSCodium (variant of vscode): 1.45.1
    • OS: Manjaro
    opened by playgithub 19
  • 无法在vscode server中使用

    无法在vscode server中使用

    你在什么场景下需要该功能?

    我在服务器上部署了vscode web,并安装了xmake插件,但是该插件不能够正常使用,希望能够增加对vscode web的适应性。

    • ubuntu18.04
    • vscode server 在ubuntu上部署vscode server可以参考该网址,直接下载对应deb包即可完成安装。可通过修改~/.config/code-server/config.yaml绑定相应的ip地址与port。
    opened by wangzhankun 17
  • UpdateIntellisense 命令生成的 compile_commands 没有包含 rule:on_config add includedirs 信息

    UpdateIntellisense 命令生成的 compile_commands 没有包含 rule:on_config add includedirs 信息

    Xmake 版本

    v2.6.9+HEAD.22ecc01

    操作系统版本和架构

    Linux: 5.15.24-amd64-desktop

    描述问题

    如题 而使用 xmake project -k compile_commands 命令则没有这个问题

    期待的结果

    UpdateIntellisense 也能正常处理 rule:on_config add includedirs 依赖

    工程配置

    No response

    附加信息和错误日志

    No response

    bug 
    opened by OuYangPaste 15
  • 关于按F5开启调试的一个提议

    关于按F5开启调试的一个提议

    主要是大部分从win平台过来的都习惯了F5,个人觉得最好能够把F5自动开启xmake run -d这个效果,类似nodejs的npm start。

    然后我去看了一下关于launch.json的配置以及说明,感觉应该是可以对type这个字段下手, 我是参考了这里的,他里面type就是用了node,我感觉应该跟xmake调试启动接口类似,但是我接下来不是太明白这个地方type到底能不能自定义修改,可能需要跟vscode的插件实现有关系了吧?

    不知道这个思路是不是已经有考虑过?我回头也会继续看看怎么搞。

    opened by littlewater 14
  • 关于Qt 模板

    关于Qt 模板

    Xmake 能增加 一些Qt模板吗? 比如 xmake create add -t qt_DialogWithButtonsBottom AboutUsDialog 创建添加一个Dialog在当前项目下 模板包括 Dialog with Buttons Bottom Dialog wiht Buttons Right Dialog without Buttons Main Window Widget

    模板文件可以参考 Qt Creator 默认生成的文件

    feature request 
    opened by qiu-hao 14
  • Debug refactor

    Debug refactor

    This PR refactor the debugging part of this extension. It adds an xmake debug type configuration, so you can have a configuration like this:

    {
        "configurations": [
        {
           "name": "XMake Debug",
            "type": "xmake",
            "request": "launch",
            "target": "example",
            "args":["-args"],
            "stopAtEntry": true
        }
      ]
    }
    

    Changelog

    • Add new debugger type, document it in the README.
    • Remove runAll in explorer, because it was not working with the previous versions, and I didn't manage to get it works with the new debug configuration (maybe I'll get it to work in a future contribution).

    Config changes

    • Remove runningTargetsArguments, debuggingTargetsArguments and customDebugConfig
    • Rename debugConfigType to debuggerBackend
    • Add envBehaviour config to manage environment between launch.json and xmake.
    opened by A2va 12
  •  vscode1.6.0版本xmake插件失效

    vscode1.6.0版本xmake插件失效

    Xmake 版本

    2.6.3

    操作系统版本和架构

    Windows11 WSL2

    描述问题

    vscode在升级至最新的1.66.0版本后,xmake插件失效。未显示任何消息,但是xmake插件的按钮不再显示。

    期待的结果

    xmake-vscode兼容1.66.0版本

    工程配置

    No response

    附加信息和错误日志

    No response

    bug 
    opened by wangzhankun 10
  • 插件自动生成的compile_commands.json没有包含QT相关的头文件路径

    插件自动生成的compile_commands.json没有包含QT相关的头文件路径

    !!! 注:提问题时若使用不能用/没效果/有问题/报错此类模糊表达,但又没有根据下面的模板给出任何相关辅助信息的,将会直接标记为 Invalid。

    描述问题

    插件自动生成的compile_commands.json没有包含QT相关的头文件路径

    {
      "directory": "D:\\workspace\\xmake",
      "arguments": ["C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.27.29110\\bin\\HostX64\\x64\\cl.exe", "/c", "/EHsc", "/nologo", 
    "/ID:\\workspace\\xmake\\build\\.gens\\xmake\\windows\\x64\\debug\\rules\\qt\\ui", 
    "/Fobuild\\.objs\\xmake\\windows\\x64\\debug\\src\\main.cpp.obj", "src\\main.cpp"],
      "file": "src\\main.cpp"
    },
    

    期待的结果

    使用命令xmake project -k compile_commands生成的compile_commands.json包含了Qt的头文件路径

    {
      "directory": "D:\\workspace\\xmake",
      "arguments": ["C:\\Program Files (x86)\\Microsoft Visual 
    Studio\\2019\\Enterprise\\VC\\Tools\\MSVC\\14.27.29110\\bin\\HostX64\\x64\\cl.exe", "/c", "/EHsc", "/nologo", "/Zi", "/FS", 
    "/Fdbuild\\windows\\x64\\debug\\compile.xmake.pdb", "/Od", 
    "/ID:\\workspace\\xmake\\build\\.gens\\xmake\\windows\\x64\\debug\\rules\\qt\\ui", "/DQT_QML_DEBUG", 
    "/DQT_DEPRECATED_WARNINGS", "/DQT_CONCURRENT_LIB", "/DQT_GUI_LIB", "/DQT_WIDGETS_LIB", "/DQT_CORE_LIB", 
    "/D_WINDOWS", "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtConcurrent", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtGui", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtGui\\5.12.11", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtGui\\5.12.11\\QtGui", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtWidgets", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtWidgets\\5.12.11", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtWidgets\\5.12.11\\QtWidgets", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtCore", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtCore\\5.12.11", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include\\QtCore\\5.12.11\\QtCore", 
    "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\include", "/IC:\\Programming\\Qt\\5.12.11\\msvc2017_64\\mkspecs\\win32-
    msvc", "/Fobuild\\.objs\\xmake\\windows\\x64\\debug\\src\\main.cpp.obj", "src\\main.cpp"],
      "file": "src\\main.cpp"
    },
    

    错误信息

    相关环境

    请提供编译和运行环境信息,下面是一些必须填写的基础信息,便于我们针对性排查问题:

    • xmake版本:xmake v2.5.7+202108290043, A cross-platform build utility based on Lua
    • xmake运行平台:Windows 10
    • xmake目标平台:Windows 10

    其他信息

    请提供关键的 xmake.lua 配置内容,或者完整 xmake.lua,也可以是其他附加信息帮助我们诊断问题(比如截图,xmake.lua或者可复现的demo),以及你遇到的问题的一些背景信息。

    duplicate 
    opened by Vinx911 9
  • debug 时找不到 dll

    debug 时找不到 dll

    Xmake 版本

    v2.6.9+HEAD.22ecc0156

    操作系统版本和架构

    Windows 10 version 21H1

    描述问题

    用一个很简单的工程测试了一下插件的功能,这个工程只有一个源代码文件,引用了 xmake-repo 上的 libsdl 库。 用插件来运行程序可以运行,在代码里获取了一下环境变量,应该是插件把 SDL2 的 dll 所在的文件夹加入了 PATH。 但是用插件来调试程序就会报错,看了一下错误代码,应该是 dll 没找到。

    看了 xmake-vscode 的代码
    https://github.com/xmake-io/xmake-vscode/blob/4c27f99a2d20f2d5a3b4f80f37191892eb15ab46/src/debugger.ts#L158-L162 可能是因为没有像 xmake run 那样设置设置环境变量? 因为不知道怎么从 xmake 获取到所需要设置的环境变量,我也没有办法自己写 launch, 虽然直接去 package 里把 dll 给 copy 过来可以结果问题,但是总不能每个 package 都手动 copy 一个过来吧。

    希望作者大佬能指点一下

    期待的结果

    能够正常 debug 程序

    工程配置

    xmake.lua 文件如下

    set_xmakever("2.6.9")
    set_project("myapp")
    
    add_rules("mode.debug", "mode.release")
    
    add_requires("libsdl")
    
    target("app")
        set_kind("binary")
        add_files("src/**.cpp")
        add_headerfiles("src/**.h")
        add_packages("libsdl")
    

    唯一一个源代码文件 main.cpp,内容如下

    #include "SDL_events.h"
    #include "SDL_video.h"
    #include <SDL2/SDL.h>
    
    int main(int argc, char** argv) {
        SDL_Init(SDL_INIT_EVERYTHING);
    
        auto window = SDL_CreateWindow("app", 
            SDL_WINDOWPOS_CENTERED, 
            SDL_WINDOWPOS_CENTERED,
            1080,
            720,
            SDL_WINDOW_SHOWN);
    
        SDL_Event e;
        bool quit = false;
    
        while(!quit) {
            while(SDL_PollEvent(&e)) {
                if (e.type == SDL_QUIT) {
                    quit = true;
                    break;
                }
            }
        }
    
        SDL_DestroyWindow(window);
        SDL_Quit();
        return 0;
    }
    

    附加信息和错误日志

    vscode 调试控制台输出

    -------------------------------------------------------------------
    You may only use the C/C++ Extension for Visual Studio Code
    with Visual Studio Code, Visual Studio or Visual Studio for Mac
    software to help you develop and test your applications.
    -------------------------------------------------------------------
    Loaded 'D:\Projects\temp\vsxmake_test\build\windows\x64\debug\app.exe'. Symbols loaded.
    Loaded 'C:\Windows\System32\ntdll.dll'. 
    Loaded 'C:\Windows\System32\kernel32.dll'. 
    Loaded 'C:\Windows\System32\KernelBase.dll'. 
    The program '[13388] app.exe' has exited with code -1073741515 (0xc0000135).
    
    bug 
    opened by VirFunc 8
  • 将xmake包的头文件路径添加到intellisense的库路径中

    将xmake包的头文件路径添加到intellisense的库路径中

    你在什么场景下需要该功能?

    某个项目使用了xmake提供的c++依赖,在项目内浏览这个依赖的头文件时intellisense警告称该头文件不存在。

    描述可能的解决方案

    xmake 插件修改c_cpp_properties.json,添加对应xmake包的头文件。

    描述你认为的候选方案

    xmake.lua中列出xmake包的包含路径,生成相应的配置文件

    其他信息

    No response

    feature request 
    opened by jingkaimori 5
  • Allow

    Allow "xmake.customDebugConfig" to be configured by project rather than globally

    Is your feature request related to a problem? Please describe.

    Right now, it is possible to configure the debugger with the "xmake.customDebugConfig" in the settings.json. This is very usefull to, for example, pass some arguments to the program we're debugging. Right now, this feature seems available only through settings.json

    Describe the solution you'd like

    Make that configuration editable by project rather than through a global option. For example, generating a .vscode/launch.json and using it could be a great solution.

    Describe alternatives you've considered

    Right now, it is doable by creating a .vscode/settings.json file and customizing it.

    Additional context

    No response

    feature request 
    opened by Altyrost 2
  • Incorrect compile_commands generated for Qt framework projects

    Incorrect compile_commands generated for Qt framework projects

    Xmake Version

    2.6.9

    Operating System Version and Architecture

    5.17.15-1-Manjaro x86_64

    Describe Bug

    xmake correctly generates compile_commands.json files with xmake project -k compile_commands. The vscode plugin generates incorrect (for Linux) compile_commands files when using Qt frameworks. The files contain Darwin -framework directives.

    Working xmake compile_commands:

    [
    {
      "directory": "/home/dev/dev/sandpit/qtcc",
      "arguments": ["/usr/bin/gcc", "-c", "-m64", "-g", "-O0", "-std=c++11", "-I/home/dev/dev/sandpit/qtcc/build/.gens/qtcc/linux/x86_64/debug/rules/qt/ui", "-DQT_QML_DEBUG", "-DQT_DEPRECATED_WARNINGS", "-DQT_OPENGL_LIB", "-DQT_NETWORK_LIB", "-DQT_GUI_LIB", "-DQT_WIDGETS_LIB", "-DQT_CORE_LIB", "-I", "/usr/include/qt/QtOpenGL", "-I", "/usr/include/qt/QtOpenGL/5.15.5", "-I", "/usr/include/qt/QtOpenGL/5.15.5/QtOpenGL", "-I", "/usr/include/qt/QtNetwork", "-I", "/usr/include/qt/QtNetwork/5.15.5", "-I", "/usr/include/qt/QtNetwork/5.15.5/QtNetwork", "-I", "/usr/include/qt/QtGui", "-I", "/usr/include/qt/QtGui/5.15.5", "-I", "/usr/include/qt/QtGui/5.15.5/QtGui", "-I", "/usr/include/qt/QtWidgets", "-I", "/usr/include/qt/QtWidgets/5.15.5", "-I", "/usr/include/qt/QtWidgets/5.15.5/QtWidgets", "-I", "/usr/include/qt/QtCore", "-I", "/usr/include/qt/QtCore/5.15.5", "-I", "/usr/include/qt/QtCore/5.15.5/QtCore", "-I", "/usr/include/qt", "-I", "/usr/lib/qt/mkspecs/linux-g++", "-fPIC", "-o", "build/.objs/qtcc/linux/x86_64/debug/src/main.cpp.o", "src/main.cpp"],
      "file": "src/main.cpp"
    }]
    

    Not working xmake-vscode generated compile_commands:

    [
    {
      "directory": "/home/dev/dev/sandpit/qtcc",
      "arguments": ["/usr/bin/gcc", "-c", "-m64", "-I/home/dev/dev/sandpit/qtcc/build/.gens/qtcc/linux/x86_64/debug/rules/qt/ui", "-framework", "QtCore", "-framework", "QtWidgets", "-framework", "QtGui", "-framework", "QtOpenGL", "-framework", "QtNetwork", "-framework", "qtmultimedia5", "-o", "build/.objs/qtcc/linux/x86_64/debug/src/main.cpp.o", "src/main.cpp"],
      "file": "src/main.cpp"
    }]
    

    Expected Behavior

    The same files to be generated by the plugin as xmake. At least the same include directories, because that's what vscode mostly uses the files for.

    Project Configuration

    xmake.lua

    add_rules("mode.debug", "mode.release")
    
    target("qtcc")
        add_rules("qt.widgetapp")
        add_frameworks("QtCore", "QtWidgets", "QtGui", "QtOpenGL", "QtNetwork", "qtmultimedia5")
        add_files("src/*.cpp")
    

    Additional Information and Error Logs

    n/a

    bug 
    opened by paul-reilly 1
  • 当我的工程中有target类型是headeronly时xmake插件不起作用

    当我的工程中有target类型是headeronly时xmake插件不起作用

    Xmake 版本

    2.6.8

    操作系统版本和架构

    Windows 10 专业版 21H2

    描述问题

    只要配置文件中有target的类型是headeronly插件会崩掉,我跟了插件的代码发现是explorer.ts:222中代码

    if (target.files != null) {
        target.file.sort();
    } else {
        target.files = []
    }
    

    修改为

    const filekeys = Object.keys(target.files);
    if (target.files != null && filekeys.length != 0) {
        target.files.sort();
    } else {
        target.files = [];
    }
    

    因为是headeronly没有使用add_files添加文件,target.files不是null是一个空对象,调用了sort就崩掉了。我不知道ts怎么优雅的修复这个bug,这么判断之后不会崩溃了。

    期待的结果

    正常加载xmake插件

    工程配置

    target("demo") set_kind("headeronly") add_includedirs("include", {public = true})

    附加信息和错误日志

    No response

    bug 
    opened by v-dao 1
  • Can Xmake: Build Level be set to both warning and verbose?

    Can Xmake: Build Level be set to both warning and verbose?

    你在什么场景下需要该功能?

    我想编译与链接的参数和警告都能够输出,就像xmake -vw一样,同时看到这两种输出比较方便,对我来说还挺常用的。 更进一步希望build log level可以自由搭配而不局限于已有的四种(normal,debug,warning与verbose)

    描述可能的解决方案

    js不太了解,不过如果不考虑以后的拓展的话v w D 三种参数的全部自由组合数也就7种+1种normal完全可以暴力枚举(开玩笑的) 用数组来配置? 或者干脆自己手写build时传给xmake的参数大概也可以吧

    描述你认为的候选方案

    No response

    其他信息

    No response

    feature request 
    opened by fonqL 5
  • vscode 调试存在bug

    vscode 调试存在bug

    Xmake 版本

    2.6.8

    操作系统版本和架构

    Windows 10 专业版 21H2

    描述问题

    工具链使用的是msys2安装的mingw-w64-x86_64-toolchain,xmake同样是使用msys2安装 image

    在调试过程中,断点调试时,打的断点位置不是鼠标点击位置 同时高亮的行并不是代码运行的行,我应该执行for循环,但是高亮的行数不对 调试 同样的代码使用微软cmake插件则没有这个问题

    期待的结果

    可以解答是配置问题,还是软件自身问题

    工程配置

    xmake.lua

    add_rules("mode.debug", "mode.release")
    
    target("hello_xmake")
        set_kind("binary")
        add_includedirs("includes")
        add_files("src/main.cpp")
    

    文件结构,.cathe .clangd是使用vscode clangd插件,在不使用,仅使用官方C/C++插件,同样存在问题

    │  .clang-format
    │  .clangd
    │  .gitignore
    │  xmake.lua
    │
    ├─.cache
    │  
    ├─.vscode
    │      
    ├─build
    │  
    ├─includes
    │      fun.h
    └─src
            main.cpp
    

    fun.h

    #include <bits/stdc++.h>
    
    void disply_print() {
        for (int i = 0; i < 10; i++) {
            std::cout << "hello xmake"
                      << "\n";
        }
    }
    
    void extracted() {
        std::deque<int> poker;
        for (int i = 1; i < 100; i++) {
            poker.emplace_back(i);
        }
        int i = 1;
        while (poker.size() > 1) {
            int t = poker.front();
            poker.pop_front();
            if (i % 7 == 0) {
                poker.emplace_back(t);
            }
            i++;
        }
    
        printf("the last poker is: %d", poker.front());
    }
    

    main.cpp

    #include "fun.h"
    
    void disply() {
        std::cout << "the number of Students is 32" << std::endl;
    }
    
    void displaynumber() {
        std::vector<int> v{0, 1, 2, 3};
        for (auto &value : v) {
            std::cout<<value<<" ";
        }
    }
    
    int main() {
        disply();
        disply_print();
        displaynumber();
        extracted();
    }
    

    setting.json

    "xmake.compileCommandsDirectory": "${workspaceRoot}/build",
    "xmake.customDebugConfig": {
    	"stopAtEntry": false,
    	"externalConsole": false,
    	"internalConsoleOptions": "neverOpen",
    	"setupCommands": [
    		{
    			"description": "为 gdb 启用整齐打印",
    			"text": "-enable-pretty-printing",
    			"ignoreFailures": true
    		}
    	]
    }
    

    附加信息和错误日志

    没有显示错误,正常调试,但是存在上述问题

    bug 
    opened by F7kyyy 13
Owner
xmake-io
🔥 Xmake is a cross-platform build utility based on Lua
xmake-io
Visual Studio and GCC precompiled header macro for CMake

cmake-precompiled-header Precompiled header setup for CMake. Supported CMake generators: Visual Studio NMake Makefiles Unix Makefiles (GCC) MinGW Make

Lars Christensen 157 Nov 6, 2022
CMake integration for include-what-you-use

Include-What-You-Use CMake Targets CMake macro to add per-source level checks on individual targets for include-what-you-use violations Status Travis

ポリ平方 POLYSQUARE 8 Apr 10, 2021
Tundra is a code build system that tries to be accurate and fast for incremental builds

Tundra, a build system Tundra is a high-performance code build system designed to give the best possible incremental build times even for very large s

Andreas Fredriksson 400 Dec 23, 2022
A CMake addon that avoids you writing boilerplate code for resource management.

SHader INJ(I)ector SHINJI (originally SHader INJector) is a CMake addon that avoids you writing boilerplate code for resource management and exposes s

Lorenzo Rutayisire 6 Dec 14, 2022
CMake module to enable code coverage easily and generate coverage reports with CMake targets.

CMake-codecov CMake module to enable code coverage easily and generate coverage reports with CMake targets. Include into your project To use Findcodec

HPC 82 Nov 30, 2022
A set of cmake modules to assist in building code

CMake 3 Tools Warning: These tools are being replaced by the Modern CMake. Some of the tools are still being maintained for now, but new projects shou

null 201 Dec 21, 2022
Source code formatter for cmake listfiles.

cmake lang The cmakelang project provides Quality Assurance (QA) tools for cmake: cmake-annotate can generate pretty HTML from your listfiles cmake-fo

null 760 Dec 31, 2022
📦 An official xmake package repository

xmake-repo An official xmake package repository Supporting the project Support this project by becoming a sponsor. Your logo will show up here with a

xmake-io 332 Dec 24, 2022
A Visual Studio extension containing a collection of tools to help contributing code to the Chromium project.

VsChromium VsChromium is a Visual Studio Extension containing a collection of tools useful for editing, navigating and debugging code. VsChromium was

The Chromium Project 258 Dec 30, 2022
Visual Studio extension for assembly syntax highlighting and code completion in assembly files and the disassembly window

Asm-Dude Assembly syntax highlighting and code assistance for assembly source files and the disassembly window for Visual Studio 2015, 2017 and 2019.

Henk-Jan Lebbink 4k Jan 6, 2023
Mobile Studio tool integration with C# scripting for the Unity game engine.

Mobile Studio Package This project is a Unity package for integrating the Mobile Studio tool suite into game development workflows. This version of th

Arm Software 76 Dec 7, 2022
Bungie's Oni modified so it compiles with Microsoft Visual Studio 2019.

OniFoxed What's this? This is a modified variant of the recently leaked Oni source code so that it compiles under Microsoft Visual Studio 2019 with so

Mark Sowden 59 Dec 2, 2022
Using Visual Studio C++ to read IP addresses and comport number (Serial number) on Windows platform

Using Visual Studio C++ to read IP addresses on Windows platform

zhuhuijin 0 Feb 2, 2022
A D++ Discord Bot template for Visual Studio 2019 (x64 and x86)

D++ Windows Bot Template A D++ Discord Bot template for Visual Studio 2019 (x64 and x86, release and debug). The result of this tutorial. This templat

brainbox.cc 28 Dec 24, 2022
Visual Studio Extension for C++ struct memory layout visualization

Visual Studio Extension for C++ struct memory layout visualization

Ramon Viladomat 391 Jan 3, 2023
A Visual Studio template used to create Cobalt Strike BOFs

Introduction Cobalt Strike beacon object files (BOFs) is a feature that added to the beacon in order to allow rapid beacon extendibility in a more OPS

Securify 163 Dec 28, 2022
CMake scripts for painless usage of SuiteSparse+METIS from Visual Studio and the rest of Windows/Linux/OSX IDEs supported by CMake

CMake scripts for painless usage of Tim Davis' SuiteSparse (CHOLMOD,UMFPACK,AMD,LDL,SPQR,...) and METIS from Visual Studio and the rest of Windows/Lin

Jose Luis Blanco-Claraco 395 Dec 24, 2022
Visual Studio and GCC precompiled header macro for CMake

cmake-precompiled-header Precompiled header setup for CMake. Supported CMake generators: Visual Studio NMake Makefiles Unix Makefiles (GCC) MinGW Make

Lars Christensen 157 Nov 6, 2022
Sharpmake is an open-source C#-based solution for generating project definition files, such as Visual Studio projects and solutions, GNU makefiles, Xcode projects, etc.

Sharpmake Introduction Sharpmake is a generator for Visual Studio projects and solutions. It is similar to CMake and Premake, but it is designed for s

Ubisoft 779 Dec 23, 2022
Visual Studio Extension that installs additional color themes

Using this Extension Download and install the extension Restart Visual Studio Navigate to Tools > Options > Environment > General and select your colo

Microsoft 328 Dec 19, 2022