RE: Building a static/standalone binary for ft-demos

[Anurag Thakur]

Thanks for the help Werner

While I could not get it to work that way because of problems with other shared 
libraries, I did manage to achieve what I needed.

I simply compiled freetype and ft-demos in termux directly without the PRoot 
environment and those binaries worked just fine under adb shell.

So, now that I can profile my code on arm64 as well, I will begin work on the 
tasks for Phase 1, starting with adding cmake and meson support to the `dense` 
module.

(Sample `simpleperf` output files attached) 

Regards
Anurag



-----Original Message-----
From: Werner LEMBERG <wl@gnu.org> 
Sent: Wednesday, May 31, 2023 11:54 AM
To: Anurag Thakur <anurag105csec21@bpitindia.edu.in>
Cc: freetype-devel@nongnu.org
Subject: Re: Building a static/standalone binary for ft-demos

> [...] Doing
>
> `$ ldd freetype-demos/bin/.libs/ftbench`
>
> Reports:
>
> `CANNOT LINK EXECUTABLE "linker64": library "libpng16.so.16" not
> found: needed by main executable`
>
> From what I understand it is because the libpng library is dynamically 
> linked but isn't available in the environment.
>
> I want to know if there is any way to build these executables 
> statically so that they can work in a standalone manner and not be 
> dependent on the environment.

I don't know this environment, but I guess the 'hard way' works:
Compile 'libpng' as a static library and make sure that `libpng16.so.16` isn't 
found during compilation; this should enforce the compiler to take the static 
library instead.


    Werner

report.txt
Description: report.txt

stat.txt
Description: stat.txt