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

On shared library names #1767

Closed
wants to merge 3 commits into from

Conversation

levitte
Copy link
Member

@levitte levitte commented Oct 21, 2016

@kaduk informed me that there was no information on the new DLL names on Windows... and except for the git log, he's absolutely correct. This adds the information in INSTALL and adds a not to this effect in the entry in CHANGES that announces the unified build, 'cause that's where this should have been notified from the start.

@levitte
Copy link
Member Author

levitte commented Oct 21, 2016

@kaduk, I'd be very pleased if you'd read through the added notes to see if they are satisfactory.

Copy link
Contributor

@kaduk kaduk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I had written something, I probably would have included the strings "libcrypto" and "libssl" in CHANGES, but I don't have a good sense for whether there are people who are familiar with the windows names but not the Unix names.
Regardless, this is nice to have, even as-is -- thanks!

@@ -947,6 +947,31 @@
where OpenSSL does not know how to build shared libraries the "no-shared"
option will be forced and only static libraries will be created.

Shared libraries are named a little different on different platforms.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might use "differently" ... but I might not.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@levitte levitte self-assigned this Oct 22, 2016
@levitte levitte added branch: master Merge to master branch 1.1.0 labels Oct 22, 2016
@levitte
Copy link
Member Author

levitte commented Oct 22, 2016

@richsalz, I forgot to lable the intended branches. Now done, are you still fine with it?

@richsalz
Copy link
Contributor

Yes.

levitte added a commit that referenced this pull request Oct 25, 2016
This is overdue since the addition of the unified build system

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #1767)
levitte added a commit that referenced this pull request Oct 25, 2016
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #1767)
@levitte
Copy link
Member Author

levitte commented Oct 25, 2016

Done

@levitte levitte closed this Oct 25, 2016
levitte added a commit that referenced this pull request Oct 25, 2016
This is overdue since the addition of the unified build system

Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #1767)
(cherry picked from commit 4fa3f08)
levitte added a commit that referenced this pull request Oct 25, 2016
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from #1767)
(cherry picked from commit 78ce90c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch: master Merge to master branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants