-
Notifications
You must be signed in to change notification settings - Fork 101
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
nob build fails on windows when called without file extension #29
Comments
just ran into this I am now at something with my shellapi.
|
OetkenPurveyorOfCode
pushed a commit
to OetkenPurveyorOfCode/musializer
that referenced
this issue
Oct 22, 2023
To support loading filenames with unicode characters on windows, declare UTF-8 support in the manifest file.
OetkenPurveyorOfCode
pushed a commit
to OetkenPurveyorOfCode/musializer
that referenced
this issue
Oct 22, 2023
To support loading filenames with unicode characters on windows, declare UTF-8 support in the manifest file.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running nob without .exe file extension fails.
The application takes its name from argv[0] which is
nob
and tries to rename a file namenob
that does not exist. (Hint: The file name isnob.exe
)The build system should append the appropriate file extension to support being called without
.exe
.One way to achieve this functionality would be:
To retrieve the binary path instead of using argv[0].
I think one should consider what should happen when the executable is called with a relative path.
I think the build system could assume that nob.exe and nob.c are always in the same directory. To support calling the build system from a different working directory, the directory the binary lives in should be prepended to the file name of the source file to generate the full source file path.
The text was updated successfully, but these errors were encountered: