-
Notifications
You must be signed in to change notification settings - Fork 55
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
objfile not output in current directory #166
Comments
It is not obvious as you can have several modules that share the same filename. What makes the most sense is to keep the folder that are packages, and drop the ones above this. |
I think I do not agree... This is about the default place to put build artifacts, which for the compilers that I know is in the current folder. It'd be very strange to strip only part of the path, no? |
Going back over the whole list of things, this one is interesting. I get where you are coming from and I think there is a legitimate point to it, but the solution didn't quite work. Should we rebase the path on top of the current directory? Mange the fully qualified module name in the filename? |
this has been a while! :) |
I think #271 would be the right solution here. I tied not in my brain for no reason: GCC, clang &al will chose a name by default if none is specified, however, we do have packages/module, so we shoudl take advantage of this. |
The command
sdc ../test.d
outputs filesa.out
and../test.o
.I would have expected that
test.o
would be created in the current directory, instead of in the same path as the input D file. This is what dmd does.The fix for this is easy, let me know if desired.
(also, looking at the code in
main.d
, I think the extension should be fully stripped from the input file before generating the objfilename, instead of just removing the last 2 characters, in case someone has files namedtest.dlang
or whathaveyou)The text was updated successfully, but these errors were encountered: