Skip to content

Utility of the static linked library in the image if --enable-shared is active #507

@Lebvanih

Description

@Lebvanih

Hello,

I was wondering why the static library libpythonXX.a (example in the alpine: /usr/local/lib/python3.8/config-3.8-x86_64-linux-gnu/libpython3.8.a) was kept in the docker image for all the image variance, while the --enable-shared flag is active for the compilation process. That file is around 50% of the image size on the alpine.

I am assuming this is intended for the usage of some use case where you might need to link some code directly to it, but the documentation of the image only make reference to using the image as base, including our own script and just run it with python (which seems to be dynamically linked to the .so files).

I am mostly curious to know if this is intended or if this is an oversight from a few year ago when the --enable-shared flag was added.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy