-
Notifications
You must be signed in to change notification settings - Fork 779
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
Avoid accidentally using the "check" macro on OSX #342
Conversation
@astrodroid , if you coudl validate this on OSX, it woudl be greatly appreciated. |
Will merge as soon as someone on OSX can test. |
@erichkeane, I will be away for most of today, I can test this pull request this evening or tomorrow. |
Hi although it works fine for me, I haven't been able to run any unit tests as I haven't found a way to run all of them automatically. Is there a script that I missed or do I have to call each test case? |
There is a CMake file in the root directory, and the unit tests all build (and I think run?) when doing 'make' after that. Do something like this from the root of Cereal (assuming you have cmake installed): |
Thanks @erichkeane, I have cmake installed. I did run cmake with the cmake_file.txt modified as here so that boost will be found:
but I get link time error, appearing something has gone wrong in the setting up of the environmental variables.
If some of you has access to a mac it might be faster than me solving my issues with boost... |
OK I managed to run the tests. It passes all of them except the portability_test 32 and 64 bit which returns segmentation fault: 11. But that was present even before and I haven't tried to look up what's causing it. |
Merged into develop. The portability tests are probably because you don't have a 32bit compiler installed, you can safely compile with those tests turned off (SKIP_PORTABILITY_TEST=ON) for CMAKE. |
Fix for #341, #273, and #104. Replace usages of "check(" with
"(check)(", which will prevent us from colliding with the macro defined
in OSX's Assert macros.