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

allow to exclude current directory from search path in dmd #17717

Open
dlangBugzillaToGithub opened this issue Jul 20, 2015 · 5 comments
Open
Labels

Comments

@dlangBugzillaToGithub
Copy link

Timothee Cour (@timotheecour) reported this on 2015-07-20T03:06:42Z

Transferred from https://issues.dlang.org/show_bug.cgi?id=14811

CC List

  • Timothee Cour

Description

I'd like to have an option to exclude current directory from search path in dmd.
I already made a local modification to dmd to allow that (dmd -exclude_cwd_from_imports)
Would that be acceptable?

(cf forum EMAIL:exclude current directory from search path in dmd ?)
@dlangBugzillaToGithub
Copy link
Author

timothee.cour2 commented on 2015-07-20T03:30:29Z

Reduced use case:
see https://github.com/timotheecour/dsnippet/tree/master/bug_14811

make
..//main.d(3): Error: module foo.fun1 from file fun1.d conflicts with another module fun1 from file ..//foo/fun1.d

With my modification (adds a flag -exclude_cwd_from_imports):
make with_flag
#works

@dlangBugzillaToGithub
Copy link
Author

timothee.cour2 commented on 2015-07-20T08:06:25Z

https://github.com/D-Programming-Language/dmd/pull/4823

@dlangBugzillaToGithub
Copy link
Author

timothee.cour2 commented on 2015-07-21T08:50:02Z

(In reply to Timothee Cour from comment #2)
> https://github.com/D-Programming-Language/dmd/pull/4823

To test it via Digger:
./digger build "master + timotheecour/dmd/exclude_cwd_from_path"
=> result/bin/dmd

@dlangBugzillaToGithub
Copy link
Author

k.hara.pg commented on 2015-07-29T22:44:45Z

(In reply to Timothee Cour from comment #0)
> (cf forum EMAIL:exclude current directory from search path in dmd ?)

http://forum.dlang.org/thread/mailman.308.1426472794.3111.digitalmars-d-learn@puremagic.com
http://forum.dlang.org/thread/CANri+ExGss5FJXBy728rJN9YpvTKoSsk9fzcCrL4vSkuExg13A@mail.gmail.com

(In reply to Timothee Cour from comment #1)
> Reduced use case:
> see https://github.com/timotheecour/dsnippet/tree/master/bug_14811

Why you need to compile the project from the subdir foo/ ? Why you cannot do that from the project root directory?

The feature explanation does not argue the necessity of the enhancement. Please show to us the situation where the feature is necessary.

@dlangBugzillaToGithub
Copy link
Author

timothee.cour2 commented on 2015-07-30T01:50:39Z

>> Why you cannot do that from the project root directory?

There's not always an obvious project root directory, eg when using submodules or several outside packages. 

>> The feature explanation does not argue the necessity of the enhancement. Please show to us the situation where the feature is necessary.

* I'm not the only one wanting this: http://forum.dlang.org/post/mlqdzpswbwqyrwiibqwg@forum.dlang.org

* It exists in c++
http://stackoverflow.com/questions/12353429/prevent-gcc-from-searching-the-current-dir-i-option-on-include-search-path

* if the 'natural' working directory is foo/ (current directory, where user edits files etc), wrapping every dmd invocation with 
'cd root && dmd some_command  && cd -'
is inconvenient. Eg, the error messages will be wrt to root, not wrt user's current directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant