Offer pre-compiled Mac (and Linux) versions

[GoogleCodeExporter]

Thanks for creating this programme, it works very well!

However, Macs don't typically have make-tools installed.
So it'd be great if you (or someone) made a pre-compiled
mac version of ttf2eot.

Many thanks in advance.

Original issue reported on code.google.com by akaxakaster@gmail.com on 1 Jul 2009 at 9:24

[GoogleCodeExporter]

I'm trying to, but without any luck right now.

If I ever end up with a usable mac executable I'll let you know.

Best regards
Pedro Fardilha

Original comment by pedro%fa...@gtempaccount.com on 7 Jul 2009 at 12:52

[GoogleCodeExporter]

Thanks, can't wait!

I've tried compiling it on a Mac, but it didn't want to build properly. 
Building it on Linux (on the same machine) 
worked fine though.

Original comment by akaxakaster@gmail.com on 7 Jul 2009 at 1:46

[GoogleCodeExporter]

I managed to compile ttf2eot, and it seems to do something, so here's a built 
executable for Mac OS X 10.5.7.

There were a few warnings though:

g++    -c -o OpenTypeUtilities.o OpenTypeUtilities.cpp
OpenTypeUtilities.cpp: In function ‘bool getEOTHeader(unsigned char*, size_t, 
std::vector<uint8_t, 
std::allocator<uint8_t> >&, size_t&, size_t&, size_t&)’:
OpenTypeUtilities.cpp:197: warning: invalid access to non-static data member 
‘sfntHeader::tables’ of NULL 
object
OpenTypeUtilities.cpp:197: warning: (perhaps the ‘offsetof’ macro was used 
incorrectly)
OpenTypeUtilities.cpp:202: warning: invalid access to non-static data member 
‘sfntHeader::tables’ of NULL 
object
OpenTypeUtilities.cpp:202: warning: (perhaps the ‘offsetof’ macro was used 
incorrectly)
OpenTypeUtilities.cpp:259: warning: invalid access to non-static data member 
‘nameTable::nameRecords’ of 
NULL object
OpenTypeUtilities.cpp:259: warning: (perhaps the ‘offsetof’ macro was used 
incorrectly)
OpenTypeUtilities.cpp:265: warning: invalid access to non-static data member 
‘nameTable::nameRecords’ of 
NULL object
OpenTypeUtilities.cpp:265: warning: (perhaps the ‘offsetof’ macro was used 
incorrectly)
g++    -c -o ttf2eot.o ttf2eot.cpp
g++ -o ttf2eot OpenTypeUtilities.o ttf2eot.o

Original comment by renzwer...@gmail.com on 7 Jul 2009 at 9:53

Attachments:

• ttf2eot

[GoogleCodeExporter]

I added a ttf2eot port to MacPorts so you can install it that way if desired.

Original comment by ryandesi...@gmail.com on 23 Aug 2009 at 9:37

[GoogleCodeExporter]

It compiles and works fine in 10.6.1.   Just converted a ttf.   Worked great.

The build warnings are trivial, and don't affect the function of the binary.

=)

Original comment by john.sla...@me.com on 25 Oct 2009 at 12:11

[GoogleCodeExporter]

What would really be beneficial to web designers would be a nice NSTask-based 
GUI wrapper for the Terminal-
impaired.  Build a .pkg installer to place this binary in /usr/local/bin and an 
app in /Applications and all the 
Dreamweaver kiddos across the world would sing your praises.

In fact, I may take a crack at such a thing myself...  If no one else has any 
interest, and the leaders of this project 
don't mind.

Original comment by john.sla...@me.com on 25 Oct 2009 at 12:19

[GoogleCodeExporter]

how I use the compiled version

Original comment by ooredro...@gmail.com on 12 Jan 2010 at 3:32

[GoogleCodeExporter]

Hi again.

I just tried to use ttf2eot 0.0.2-2 using both the MacPorts and one compiled 
myself.
With some fonts, both gave me the following error:

unknown error parsing input font, m

Does anyone know why this could be happening and what should I do about it?

Thank you!

Original comment by pedro%fa...@gtempaccount.com on 12 Apr 2010 at 4:05

[GoogleCodeExporter]

I had a ton of troubles with the binary as well- the one I compiled gave me all 
kinds of garbage text in Terminal, gave me no oet. Tried the binary provided 
here, gave me a permission denied error. 

Then I found an online ttf to eot converter which works like a charm:
http://www.kirsle.net/wizards/ttf2eot.cgi

Original comment by heather....@gmail.com on 4 Sep 2010 at 8:23

[GoogleCodeExporter]

Heather,

For those like us who got this "garbage text" in the terminal, it's due to the 
lack of  <  >  around the TTF font path. For example, the correct syntax is:

ttf2eot < path/to/some.ttf > output.eot

Original comment by m...@briangonzalez.org on 9 Aug 2012 at 2:16