Conversation
|
Even if this features are not used in Back in 8fdf48f I added the definition of the Some alternative solutions could be:
Interesting discussions on this: |
|
we currently use the version of this PR within our ROS2 base, and it's working fine. Question here is what do you with this PR. |
|
There are several possible options, including this PR itself. In my opinion the best solution in the short term is to transform the In the long term it would make sense to just stop using non-standard definitions ( |
|
|
|
I am fine with explicitly defining |
|
I think we can revert to using |
This reverts commit acb0c4b.
|
I just reverted my initial commit and defined |
|
Here's an approach I would consider taking: |
|
See #38 for an alternative approach. |
|
I'll close this in favor of #38 |
I changed
<cmath>to<math.h>in order to consistently activate the_USE_MATH_DEFINESsymbols such asM_PIwhen compiling a complete windows stack workspace, such as ROS2.0The reason for opening this PR is that when building the ROS2.0 workspace on Windows, this package fails with
M_PIsymbols not being defined. The problem is thatcmathdifferent frommath.hdoes only once check whether the math symbols are activated. If something higher in the pipeline overwrites these definitions,cmathgets built wo/ these symbols.see this stackoverflow thread for more information.