Skip to content

GREENTEA can't compile is DEVICE_SERIAL is not enabled #9850

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

Closed
jeromecoutant opened this issue Feb 26, 2019 · 4 comments · Fixed by #11086
Closed

GREENTEA can't compile is DEVICE_SERIAL is not enabled #9850

jeromecoutant opened this issue Feb 26, 2019 · 4 comments · Fixed by #11086

Comments

@jeromecoutant
Copy link
Collaborator

Description

How to reproduce:

  • remove SERIAL from DEVICE_HAS in targets json file
  • add "*cellular*" in .mbedignore
$ mbed compile -t ARM -m NUCLEO_L476RG -v

[Error] greentea_serial.h@10,0:  #1046: namespace "mbed"  has no member class "RawSerial"
[Error] greentea_serial.h@10,0:  #262: not a class or struct name
[Error] greentea_serial.cpp@15,0:  #1046: namespace "mbed"  has no member class "RawSerial"
[Error] greentea_serial.cpp@15,0:  #18: expected a ")"

I don't see any reason why greentea-client should be compiled when DEVICE_SERIAL is not enabled.

Thx

Issue request type

[ ] Question
[ ] Enhancement
[x] Bug
@jeromecoutant
Copy link
Collaborator Author

Note there is also impacts in:

  • UTEST compilation:
[Error] utest_serial.h@25,0:  #5: cannot open source input file "greentea-client/greentea_serial.h": No such file or directory
  • unity compilation:
[Error] unity.c@8,0:  #5: cannot open source input file "utest/unity_handler.h": No such file or directory

@ciarmcom
Copy link
Member

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

@jeromecoutant
Copy link
Collaborator Author

Hi

Note that this issue is raised during TFM scope. (#9221) (#9853)

cc @ARMmbed/mbed-os-hal @ARMmbed/mbed-os-maintainers @ARMmbed/mbed-os-psa

@kjbracey
Copy link
Contributor

Somewhat related: #6674

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

Successfully merging a pull request may close this issue.

3 participants