Skip to content

--mbed-os-path Doesn't work #329

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Open
BioBox opened this issue Sep 5, 2022 · 2 comments · May be fixed by #330
Open

--mbed-os-path Doesn't work #329

BioBox opened this issue Sep 5, 2022 · 2 comments · May be fixed by #330
Labels
bug Something isn't working

Comments

@BioBox
Copy link

BioBox commented Sep 5, 2022

Describe the bug
I have a copy of the mbed os, but using the --mbed-os-path doesn't change the directory that cmake attempts to use; it always assumes that the os is right in the current directory.

To Reproduce
Steps to reproduce the behavior:

  1. Run mbedtools new PATH to download the mbed os.
  2. Run mbedtools new -c OS_PATH to create a project without copying the entire operating system.
  3. Run mbedtools compile [...] --mbed-os-path OS_PATH
  4. See error

Expected behavior
The --mbed-os-path setting should modify the MBED_PATH so that cmake is pointed to the correct os directory.
@BioBox BioBox added the bug Something isn't working label Sep 5, 2022
@BioBox
Copy link
Author

BioBox commented Sep 5, 2022

This bug also happens with the configure command.

@BioBox
Copy link
Author

BioBox commented Sep 7, 2022

My idea for a solution would be to have --mbed-os-path be used for the new command instead of the building one.

@BioBox BioBox linked a pull request Sep 12, 2022 that will close this issue
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use a single copy of mbed os for different projects. BioBox/mbed-tools
1 participant
@BioBox