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

when doing a clean build, you get an error message about "file not found CMakeCache.txt" #28

Closed
MinnieTheMoocher opened this issue Sep 16, 2016 · 5 comments
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature

Comments

@MinnieTheMoocher
Copy link

When you do a REAL clean build,
i.e., you are completely DELETING the ./build subfolder of your sourcecode,
including all of its contents AND the folder itself,
and then are using your (nice!) plugin to launch a build without first launching
a manual "CMake: configure" command, then your plugin will display an error message
"file not found: build/CMakeCache.txt".
It would be much nicer if it instead could detect that either the folder OR that file
is not present, and in that case will automatically launch a cmake configure
instead of displaying that error message.

@vector-of-bool
Copy link
Contributor

Hmm... Sounds like a problem. Could I get a more precise list of steps to reproduce the issue? I'll get on this one.

@vector-of-bool vector-of-bool added the bug a bug in the product label Sep 16, 2016
@vector-of-bool
Copy link
Contributor

This behavior may have been changed/fixed in the 0.4.0 release. Could you try to reproduce the issue and confirm that it still occurs?

@MinnieTheMoocher
Copy link
Author

MinnieTheMoocher commented Sep 19, 2016

the behaviour (with 0.4.0) is now that I get an error message which requests me to first configure the project.
It allows me 2 reactions:

  • do that
  • close

This means that the bug is gone and this issue could be closed.
However: may I convert the bug report into a change request?

I can not see a real good reason for that prompt.
Why not automatically launch the "configure" step, and then the build?
I can not see a usecase where I as a user would not want the "configure" step to automatically run.
If I really want to stop it, there is the "stop" button for me.

I would find it much more convenient if I could completely skip worrying about
the "configure" step, and instead just use "CMake: build" all the time
(provided that I have present proper user settings and/or workspace settings).

@vector-of-bool vector-of-bool added enhancement an enhancement to the product that is either not present or an improvement to an existing feature and removed bug a bug in the product labels Sep 20, 2016
@vector-of-bool
Copy link
Contributor

You're probably right. I've considered just removing that prompt. Usually, the only time I've seen it is when I accidentally strike the F7 key in a non-CMake project, and even then it will get caught on the current workspace not being a CMake project.

@vector-of-bool vector-of-bool added the in progress actively being working on label Sep 21, 2016
vector-of-bool added a commit that referenced this issue Sep 21, 2016
…ld command.

It's not really useful (Address issue #28)
@vector-of-bool vector-of-bool removed the in progress actively being working on label Sep 21, 2016
@vector-of-bool
Copy link
Contributor

Changed in next release

@github-actions github-actions bot locked and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement an enhancement to the product that is either not present or an improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants