Certain libraries (like for instance python, when used in embedded mode) use #pragma to link necessary libraries i.e. hard coded in config files. The library name used doesn't match what gradle publishes. Ideally, these libraries should have a way to disable this auto-include but that is not always the case.
Expected Behavior
Unsure how this can be handled but one way is either not to rename the libraries or rename them back to expected/generated-name after expansion from cache. Other alternative is to maintain our own version of the default config file.
Current Behavior
Published library names and expected library names don't match. For instance, when publishing python v2.7 the published library name is Python_debug-2.7.12.lib but the expected is python27.lib which is what is called out in the default config files.
Context
Publish python as an artifact and consume it in an application.
Certain libraries (like for instance python, when used in embedded mode) use #pragma to link necessary libraries i.e. hard coded in config files. The library name used doesn't match what gradle publishes. Ideally, these libraries should have a way to disable this auto-include but that is not always the case.
Expected Behavior
Unsure how this can be handled but one way is either not to rename the libraries or rename them back to expected/generated-name after expansion from cache. Other alternative is to maintain our own version of the default config file.
Current Behavior
Published library names and expected library names don't match. For instance, when publishing python v2.7 the published library name is Python_debug-2.7.12.lib but the expected is python27.lib which is what is called out in the default config files.
Context
Publish python as an artifact and consume it in an application.