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

Deleting the build folder. #98

Closed
SaxonRah opened this issue Oct 7, 2024 · 5 comments
Closed

Deleting the build folder. #98

SaxonRah opened this issue Oct 7, 2024 · 5 comments

Comments

@SaxonRah
Copy link

SaxonRah commented Oct 7, 2024

In previous versions, I swear I could delete the build folder then click Configure CMake everything would be fine and I could still compile. No errors.

Now doing the same thing, results in: ninja: error: loading 'build.ninja': The system cannot find the file specified.

Running cmake -G Ninja .. in the build folder after clicking Configure CMake in the extension, solves the ninja error.

I had a friend contact me about this same problem, they had accidently deleted the build folder, and since I already knew the solution, I was able to solve that for them effortlessly. They apparently searched and struggled with it for a day or two and couldn't figure it out.

I'm partly posting this issue so people can find a solution if they encounter this, as well ask if this is expected functionality? I don't think I remember running cmake -G Ninja .. in the build folder before, but I could be wrong as I have to use that command for other toolchains and just can't remember.

@will-v-pi
Copy link
Collaborator

It looks like the notification saying configuration is complete pops up before configuration is actually complete - could you try waiting 10s (or until the build.ninja file appears in the build folder) after clicking Configure CMake before you click Compile and see if that works?

@Prototype-Laboratory
Copy link

Prototype-Laboratory commented Oct 14, 2024

Hi,
I am facing the same issue. The build.ninja file did not appear after waiting. The workaround, running cmake -G Ninja .. in the build folder after clicking Configure CMake in the extension, works for me too, but it isn't convenient. I'm using Linux.

Regards

@Prototype-Laboratory
Copy link

Ok, I found the mistake. In one of my CMakeLists.txt files in my project folder was the path to the pico_sdk_import.cmake file wrong. After I have corrected it, it is working now.

@paulober
Copy link
Collaborator

@SaxonRah Just pushed a commit that should fix this issue. Can you confirm with the preview build?

@SaxonRah
Copy link
Author

@SaxonRah Just pushed a commit that should fix this issue. Can you confirm with the preview build?

Yes, That does fix the problem. The build.ninja file seems to be generated before/at the same time as the popup.

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

4 participants