Dmitry Gerasimov

Unfortunately, it's all usually not that easy. This might work for simplest cases, but for most real-world projects this won't work, as the compiler needs to know lots of compilation...

> I don't want to compile complex real-world projects, I just want to open a C file and see what "hello world" or simple functions compile into, out of curiosity....

Hi, At first, I'm sorry for a too-late reply. I've tried exact the same configuration with the same directory layout as yours, but it seems to work well. Maybe there...

> But, when I tried to slightly change the source code, the assembly file did not get updated. Looks very similar to #6. It seems that fixing that issue will...

Yep, that would be nice :) Unfortunately, VS Code does not exposes [variableResolver](https://github.com/microsoft/vscode/blob/cc8ff11f574d029f90284509da15337b6de17ca3/src/vs/workbench/services/configurationResolver/common/variableResolver.ts) yet (which is weird as a lot of extensions need this thing).

cmake-tools has [its own](https://github.com/microsoft/vscode-cmake-tools/blob/a856186544f8afefd34ea4b1060e7fd4f56fb1fc/src/expand.ts) variables parser under the hood. And so does disasexpl, just not that powerful (yet). I think that [current resolver](https://github.com/dseight/vscode-disasexpl/blob/9c0138df82077ee946a520748dca572a16614b0e/src/provider.ts#L87) needs to be rewritten, with [variableResolver](https://github.com/microsoft/vscode/blob/cc8ff11f574d029f90284509da15337b6de17ca3/src/vs/workbench/services/configurationResolver/common/variableResolver.ts) as...

Thank you for the comprehensive description! Relative paths handling should be fixed with commit e4b202996a3255789548ff35b35dd26d4b0fbfcf (release 0.2.2). Regarding the reloading of file changes — it should work fine as well....