You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ran into an unexpected issue the other day, which I've already mostly documented here in #1476
But TLDR'
Started making a console based application to get acquainted with the language.
Ran into an issue where a missing .dll was causing my application to fail upon starting.
No exit codes, no errors, nothing
Only output I was getting was the launch message (after running clean-run)
Compared things with a console app built from a CLion C console app template.
For some reason, I got a pop up error from Windows stating that a .dll was missing which ended up solving my original problem.
I should note that in the CLion test project, I was using the IDE to build/launch the program instead of doing things on the command line. I only got the error message when running things through the IDE. When trying to run the built executable from the command line, I saw the same behavior like in the C3 version.
I don't know what CLion is doing behind the scenes but given that I was seeing the same behavior from both programs when running from the command line, it feels like my original issue is probably expected behavior so I wouldn't consider this a super high priority issue.
That said, it'd be nice if it were possible to add some kind of error message or at the very least, an exit code.
The text was updated successfully, but these errors were encountered:
👋
Ran into an unexpected issue the other day, which I've already mostly documented here in #1476
But TLDR'
.dll
was causing my application to fail upon starting.clean-run
).dll
was missing which ended up solving my original problem.I should note that in the CLion test project, I was using the IDE to build/launch the program instead of doing things on the command line. I only got the error message when running things through the IDE. When trying to run the built executable from the command line, I saw the same behavior like in the C3 version.
I don't know what CLion is doing behind the scenes but given that I was seeing the same behavior from both programs when running from the command line, it feels like my original issue is probably expected behavior so I wouldn't consider this a super high priority issue.
That said, it'd be nice if it were possible to add some kind of error message or at the very least, an exit code.
The text was updated successfully, but these errors were encountered: