Skip to content

Buggy dependencies handling with multiple ./distribute.sh #90

Closed

Description

@tito

We should be smarter when using ./distribute.sh.

We should:

  • seperate C libs with Python extensions, and prior C libs before any python extensions.
  • be smart of the python deps: if someone compiled with -m "kivy" and then "sqlite3 kivy", sqlite3 will be compiled, but not python again. So the module sqlite3 will not appear in the final distribution!

Activity

  1. techtonik commented on May 19, 2014

    @techtonik

    How about moving from .sh build system to something more Pythonic like SCons?

  2. knappador commented on May 19, 2014

    @knappador
    Contributor

    Mathieu, does this require better usage of distribute.sh or re-design of
    part of distribute.sh?

    K

    2014-05-19 23:47 GMT+09:00 anatoly techtonik notifications@github.com:

    How about moving from .sh build system to something more Pythonic like
    SCons?

    —
    Reply to this email directly or view it on GitHubhttps://github.com//issues/90#issuecomment-43513261
    .

  3. inclement commented on Dec 6, 2015

    @inclement
    Member

    I'll close this as fixed by the new toolchain - it should build a different python-install for each set of optional dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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