Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.12.3 windows python dependencies on macOS #10561

Closed
cederom opened this issue May 10, 2019 · 12 comments
Closed

5.12.3 windows python dependencies on macOS #10561

cederom opened this issue May 10, 2019 · 12 comments

Comments

@cederom
Copy link

cederom commented May 10, 2019

Hello world, with 5.12.3 I noticed a new warning on missing pywin32 and wmi Windows Python dependencies while running on macOS:

[mbed] WARNING: Missing Python modules were not auto-installed.
       The Mbed OS tools in this program require the following Python modules: pywin32, wmi
       You can install all missing modules by running "pip install -r requirements.txt" in "/(..)/firmware/mbed-os"
       On Mac you might have to install packages as your user by adding the "--user" flag

Do I really need them on macOS?

@ciarmcom
Copy link
Member

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1194

@cederom
Copy link
Author

cederom commented May 11, 2019

Thank you for looking into the issue :-) I have managed to install wmi by hand (it was next on the list after failing package), but pywin32 seems Windows only package and it not available on other platforms..

Another idea, I know this is pip related, would be to install all possible dependencies/requirements, even if some of them fail. At the moment the requirements.txt contains some list of packages that is not processed further when one of the elements cannot get installed.. but there are some packages that still can be installed even if previous package fails. The simples solution would be putting "mandatory" packages first and then the "optional" ones.. unless all of them are mandatory :-)

@0xc0170
Copy link
Contributor

0xc0170 commented May 13, 2019

cc @ARMmbed/mbed-os-tools

@linlingao
Copy link
Contributor

I'm also using Mac and getting the same warning. I haven't noticed anything broken. It could be we just need to remove these warnings.

@cederom
Copy link
Author

cederom commented May 13, 2019

I guess more like add some OS detect in mbed deploy or mbed update in order to generate host specific requirements.txt rather than remove warnings :-)

@TeroJaasko
Copy link
Contributor

TeroJaasko commented Jun 7, 2019

Same warnings are given when building in Linux too.

@teetak01
Copy link
Contributor

teetak01 commented Jun 7, 2019

This issue has been fixed in Mbed CLI master. It would just require a new release of the tool.
ARMmbed/mbed-cli#889

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 13, 2019

@ARMmbed/mbed-os-tools When the new version of tools is released? This issue could be fixed and closed.

@mark-edgeworth
Copy link
Contributor

We're intending to release a new version of mbed-cli within the next week provided we can be reasonably clear on what we are releasing. We're currently blocked on updating the version of the related mbed-ls while we work through some inconsistencies we've found in the target database.

@cederom
Copy link
Author

cederom commented Aug 13, 2019

Great news @mark-edgeworth hope that full-rebuild will be fixed as well.. it takes lots of time.. I am eager to test :-)

@madchutney
Copy link
Contributor

madchutney commented Aug 22, 2019

Hi @cederom, we have released a new version of Mbed CLI (1.10.1). I hope it resolves your issue, please reopen and mention myself or @mark-edgeworth if there are any issues.

Sorry it took so long to get a release out .

@cederom
Copy link
Author

cederom commented Aug 27, 2019

NO FULL REBUILD NOW! ONLY WHAT HAS CHANGED! THANK YOU!! @madchutney @mark-edgeworth @0xc0170 @teetak01 @TeroJaasko @linlingao + team :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants