xcbeautify icon indicating copy to clipboard operation
xcbeautify copied to clipboard

The cause duplicate symbols is not completly displayed.

Open blastmann opened this issue 1 year ago • 5 comments

First I use xcodebuild to build my project, duplicated symbols are displayed with full path:

ld: warning: duplicate symbol '_ZSTD_copyCCtx' in:
    /Volumes/test_result/Build/Products/DailyBuild-iphonesimulator/XCFrameworkIntermediates/Btts/libbtts.a(zstd_compress.o)
    /Volumes/est_result/Build/Products/DailyBuildiphonesimulator/XCFrameworkIntermediates/Diagnose/DefaultLogger/mars.framework/mars(zstd_compress.c.o)

I use xcbeautify to filter my xcodebuild logs like below:

set -o pipefail && xcodebuild build-for-testing -workspace xxx -quiet | xcbeautify -qq


❌ duplicate symbol '_ZSTD_copyCCtx' in
❌ duplicate symbol '_ZSTD_getCParams' in

Only symbol name is printed. That's not easy to findout where are the duplicated objects.

I think it is a bug.

blastmann avatar Sep 27 '23 08:09 blastmann

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable. If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future. Thank you for your understanding.

github-actions[bot] avatar Oct 28 '23 01:10 github-actions[bot]

Hola 👋,

We want to inform you that we have decided to close this stale issue as there hasn't been any activity or response regarding it after marking it as stale.

We understand that circumstances may have changed or priorities may have shifted, and that's completely understandable. If you still believe that this issue needs to be addressed, please feel free to reopen it and provide any necessary updates or additional information.

We appreciate your understanding and look forward to your continued contributions to the project.

Thank you.

github-actions[bot] avatar Nov 02 '23 01:11 github-actions[bot]

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable. If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future. Thank you for your understanding.

github-actions[bot] avatar Dec 12 '23 02:12 github-actions[bot]

Hola 👋,

We want to inform you that we have decided to close this stale issue as there hasn't been any activity or response regarding it after marking it as stale.

We understand that circumstances may have changed or priorities may have shifted, and that's completely understandable. If you still believe that this issue needs to be addressed, please feel free to reopen it and provide any necessary updates or additional information.

We appreciate your understanding and look forward to your continued contributions to the project.

Thank you.

github-actions[bot] avatar Dec 18 '23 01:12 github-actions[bot]

Hola 👋,

We want to inform you that the issue has been marked as stale. This means that there hasn't been any activity or updates on it for quite some time, and it's possible that it may no longer be relevant or actionable. If you still believe that this issue is valid and requires attention, please provide an update or any additional information that can help us address it. Otherwise, we may consider closing it in the near future. Thank you for your understanding.

github-actions[bot] avatar Jan 26 '24 01:01 github-actions[bot]