Sorry, my fault, fix in https://codereview.qt-project.org/c/qt/qtbase/+/737194 
. But I think that will not help to fix the git history which still contains 
those lfs objects.

—Liang

Sent from Outlook for Mac


Confidential

From: Albert Astals Cid <[email protected]>
Date: Wednesday, 20 May 2026 at 10:01
To: [email protected] <[email protected]>
Cc: Liang Qi <[email protected]>
Subject: Re: [Development] Long live Qt for HarmonyOS!

El divendres, 15 de maig del 2026, a les 19:21:05 (Hora d’estiu d’Europa 
central), Liang Qi via Development va escriure:
> Hi, all,
>
> With [change 733351 in Qt Gerrit][1] now merged into the dev branch of
> qtbase, along with several other changes merged into the qt5 dev branch
> (see [the harmonyos_upstream topic][2]), qtbase dev now supports building
> on HarmonyOS 6.0.0 (API Level 20).
>
> If you are interested in building qtbase for HarmonyOS, please refer to the
> [Qt Wiki page][3].
>
> If you encounter any CI/COIN build failures on HarmonyOS in your gerrit
> change and need assistance, please feel free to add me and/or anyone listed
> as an author on the related changes.
>
> Happy hacking!
>
> [1]: https://codereview.qt-project.org/c/qt/qtbase/+/733351
> [2]:
> https://codereview.qt-project.org/q/topic:%22harmonyos_upstream%22+status:m
> erged [3]: https://wiki.qt.io/Building_Qt6_for_HarmonyOS

Is it on purpose that we need to use git lfs now in qtbase?

$ git lfs ls-files
79c27214e4 - src/harmonyos/templates/AppScope/resources/base/media/app_icon.png
3cf4698f02 - 
src/harmonyos/templates/entry/src/main/resources/base/media/background.png
8f9794085c - 
src/harmonyos/templates/entry/src/main/resources/base/media/foreground.png
567c7c0c7a - 
src/harmonyos/templates/entry/src/main/resources/base/media/startIcon.png
53ce1f45f8 - 
src/harmonyos/templates/entry/src/ohosTest/resources/base/media/icon.png

Cheers,
  Albert

>
> Best regards,
> Liang
> Qt for HarmonyOS team
>
>
> Confidential




-- 
Development mailing list
[email protected]
https://lists.qt-project.org/listinfo/development

Reply via email to