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

build error with boost 1.53 #345

Closed
bburas opened this issue May 11, 2024 · 1 comment · Fixed by #346
Closed

build error with boost 1.53 #345

bburas opened this issue May 11, 2024 · 1 comment · Fixed by #346

Comments

@bburas
Copy link

bburas commented May 11, 2024

Trying to build from source on redhat 7.9, boost 1.53, g++ 12.1.1
$ make
Consolidate compiler generated dependencies of target SimpleAmqpClient
[ 9%] Building CXX object CMakeFiles/SimpleAmqpClient.dir/src/BasicMessage.cpp.o
/home/bburas/projects/broker-demo/SimpleAmqpClient/src/BasicMessage.cpp: In member function 'const string& AmqpClient::BasicMessage::ContentType() const':
/home/bburas/projects/broker-demo/SimpleAmqpClient/src/BasicMessage.cpp:77:33: error: 'class boost::optional<std::basic_string >' has no member named 'value'
77 | return m_impl->content_type.value();

alanxz added a commit that referenced this issue May 14, 2024
The library currently claims support for boost 1.47, which does not have
the boost::optional::value API, which BasicProperties has used.

Fixes: #345

Signed-off-by: GitHub <[email protected]>
alanxz added a commit that referenced this issue May 14, 2024
The library currently claims support for boost 1.47, which does not have
the boost::optional::value API, which BasicProperties has used.

Fixes: #345

Signed-off-by: GitHub <[email protected]>
@alanxz
Copy link
Owner

alanxz commented May 14, 2024

Looks like boost::optional::value isn't a part of the API in v1.53. I've added #346, see if this fixes the issue you were having.

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

Successfully merging a pull request may close this issue.

2 participants