-
Notifications
You must be signed in to change notification settings - Fork 32
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
Install .dll files into bin directory #32
Comments
Hey @markand , I am Komal from Pune, India. I'm studying 4th year of engineering. I really want to work on this issue. But since, I am totally novice to open source, could you help me? How do I go about this issue? |
@swatanabe What do you think about this one? I noticed that under Cygwin the DLLs are actually installed in the --bindir and did wonder briefly why we don't do this for "ordinary" Windows. |
AMDG
On 12/18/2018 05:40 PM, Peter Dimov wrote:
@swatanabe What do you think about this one? I noticed that under Cygwin the DLLs are actually installed in the --bindir and did wonder briefly why we don't do this for "ordinary" Windows.
bin/ is probably better, but I'm uncertain
whether it's worth a breaking change at this
point.
In Christ,
Steven Watanabe
|
I looked at the history, and Cygwin was changed in boostorg/build@fe12dc5 by @vprus, but it's not clear why Windows hasn't been. It definitely sounds like the right thing to do, while we're at it. |
I'm not sure if this is a real breaking change. The .dll files are never implied in build process, only users are responsible of updating their PATH or copy .dll once packaging. Thus this is not a big deal IMHO. |
We could in principle add |
Hello,
On Windows, .dll files are installed in the lib/ directory under the prefix. This is quite awkward and should be installed into bin/ directory as many other projects and conventions do.
Thus, user that adds PATH to a common prefix + bin/ will have runtime dependencies correctly.
The text was updated successfully, but these errors were encountered: