ttf-pt-sans_1.1:: Install fonts after target boots#68
Merged
chaitu236 merged 1 commit intoni:nilrt/master/nextfrom Oct 2, 2024
Merged
ttf-pt-sans_1.1:: Install fonts after target boots#68chaitu236 merged 1 commit intoni:nilrt/master/nextfrom
chaitu236 merged 1 commit intoni:nilrt/master/nextfrom
Conversation
chaitu236
requested changes
Oct 2, 2024
chaitu236
left a comment
chaitu236
left a comment
There was a problem hiding this comment.
Please update commit message so it follows 50/72 rule.
Access to the font cache on the target is required to get rid of the font warnings. Signed-off-by: Erick Shepherd <erick.shepherd@ni.com>
erickshepherdNI
force-pushed
the
dev/fix_font_warnings
branch
from
77debab to
d4686b3
Compare
chaitu236
approved these changes
Oct 2, 2024
Shreejit-03
pushed a commit
to Shreejit-03/meta-openembedded
that referenced
this pull request
Feb 23, 2026
Remove patches that have been integrated upstream: - Serial setup handling respecting user intent - POSIX-compliant termios baud rate configuration - Type safety and error handling improvements $ git --no-pager log --oneline 1a81f3c7be08..e3461097252e e3461097252e Merge pull request ni#61 from MaxKrummenacher/master 988deaad893b Merge pull request ni#69 from ivitro/fix/termios-use-cfset-speed 03aae5517cda Merge pull request ni#68 from ivitro/fix-serial-setup-handling e124c19e97e9 Fix -Wstringop-overflow warning in process_write_data 363f569a531f Use cfsetispeed/cfsetospeed for baud configuration 9012c3366433 Fix serial setup handling to respect user intent 8a8aba302529 linux-serial-test.c: fix potential hang in while loop 8a5709984363 linux-serial-test.c: fix returned error code Signed-off-by: Vitor Soares <vitor.soares@toradex.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our base system image build have been throwing multiple warnings about fonts not being able to find configuration files. I believe this is because the build requires access to files, such as the font cache, that are present on the target. Updating the font postinst recipe to run on the target resolves the warnings. The related tech debt item is here: https://dev.azure.com/ni/DevCentral/_workitems/edit/2812142
Testing
Built locally and confirmed there were no font warnings.