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

Should test with Zephyr in the CI #40

Open
thiagomacieira opened this issue Aug 4, 2016 · 0 comments
Open

Should test with Zephyr in the CI #40

thiagomacieira opened this issue Aug 4, 2016 · 0 comments

Comments

@thiagomacieira
Copy link
Member

Zephyr is important.

thiagomacieira added a commit to thiagomacieira/tinycbor that referenced this issue Jan 30, 2018
Freestanding C, as opposed to hosted C (see the macro), is restricted to
a few C headers and usually lacks a libc. In our case, that means we
cannot assume <stdio.h> and FILE* is present, but we do require
<string.h> (memcpy, memcmp).

This commit simply makes it easier for me to test that TinyCBOR still
compiles in freestanding mode. Eventually I need to test with an actual
Zephyr build (issue intel#40).

Signed-off-by: Thiago Macieira <[email protected]>
thiagomacieira added a commit that referenced this issue Jan 30, 2018
Freestanding C, as opposed to hosted C (see the macro), is restricted to
a few C headers and usually lacks a libc. In our case, that means we
cannot assume <stdio.h> and FILE* is present, but we do require
<string.h> (memcpy, memcmp).

This commit simply makes it easier for me to test that TinyCBOR still
compiles in freestanding mode. Eventually I need to test with an actual
Zephyr build (issue #40).

Signed-off-by: Thiago Macieira <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant