Skip to content

resolve undefined symbol OH_NativeWindow_NativeWindowHandleOpt on OpenHarmony#1722

Open
geocapp wants to merge 1 commit into
vsg-dev:masterfrom
geocapp:master
Open

resolve undefined symbol OH_NativeWindow_NativeWindowHandleOpt on OpenHarmony#1722
geocapp wants to merge 1 commit into
vsg-dev:masterfrom
geocapp:master

Conversation

@geocapp

@geocapp geocapp commented Jun 20, 2026

Copy link
Copy Markdown

Description

I am attempting to cross-compile VulkanSceneGraph (vsg v1.1.15) under Windows 11 using the HarmonyOS SDK provided by DevEco Studio 6.1.1. The objective is to run my downstream project vsgPotree(https://github.com/geocapp/vsgPotree.git) on HarmonyOS to support point cloud visualization.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Source Setup: Open vsg v1.1.15 source code using the integrated CMake-GUI inside DevEco Studio.
  • CMake Configuration: Select Ninja as the generator and point to the HarmonyOS SDK toolchain file for cross-compilation.
  • Build Flags: Enable the BUILD_SHARED_LIBS option.
  • Generation: Click "Generate" (the build.ninja compiles successfully).
  • Compilation: Open a terminal in the build directory and execute: cmake --build .

Test Configuration:

  • Host OS: Windows 11
  • IDE & SDK: DevEco Studio 6.1.1 (incorporating HarmonyOS SDK)
  • Library Version: VulkanSceneGraph (vsg) v1.1.15
  • Build System & Toolchain : Integrated CMake-GUI in DevEco Studio
  • Generator : Ninja
  • Key Configurations : BUILD_SHARED_LIBS enabled (checked)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

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