-
Notifications
You must be signed in to change notification settings - Fork 381
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated perfetto's GN build files to support traced compilation in QNX
Created new argument 'is_qnx' to handle all QNX-specific compilation steps in GN build system. Currently, compilation for QNX is only supported via perfetto's standalone builds. Also, updated the perfetto's codebase to avoid running Linux-specific code in QNX. When compiling for QNX the PERFETTO_OS_LINUX flag is still set to keep the QNX build as compatible as possible with the Linux build. With this change, one can build the QNX target of traced by compiling with the following args.gn file: ''' target_os = "qnx" target_cpu = "arm64" ''' Only arm64 architecture is supported and one needs to setup the QNX developer environment before being able to compile. NOTE: traced_relay compiles but still does not run with this change. Test: tools/ninja -C out/qnx traced traced_relay perfetto Bug: 382283537 Change-Id: I08bd3672a60b69cb92ba87eaeda9cec5b893afbc
- Loading branch information
Jahdiel Alvarez
committed
Dec 11, 2024
1 parent
785e811
commit 61f4b96
Showing
26 changed files
with
227 additions
and
40 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.