Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Optiligence
Copy link

Also fixes installation directories (using GNUInstallDirs) because I didn’t want to commit on top of to-be-fixed code (or create conflicting/interdependent PRs).

i.e. the imported target name from Snappy::snappy to Snappy::Snappy
as is general practice
`DESTINATION lib` in `install(TARGETS)` was also installing DLLs to lib
it also allows configuration in contrast to hard coded values
allows to install shared and static builds on top of each other
using different export names and dispatch in SnappyConfig

with the ability (not requirement) to link to a static or shared variant explicitly as goal in mind
the following approaches are unsuitable:
- populating a variable in SnappyConfig or in downstream projects → prevents errors as per [0]
- creating an alias target for one of the imported targets → currently not allowed [1]
- manually creating a default imported target and populating all necessary properties → bad for maintenance

[0] https://cmake.org/cmake/help/latest/policy/CMP0028.html
[1] https://cmake.org/cmake/help/latest/command/add_library.html#alias-libraries
@cmumford
Copy link
Contributor

@googlebot rescan

@pwnall
Copy link
Member

pwnall commented Jan 12, 2022

Thank you for your contribution!

We're not currently interested in contributions to the build configuration. We now have a paragraph explaining the situation in https://github.com/google/snappy/blob/master/README.md#contributing-to-the-snappy-project

@pwnall pwnall closed this Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants