headers
NightStrike | 3 Sep 2009 00:27
Picon

[ft] freetype2 and Win64

While compiling freetype2 for Win64 to meet a VLC dependency, I
encounter these warnings:

configure: WARNING: unrecognized options: --enable-msw,
--disable-dependency-tracking
configure: WARNING: unrecognized options: --enable-msw,
--disable-dependency-tracking
In file included from
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cff.c:26:0:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:
In function ‘cff_decoder_parse_charstrings’:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:866:12:
warning: cast from pointer to integer of different size
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:867:12:
warning: cast from pointer to integer of different size
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:868:12:
warning: cast from pointer to integer of different size
In file included from
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdf.c:30:0:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:
In function ‘bdf_create_property’:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:1006:35:
warning: cast to pointer from integer of different size
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:
In function ‘bdf_get_property’:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:1031:14:
warning: cast from pointer to integer of different size
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:
In function ‘_bdf_add_property’:
/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/bdf/bdflib.c:1276:26:
(Continue reading)

Permalink | Reply | 13 comments |
headers
mpsuzuki | 3 Sep 2009 04:03
Picon

Re: [ft] freetype2 and Win64

Hi,

Thank you for poining out the warning on Win64 platform
and the analysis. I want to take a look, could you give
me the information about your development environment to
reproduce this issue? The messages you see look like by
gcc.

I've ever worked for a few LP64 systems of Unix and Mac
OS X, but never worked for Win64.

Regards,
mpsuzuki

On Wed, 2 Sep 2009 18:27:22 -0400
NightStrike <nightstrike <at> gmail.com> wrote:

>While compiling freetype2 for Win64 to meet a VLC dependency, I
>encounter these warnings:
>
>configure: WARNING: unrecognized options: --enable-msw,
>--disable-dependency-tracking
>configure: WARNING: unrecognized options: --enable-msw,
>--disable-dependency-tracking
>In file included from
>/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cff.c:26:0:
>/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:
>In function ‘cff_decoder_parse_charstrings’:
>/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:866:12:
>warning: cast from pointer to integer of different size
(Continue reading)

Permalink | Reply | 3 comments |
headers
NightStrike | 3 Sep 2009 04:29
Picon

Re: [ft] freetype2 and Win64

I'm using a linux64 to win64 cross compiler available here:

https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/mingw-w64-bin_x86_64-linux_20090902.tar.bz2/download

From this page:

https://sourceforge.net/projects/mingw-w64/files/

This is the mingw-w64 sf project of which I am an administrator.

This is with a GCC 4.5 toolchain (built off of GCC HEAD and binutils HEAD).

Mostly, warnings like this just require casting the pointer into an
intptr_t type instead of a long, which is a more portable way of doing
things.  Your setup, however, requires changing your own internal
typedef, which seems to be used for more than just capturing pointers.
 It seems to be somewhat overloaded in its purpose.

We are always active on irc://irc.oftc.net/#mingw-w64 if you'd like to
join.  A web based client is on the sf website:

http://mingw-w64.sourceforge.net/mibbit.html

2009/9/2  <mpsuzuki <at> hiroshima-u.ac.jp>:
> Hi,
>
> Thank you for poining out the warning on Win64 platform
> and the analysis. I want to take a look, could you give
> me the information about your development environment to
> reproduce this issue? The messages you see look like by
(Continue reading)

Permalink | Reply | 2 comments |
headers
mpsuzuki | 3 Sep 2009 07:20
Picon

Re: [ft-devel] Re: [ft] Re: Few typefaces are not loading

I thank Dmitry for guiding Noorul to right place, while
I was off line.

On Sat, 29 Aug 2009 12:41:39 +0530
Noorul Sahabudeen <noorulsahabudeen.cg <at> gmail.com> wrote:
>Windings works fine with FT_ENCODING_MS_SYMBOL, but is there any simple 
>way to set the default style that font supports and load the charmapa, 
>Because i dont' know anything about these encoding styles ans stuffs.

Before all, FreeType2 tries to provide Unicode character
interface by default, for convenience of the programmers.
"Unicode by default" is not perfect solution, but the most
generic solution especially for TrueType. More generic-but-
hardheaded solution would be "no cmap is loaded by default",
but I don't think it's welcomed in today, except of die-hard
programmers with Code Set Independent style.

With keeping "Unicode by default" feature, the automatic
determination of cmap is quite difficult, because most of
non-Unicode cmap of TrueType is incompatible with Unicode
(e.g. CJK encodings and Apple WorldScript encodings for
Arabic/Hebrew/Indic etc). Some people may request the
encoding convertor (something like iconv()) behind of FT2
API, but there's no compact, portable, generic library
with appropriate license to be included in FT2. FT2 user
should select the best encoding convertor fitting their
own purpose.

Even if a genius could write encoding convertor for FT2,
the problem of MS Symbol cannot be solved. MS Symbol encoding
(Continue reading)

Permalink | Reply | 0 comments |
headers
mpsuzuki | 3 Sep 2009 07:39
Picon

Re: [ft] freetype2 and Win64

Thank you for info.

It seems that now precompiled binaries of mingw-w64
for 32-bit Linux platform are not provided (the last
binaries are released on 2009-06-04). I will compile
the toolchain from source package, please wait one week
or so.

Regards,
mpsuzuki

