Cannot find ".vscode\compile_commands.json". about xmake-vscode

[waruqi]

xmake-vscode/src/xmake.ts

Lines 193 to 205 in 32ab272

	async onProjectFileUpdated(affectedPath: vscode.Uri) {
	// trace
	log.verbose("onProjectFileUpdated: " + affectedPath.fsPath);
	// wait some times
	await utils.sleep(2000);
	// update project cache
	let filePath = affectedPath.fsPath;
	if (filePath.includes("xmake.lua")) {
	this.loadCache();
	this.updateIntelliSense();

The compile_commands.json file will only be generated when the xmake.lua file is changed. You can try to modify the xmake.lua file.

Sorry, I don’t have a windows+vscode environment. If this problem still exists, you can use vscode to open the xmake-vscode project source code, load and run it, and debug the following code.

[waruqi]

@jprochazk have fixed it, you can try it again. I have uploaded v1.4.3 to vscode market.

[RussellHaley]

The update was in the extensions window when I opened VS Code. I accepted the update and it restarted the project. It wouldn't compile right away. I changed a cpp file and compile_commands.json showed up. I couldn't get it to build until I restarted again, but I think that was my fumbling.

Xmake works as expected. Adding a new file to the project and to xmake.lua works (new entry in compile_comanes.json). The keymaps don't change from the defaults. To change the key mappings: Manage (Gear icon, bottom left) -> Keyboard Shortcuts. Type "xmake:" then change the shortcut. Is it possible to re-arrange keymaps in a VSCode extension?

I changed:
New window ctrl+shift+n -> ctrl + alt + n (re-assigned)
Build Task -> (removed)
xmake: build -> ctrl+shift+b (same as Visual Studio)
xmake: clean -> ctrl+shift+n
xmake: run -> shift + .

Thanks Ruki, @jprochazk.

[waruqi]

Is it possible to re-arrange keymaps in a VSCode extension?

Currently you can only modify the key mapping manually. refer #50 (comment)

File > Preferences > Keyboard Shortcuts, write xmake into the search bar, find XMake: Debug, right click it and click Change Keybinding