Re: [ft-devel] a couple of warnings from 2.5.4 with mingw/darwinx

[suzuki toshiya]

Dear Werner,

> is it possible to create a statically linked program for the GUI?

In my understanding, even if it is "hello world" using only standard
I/O, we cannot built statically linked binary on Mac OS X, as far
as we use the genuine SDKs. There is no libc.a :-(

The source of some Carbon libraries (including libc) are disclosed,
so there are (once there were?) experts rebuilding the fundamental
libraries by themselves and provided the archive libraries for statically
linked binary.

However, the libraries working with Mac OS X's native GUI are not
open source, so we could not have the archive libraries of them X-O

There might be possibility that the software running with X window
might be built as a static binary, but I've not tested yet.

> which is *very* annoying.

Fully I agree. I don't know how many I should repeat to express
my sympathy.

Regards,
mpsuzuki

Werner LEMBERG wrote:
>>> It is a bit complicated, but I think in a nutshell it means running
>>> configure with CC="darwinx-gcc -arch ppc -arch i386 -arch x86_64"
>>> [...]
> 
> Thanks to both of you for working on that issue.
> 
> Not related to the bug, I have a question regarding the build process:
> If I cross-compile a program `foo' with those instructions for Darwin,
> is it possible to create a statically linked program for the GUI?
> Using the `mxe' cross compiling environment (which is a wrapper around
> MinGW64), I can e.g. build Qt applications statically on Windows,
> getting just a single binary file without any DLLs.  This is not
> possible if I try to compile on a Mac, which is *very* annoying.
> People might argue that it is against the philosophy of OSX, but for
> small programs like my ttfautohintGUI tool it would be a tremendous
> help if I had a single file and nothing else...
> 
> 
>     Werner