Re: Build libfreetype with custom, embedded environment fails
Erich Ente <[email protected]> Tue, 21 Apr 2026 12:27:48 +0200
| Newsgroups | gmane.comp.fonts.freetype.user |
|---|---|
| Message-ID | <CAPykt4asW-BJy4T9WwtzHYkyQYE3_F0JAzMii64uK4o+48tCOw@mail.gmail.com> |
Mewnhile I managed to get it working even with TI's compiler and environment. But it was more some kind of dirty hack, I had to replace the complex macros in fterrdef.h by plain and straight-forward defines such as #define FT_Ok 0x00 #define FT_Err_Ok 0x00 #define FT_Error_Cannot_Open_Resource 0x01 #define FT_Err_Cannot_Open_Resource 0x01 #define FT_Error_Unknown_File_Format 0x02 #define FT_Err_Unknown_File_Format 0x02 With them, with the related prefixes corrected in different modules and by adding some explicit includes such as stdint.h it now compiles properly. Functional testign is still pending... Am Sa., 4. Apr. 2026 um 08:02 Uhr schrieb Werner LEMBERG <[email protected]>: > > > thank you for your feedback. Unfortunately the problem here is, I > > can use neither configure nor make. so whatever these scripts are > > doing and defining in the compile-environment, has to be done > > manually. And here it seems I miss something dramatically important > > - resulting in the errors described above... > > Sorry for the late reply; the mail server of gnu.org was under attack > the last few days, and only now the pending e-mails are sent out. > > Have you had a look into the various `docs/INSTALL.*` files? The > document `INSTALL.ANY` should cover your use case. Note, however, > that the files might be slightly out of date. If you encounter > problems please report them here. > > > Werner >