-
Notifications
You must be signed in to change notification settings - Fork 881
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
Explicitly specify the project is a C project if tests aren't used. #1055
Conversation
CMake assumes the default project uses both C and C++, and therefore will fail if both a C and a C++ compiler isn't found. This essentially blocks pure C projects from using msgpack-c if they also don't have a C++ compiler. Just specifying that the project is "C" isn't possible though, as the test themselves use C++. The workaround here is that we specify the project needs both a C and C++ compiler if tests are used, but only a C compiler if the tests aren't used.
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## c_master #1055 +/- ##
=========================================
Coverage 55.45% 55.45%
=========================================
Files 8 8
Lines 1044 1044
=========================================
Hits 579 579
Misses 465 465 |
Thanks! LGTM. |
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
msgpack is written in c, so only enforce a c compiler upstream: msgpack/msgpack-c#1055 Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com>
CMake assumes the default project uses both C and C++, and therefore will fail if both a C and a C++ compiler isn't found. This essentially blocks pure C projects from using msgpack-c if their users also don't have a C++ compiler.
Just specifying that the project is "C" isn't possible though, as the test themselves use C++. The workaround here is that we specify the project needs both a C and C++ compiler if tests are used, but only a C compiler if the tests aren't used.