Skip to content

Build failure on QNX with "Dinkum" STL #156

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
muggenhor opened this issue Jun 28, 2017 · 3 comments
Closed

Build failure on QNX with "Dinkum" STL #156

muggenhor opened this issue Jun 28, 2017 · 3 comments
Assignees
Milestone

Comments

@muggenhor
Copy link
Contributor

Attempting to build with the QNX SDK and "Dinkum" C++ standard library implementation results in this compile error:

include/json_spirit/json_spirit_writer_template.h:80:38: error: there are no arguments to 'iswprint' that depend on a template parameter, so a declaration of 'iswprint' must be available [-fpermissive]

That's the result of:

  1. not including the header that defines this function (<wctype.h> on C, <cwctype> on C++)
  2. when using the C++ header: not using this method from the std:: namespace because that's where the C++ standard requires it to be present: http://en.cppreference.com/w/cpp/string/wide/iswprint
@muggenhor muggenhor added this to the v0.4.1 milestone Jun 28, 2017
@muggenhor muggenhor self-assigned this Jun 28, 2017
@mhtouchette
Copy link

Hello,
Since you fixed a bug for qnx support, I'm assuming that you managed to compile and use cucumber-cpp on a qnx target. Any chance you might want to share how you did that?

@muggenhor
Copy link
Contributor Author

muggenhor commented Feb 23, 2018

Hi @mhtouchette. I can confirm that this builds on QNX, as it's part of our company's CI. But after looking at the CI scripts I cannot find any scripts that execute the tests on QNX. It should be possible though, unfortunately I don't have any direct access to QNX hardware myself to try setting this up. More importantly though I lack the development experience for that platform to justify spending time on setting this up here.

@mhtouchette
Copy link

Ok, still good to know that it should be feasible. Thanks!

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

No branches or pull requests

2 participants