Skip to content

Fix missing dependencies in MAVSDKConfig.cmake.in#2658

Merged
julianoes merged 1 commit intomainfrom
fix-cmake-config
Sep 23, 2025
Merged

Fix missing dependencies in MAVSDKConfig.cmake.in#2658
julianoes merged 1 commit intomainfrom
fix-cmake-config

Conversation

@JonasVautherin
Copy link
Copy Markdown
Collaborator

Aren't those missing? 🤔

@sonarqubecloud
Copy link
Copy Markdown

@julianoes
Copy link
Copy Markdown
Collaborator

Hm, presumably. I don't usually build that way I think.

@JonasVautherin
Copy link
Copy Markdown
Collaborator Author

Without that I get:

  "mav::MessageSet::addFromXMLString(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, bool)", referenced from:
      mavsdk::MavsdkImpl::MavsdkImpl(mavsdk::Mavsdk::Configuration const&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
      mavsdk::MavsdkImpl::MavsdkImpl(mavsdk::Mavsdk::Configuration const&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
      mavsdk::MavsdkImpl::MavsdkImpl(mavsdk::Mavsdk::Configuration const&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
      mavsdk::MavsdkImpl::MavsdkImpl(mavsdk::Mavsdk::Configuration const&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
      mavsdk::MavsdkImpl::load_custom_xml_to_message_set(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::BufferParser::BufferParser(mav::MessageSet const&)", referenced from:
      std::__1::unique_ptr<mav::BufferParser, std::__1::default_delete<mav::BufferParser>> std::__1::make_unique[abi:nn200100]<mav::BufferParser, mav::MessageSet&, 0>(mav::MessageSet&) in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::MessageSet::idForMessage(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const", referenced from:
      mavsdk::MavsdkImpl::message_name_to_id_safe(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::MessageSet::getMessageDefinition(int) const", referenced from:
      mavsdk::MavsdkImpl::message_id_to_name_safe(unsigned int) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
      mavsdk::MavsdkImpl::get_message_definition_safe(int) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::MessageSet::create(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const", referenced from:
      mavsdk::MavsdkImpl::create_message_safe(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::BufferParser::parseMessage(unsigned char const*, unsigned long, unsigned long&) const", referenced from:
      mavsdk::MavsdkImpl::parse_message_safe(unsigned char const*, unsigned long, unsigned long&) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
  "mav::MessageDefinition::fieldNames() const", referenced from:
      mavsdk::LibmavReceiver::libmav_message_to_json(mav::Message const&) const in libmavsdk.a[32](libmav_receiver.cpp.o)
  "mav::Message::getAsNativeTypeInVariant(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) const", referenced from:
      mavsdk::LibmavReceiver::libmav_message_to_json(mav::Message const&) const in libmavsdk.a[32](libmav_receiver.cpp.o)
  "mav::FieldType::baseSize() const", referenced from:
      mav::MessageResult mav::Message::get<unsigned char>(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&, unsigned char&, int) const in libmavsdk.a[17](mavsdk_impl.cpp.o)
      unsigned char mav::Message::_readSingle<unsigned char>(mav::Field const&, int) const in libmavsdk.a[17](mavsdk_impl.cpp.o)

@julianoes julianoes merged commit 5c85bce into main Sep 23, 2025
54 checks passed
@julianoes julianoes deleted the fix-cmake-config branch September 23, 2025 21:55
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 this pull request may close these issues.

2 participants