Add generated libtool file and .libs/ directories #4511
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
libtool is a generated script. See https://www.sourceware.org/autobook/autobook/autobook_49.html ("You must then arrange for your project build process to create an instance of libtool on the user’s machine [...]"). Also documented in the generated script itself ("Generated automatically by config.status [...] NOTE: Changes made to this file will be lost: look at ltmain.sh")
.libs/ directories are created by libtool; see https://www.gnu.org/software/libtool/manual/libtool.html ("Note that Libtool automatically created .libs directory upon its first execution, where PIC library object files will be stored.")