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

Failure to generate with castxml for c++11 type within orogen #112

Open
vbargsten opened this issue Dec 7, 2018 · 1 comment
Open

Failure to generate with castxml for c++11 type within orogen #112

vbargsten opened this issue Dec 7, 2018 · 1 comment

Comments

@vbargsten
Copy link

In a ROCK installation, I am using a c++11 type within a struct and get an error such as

In file included from /usr/lib/gcc/x86_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/tuple:35:
    /usr/lib/gcc/x86_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/bits/c++0x_warning.h:32:2: error: This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
    #error This file requires compiler and library support \
     ^
    1 error generated.

when building an orogen component using this type. I found that it works when calling castxml with "-std=c++11". I tried to set TYPELIB_CASTXML_DEFAULT_OPTIONS using export and using Autobuild's package.define method, but the option is not respected. Hard-coding the option into typelibs ruby bindings for calling castxml works.

@doudou
Copy link
Contributor

doudou commented Dec 7, 2018

Hi @vbargsten. So far, orogen itself has unfortunately no way to specify the C++ standard it should be using on the command line and/or through the orogen file. This would be a welcome addition (hint hint ... ;-))

It will automatically "switch" to C++11 if one of the used libraries (through using_library) uses it and specifies the standard in its pkg-config file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants