Re: Progress on Mac installation cloning

[Mojca M. <moj...@gm...>]

On 3 March 2016 at 22:50,  <pl...@pi...> wrote:
>
> Firstly there are two ways to get PNG et co. : the older gdlib which you
> probably don't need to use now ; and whatever is already on the system
> for png/jpeg etc which is certainly already part of a basic MacOSX system.

It is not.

I happen to have
   /usr/X11/lib/libpng.dylib
(which probably came with X11 and might be missing on the student's
computer), but jpeg, pango, cairo etc. are certainly missing.

>
> for example my linux system shows this as part of the output from
> ./configure :
>
>    libgd-based png, jpeg, and gif terminals: no (see config.log)
>    cairo-based pdf and png terminals: yes
>
> What I think you are missing are the header files which are probably not
> installed by default. The configure script is looking for headers (
> sometimes the package has -devel added to the name )  , I'm not sure of
> the conventions for Mac packages.
>
> You probably need to install cairo and pango headers.

If he wants to use pango and cairo, he has to install them manually
from source. There are no -devel packages to be found anywhere (except
in third-party package managers that he wants to avoid). In the same
way he has to compile libpng, libjpeg and others from source.

> The 32b , 64b issue is something else. As I previously said you are
> trying to cross-compile here which means you will at least need the
> TARGET system header files available to the configure script.

No, he can use the same header files (and even the same libraries if
he sets the CFLAGS/CXXFLAGS properly), but that's beyond the scope of
this discussion.

> I suggest you master the first part and worry about that later.

Indeed. (I wouldn't even bother making 32-bit binaries at all.)

Mojca