On Wed, 2 Sep 2009 22:29:55 -0400
NightStrike <nightstrike <at> gmail.com> wrote:

>I'm using a linux64 to win64 cross compiler available here:
>
>https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Automated%20Builds/mingw-w64-bin_x86_64-linux_20090902.tar.bz2/download
>
>From this page:
>
>https://sourceforge.net/projects/mingw-w64/files/
>
>This is the mingw-w64 sf project of which I am an administrator.
>
>This is with a GCC 4.5 toolchain (built off of GCC HEAD and binutils HEAD).

>2009/9/2  <mpsuzuki <at> hiroshima-u.ac.jp>:
>> Hi,
>>
>> Thank you for poining out the warning on Win64 platform
(Continue reading)

Permalink | Reply | 1 comment |
headers
NightStrike | 3 Sep 2009 07:54
Picon

Re: [ft] freetype2 and Win64

Yes, unfortunately, our build slaves for that platform are down.  The
machine kept over heating :)

You may find it much easier to use this makefile:

http://mingw-w64.svn.sourceforge.net/viewvc/mingw-w64/experimental/buildsystem/makebuildroot.mk?view=markup

execute it like this:

make -f makebuildrook.mk

It will download the sources and build an entire toolchain for you.

2009/9/3  <mpsuzuki <at> hiroshima-u.ac.jp>:
> Thank you for info.
>
> It seems that now precompiled binaries of mingw-w64
> for 32-bit Linux platform are not provided (the last
> binaries are released on 2009-06-04). I will compile
> the toolchain from source package, please wait one week
> or so.
>
> Regards,
> mpsuzuki
>
> On Wed, 2 Sep 2009 22:29:55 -0400
> NightStrike <nightstrike <at> gmail.com> wrote:
>
>>I'm using a linux64 to win64 cross compiler available here:
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
mpsuzuki | 3 Sep 2009 17:31
Picon

Re: [ft] help with mac build

Hi,

I'm quite sorry for this lated reply. I was almost off line
of this list during last week.

On Fri, 28 Aug 2009 17:57:41 +0200
audioboy 77 <audioboy77 <at> googlemail.com> wrote:
>after spending a lot of time trying and failing to build the lib with make,

Have you read docs/INSTALL.MAC? If so, but you could not build
FT2 library, I'm quite sorry, I made wrong assumption as if all
Mac OS X developer is very very familiar with the conventional
GNU-like software development on Unix. I must improve the document,
please let me know what kind of commands you executed, and
what kind of errors you received.

>i decided to go the route of building the lib manually via an xcode project.
> i made an xcode project and built the library apparently ok.

Umm, I don't use Xcode at all, I have no recommended way to
check the built binary is ok...

>then back in my application project, i included the library - but i have one
>error during linking...
>
>_ATSFontGetFileReference" referenced from:
>_FT_ATSFontGetFileReference in libfreetype.a (ftbase.o)
>
>I really would appreciate it someone can help as i've been struggling for a
>week trying to get this to work, and am basically tearing my hair out...
(Continue reading)

Permalink | Reply | 0 comments |
headers
erik | 6 Sep 2009 01:05
Picon
Favicon

[ft] Freetype in action

I Hope I don't get booted for posting unrelated stuff, but I thought you
guys would like to see what you've been contributing to without knowing it
:)

http://www.timetrap.se/media.php

It's footage from a game I've spent all my free time on the last year and
a half and it's finally finished. Freetype is used to generate all fonts
in the game... as in it doesn't run in the final game, but it's used to
pregenerate content.
Kudos to the maintainers of Freetype... it's a great lib... and you're in
the credits ;)

Cheers,
Erik
Permalink | Reply | 0 comments |
headers
mpsuzuki | 7 Sep 2009 06:02
Picon

Re: [ft] freetype2 and Win64

Hi,

Just I've built Win64 development tools, the problems
you reported are completely reproduced. However, I don't
have the extra licenses/machines to test Win64 binaries.
I will have to ask for your help to finish this issue...

On Wed, 2 Sep 2009 18:27:22 -0400
NightStrike <nightstrike <at> gmail.com> wrote:
>/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:
>In function ‘cff_decoder_parse_charstrings’:
>/home/nightstrike/work/vlc/extras/contrib/src/freetype2/src/cff/cffgload.c:866:12:
>warning: cast from pointer to integer of different size

[snip]

>All of these are related to castings that assume that pointers are the
>size of long.  On this platform, they are not.

Correct. Win64 is LLP64, we cannot calculate the pointer
with unsigned long variables. When I've ever worked for
16-bit and 64-bit systems, I was thinking about ILP64 and
LP64 systems, but I slipped to take LLP64 into account.
It is my error, I'm sorry.

>                                                I looked into some of
>them, and I see for instance this:
>
>  /*************************************************************************/
>  /*                                                                       */
(Continue reading)

Permalink | Reply | 8 comments |
headers
Aya Koshigaya | 7 Sep 2009 22:43
Picon
Favicon

[ft] Scaline for rasterizer?

Hi,

I am using the standalone grays-rasterizer and am passing the outline  
to it.
But... what is the range for the rasterizer?

When I pass a rect with yMin = 0 and yMax = 14660 to it, I get a  
rasterized Rect that has a height of 229px... where is the relation  
between 14660 and 229..? :/

Best regards,
Aya~
Permalink | Reply | 5 comments |

Gmane