Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI is not started if makefile.buildLog is provided #266

Closed
cetygamer opened this issue Jan 13, 2022 · 2 comments
Closed

UI is not started if makefile.buildLog is provided #266

cetygamer opened this issue Jan 13, 2022 · 2 comments
Milestone

Comments

@cetygamer
Copy link

If makefile.buildLog option is provided, extension does not activate UI (icon in the side bar) and does not register most commands.

Only commands available in such case:

image

Debug extension log (I stripped IntelliSense configuration and parsing of make output):

Configurations cached at /home/frim/editline/.vscode/configurationCache.log
No path to the makefile is defined in the settings file.
No folder path to the makefile is defined in the settings file.
Build log defined at "/home/frim/editline/.vscode/build.log"
Always pre-configure: false
Dry-run switches: --always-make,--keep-going,--print-directory
Additional compiler names: 
Exclude compiler names: 
No current configuration is defined in the workspace state. Assuming 'Default'.
No target defined in the workspace state. Assuming 'Default'.
No current launch configuration is set in the workspace state.
Default launch configuration: MIMode = undefined,
                    miDebuggerPath = undefined,
                    stopAtEntry = undefined,
                    symbolSearchPath = undefined
Configure on open: true
Configure on edit: false
Configure after command: false
Only .PHONY targets: false
Save before build or configure: true
Build before launch: true
Clear output before build: true
Ignore directory commands: true
compile_commands.json path: null
Deduced command 'make ' for configuration "Default"
Saving opened files before build.
Configuring from cache: /home/frim/editline/.vscode/configurationCache.log
Load configuration from cache elapsed time: 0.28
<STRIPPED>
Preprocessing: "/home/frim/editline/.vscode/build.log"
Preprocess elapsed time: 0
Parsing for IntelliSense.
Updating the CppTools IntelliSense Configuration Provider.
Parsing dry-run output for CppTools Custom Configuration Provider.
<STRIPPED>
No launch configurations have been detected.
Complete list of launch targets: 
Parsing for launch targets elapsed time: 0.013
Generating parse content for build targets.
Generating targets information with command: 'make all --print-data-base --no-builtin-variables --no-builtin-rules --question'
Writing the dry-run output: /home/frim/editline/.vscode/targets.log
Spawning child process with:
 process name: make
 process args: all,--print-data-base,--no-builtin-variables,--no-builtin-rules,--question
 working directory: /home/frim/editline
 shell type: default
Generating dry-run elapsed time: 0.019
Parsing for build targets from: "/home/frim/editline/.vscode/targets.log"
Found the following 134 build targets defined in the makefile: <STRIPPED>
Complete list of build targets: <STRIPPED>
Parsing build targets elapsed time: 0.008
Configure finished. The status for all the subphases that ran:
loadFromCache: return code = 0, elapsed time = 0.28
generateParseContent: return code = 0, elapsed time = 0
preprocessParseContent: return code = 0, elapsed time = 0
parseIntelliSense: return code = 0, elapsed time = 0.054
parseLaunch: return code = 0, elapsed time = 0.013
dryrunTargets: return code = 1, elapsed time = 0.019
parseTargets: return code = 0, elapsed time = 0.008
Configure succeeded.
Sending telemetry: eventName = configure
properties: firstTime = "false",makeDryRun = "false",readCache = "true",isClean = "true",processTargetsSeparately = "false",resetBuildTarget = "false",triggeredBy = "configure dirty (on open), settings (configureOnOpen)",buildTarget = "(unset)"
measures: numberBuildTargets = "134",numberLaunchTargets = "0",numberIndexedSourceFiles = "3",numberMakefileConfigurations = "0",totalElapsedTime = "0.429",exitCode = "0",loadFromCache.exitCode = "0",loadFromCache.elapsed = "0.28",generateParseContent.exitCode = "0",generateParseContent.elapsed = "0",preprocessParseContent.exitCode = "0",preprocessParseContent.elapsed = "0",parseIntelliSense.exitCode = "0",parseIntelliSense.elapsed = "0.054",parseLaunch.exitCode = "0",parseLaunch.elapsed = "0.013",dryrunTargets.exitCode = "1",dryrunTargets.elapsed = "0.019",parseTargets.exitCode = "0",parseTargets.elapsed = "0.008"
Configure elapsed time: 0.429
Sending telemetry: eventName = settings
properties: makefile.loggingLevel = "Debug",makefile.makeDirectory = "undefined",makefile.makefilePath = "undefined",makefile.buildLog = "...",makefile.extensionLog = "...",makefile.configureOnEdit = "false",makefile.configureAfterCommand = "false"
@andreeis
Copy link
Contributor

andreeis commented Jan 14, 2022

@cetygamer, yes we found this after 0.3.1 and it will be fixed with 0.4.0 (soon).

#256

In the meantime, you can manually run "Makefile: Configure" from the VSCode commands pallette or you can install manually a vsix (downloaded from here) which contains the fix. Use "Install from vsix" context menu of "..." in the extensions left side tab.

@andreeis andreeis added this to the 0.4.0 milestone Jan 14, 2022
@andreeis
Copy link
Contributor

@cetygamer, we released Makefile Tools 0.4.0 today which contains the fix for this issue and also worth noting, localization support. If you happen to use VSCode language packs, give Makefile Tools a try in your preferred language.
Let us know if you encounter any issues: with the translated strings, any other bugs or if you have any feedback for the future of this extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants