headers
nafiton smith | 1 Mar 2004 12:57

Re: Compiling freetype on uclinux

hello

Werner LEMBERG wrote:

>>And this last warning about _start symbol is really suspicious,
>>isn't it?  Any idea?
>>    
>>
>
>>From the autoconf info file:
>
> - Variable: LDFLAGS
>     Stripping (`-s'), path (`-L'), and any other miscellaneous options
>     for the linker.  Don't use this variable to pass library names
>     (`-l') to the linker, use `LIBS' instead.  If it is not set in the
>     environment when `configure' runs, the default value is empty.
>     `configure' uses this variable when linking programs to test for
>     C, C++ and Fortran 77 features.
>
>The same can be found in the libtool info file.
>
>Additionally, you shouldn't do
>
>  LDFLAGS=... CFLAGS=... ./configure
>
>but
>
>  ./configure LDFLAGS=... CFLAGS=...
>
>also according to the autoconf info file.
(Continue reading)

Permalink | Reply | 8 comments |
headers
Werner LEMBERG | 1 Mar 2004 13:42
Picon

Re: Compiling freetype on uclinux


> configure: warning: CFLAGS=-v  -O2 -D__uClinux__ 
> -I/home/nafi/uClinux-dist/lib/uClibc/include 
> -I/home/nafi/uClinux-dist/linux-2.4.x/include -m5307 -Wa,-S -Wa,-m5307 
> -msep-data: invalid host type
> configure: warning: LDFLAGS=-Wl,-elf2flt -Wl,-move-rodata: invalid host 
> type
> configure: error: can only configure for one host and one target at
> a time

You have written

  ./configure CFLAGS="..."  LDFLAGS="..."

haven't you (note the double quotes)?

> Where can I read this auto tools info?  This is a Red Hat Linux, I
> looked for man autoconf, autoconf --help, find -iname *autoconf* and
> at tlpd.org site but I was not able to find that info.  I am walking
> through these files on a change and try steps.

The info pages can be visited with `info' (or with `M-x info' within
Emacs):

  info autoconf

If this doesn't bring you to autoconf.info you probably haven't it
installed.  You should install the most recent version of autoconf,
2.59.
(Continue reading)

Permalink | Reply | 7 comments |
headers
nafiton smith | 1 Mar 2004 18:12

Re: Compiling freetype on uclinux


Werner LEMBERG wrote:

>>configure: warning: CFLAGS=-v  -O2 -D__uClinux__ 
>>-I/home/nafi/uClinux-dist/lib/uClibc/include 
>>-I/home/nafi/uClinux-dist/linux-2.4.x/include -m5307 -Wa,-S -Wa,-m5307 
>>-msep-data: invalid host type
>>configure: warning: LDFLAGS=-Wl,-elf2flt -Wl,-move-rodata: invalid host 
>>type
>>configure: error: can only configure for one host and one target at
>>a time
>>    
>>
>
>You have written
>
>  ./configure CFLAGS="..."  LDFLAGS="..."
>
>haven't you (note the double quotes)?
>
>  
>
Yes, it has the double quotes. I am running it from a script ( I think 
this make no difference, or does it?). And almost works with the 
parameters before ./configure, but it does not work at all with the 
parameters after it.

>>Where can I read this auto tools info?  This is a Red Hat Linux, I
>>looked for man autoconf, autoconf --help, find -iname *autoconf* and
>>at tlpd.org site but I was not able to find that info.  I am walking
(Continue reading)

Permalink | Reply | 6 comments |
headers
Werner LEMBERG | 1 Mar 2004 22:14
Picon

Re: Type1 Font Char -> Bitmap Troubles


> I'm trying to access characters from a type1 font and place them
> into a bitmap ready for drawing and have not been sucessful despite
> reading carefully the glyph guidlines, the tutorial and many bits
> and pieces in the api reference(all of which I found were a bit
> ambiguous/inadequate towards what I'm trying to accomplish).

I don't have time to analyze your code.  What I can suggest is to
follow the demo programs in the ft2demos bundle (which even have a
BeOS front end).  And please use the current CVS (or a daily snapshot)
which will become soon (so I hope) a new release.

    Werner
Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 1 Mar 2004 23:48
Picon

Re: Compiling freetype on uclinux

> >You have written
> >
> >  ./configure CFLAGS="..."  LDFLAGS="..."
> >
> >haven't you (note the double quotes)?
>

> Yes, it has the double quotes. I am running it from a script ( I
> think this make no difference, or does it?).

It makes a difference if you use the Freetype's top-level configure
wrapper (instead of the real configure script in builds/unix).  Then
you have to protect the arguments like this

  ./configure CFLAGS="\"...\""  LDFLAGS="\"...\""

Sorry for not mentioning it.

> It is 2.53 autoconf here. So, no info. I will try an update. Can this be 
> the problem with the parameter order?

No.  Note that the `autoconf' package is only used to create configure
scripts, not to execute it.  With other words, it is a developer
tool.  Anyway, the autoconf documentation provides a lot of tips how
to write portable shell scripts, which programs work strange for a
given platform, etc.

    Werner
Permalink | Reply | 5 comments |
headers
nafiton smith | 2 Mar 2004 10:17

Re: Compiling freetype on uclinux

Hello

Werner LEMBERG wrote:

>>>You have written
>>>
>>> ./configure CFLAGS="..."  LDFLAGS="..."
>>>
>>>haven't you (note the double quotes)?
>>>      
>>>
>
>  
>
>>Yes, it has the double quotes. I am running it from a script ( I
>>think this make no difference, or does it?).
>>    
>>
>
>It makes a difference if you use the Freetype's top-level configure
>wrapper (instead of the real configure script in builds/unix).  Then
>you have to protect the arguments like this
>
>  ./configure CFLAGS="\"...\""  LDFLAGS="\"...\""
>
>Sorry for not mentioning it.
>  
>
I protected the arguments, but it keeps failing (doing it before or 
after the configure call). But I fear I must be missing something more
(Continue reading)

Permalink | Reply | 4 comments |
headers
Torgeir Veimo | 2 Mar 2004 13:04
Picon
Favicon

Re: [Devel] rendering bug reintroduced in freetype 2.1.7

On Mon, 2004-03-01 at 23:31 +0100, Werner LEMBERG wrote:

> > Here's a fix which restores the rendering as it was in 2.1.4;
> > 
> > --- src/pshinter/pshglob.c      2004-02-05 15:31:55.893371707 +0000
> > +++ src/pshinter/pshglob.c-orig 2004-02-05 15:29:16.757977331 +0000
> >  <at>  <at>  -663,7 +663,7  <at>  <at> 
> >            read++;
> >          }
> >   
> > -        dim->stdw.count = write - dim->stdw.widths; 
> > +        dim->stdw.count = priv->num_snap_heights;
> >        }
> >   
> >        /* copy blue zones */
> > 
> > I'm not qualified to say what is really happening here. 
> 
> I've meanwhile committed a similar fix (among other small
> improvements):
> 
>   dim->stdw.count = priv->num_snap_heights + 1;
> 
> Please test.

o's and i's look very nice now. Not just the stem width is correct, but
rendering in general seems to be improved somewhat. Compare with 2.1.3
here (subpixel antialiasing);

http://nothome.com/freetype2.1.3.png
(Continue reading)

Permalink | Reply | 0 comments |
headers
John Hunter | 2 Mar 2004 17:19

text appears clipped on small rasters


When I render characters at small raster sizes (eg 80 dpi, 12 point),
the right hand side of the character often appears as if it has been
clipped off.  I suspect I am not handling something properly.

Below is code modified from example1.c in the tutorial that
illustrates the problem.  When I print the raster for "0" to a string
with show image, I get

  0   0   0   0   0   0   0   0   0   0
  0   0   0   0   0   0   0   0   0   0
  0  10 160 240 233 128   0   0   0   0
  0 149 191  13  28 221  98   0   0   0
  4 243  68   0   0 112 197   0   0   0
 37 255  21   0   0  66 243   0   0   0
 49 255  10   0   0  54 255   1   0   0
 37 255  21   0   0  66 243   0   0   0
  4 243  67   0   0 112 198   0   0   0
  0 150 189  13  28 221  98   0   0   0
  0  10 161 240 234 129   0   0   0   0
  0   0   0   0   0   0   0   0   0   0
  0   0   0   0   0   0   0   0   0   0

                              ^
                  raster appears clipped here

I ran this code with Vera.ttf.

Any advice?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Werner LEMBERG | 2 Mar 2004 23:43
Picon

Re: Compiling freetype on uclinux

> I untar the downloaded file and run the configure through this
> script that I put on the untarred directory root:

I've modified your script, see below.  It works on my GNU/Linux box.
Please try again.

    Werner

======================================================================

#!/bin/sh
rm -f config.cache config.status
CC="m68k-elf-gcc"
CFLAGS="-O2 -D__uClinux__ \
        -I/home/nafi/uClinux-dist/lib/uClibc/include \
        -I/home/nafi/uClinux-dist/linux-2.4.x/include \
        -m5307 -Wa,-S -Wa,-m5307 -msep-data"
LDFLAGS="-Wl,-elf2flt -Wl,-move-rodata \
         -L/home/nafi/uClinux-dist/lib/uClibc/lib"
LIBS="-lc"
CONFIG="--prefix=/home/nafi/uClinux-dist/libfreetype \
        --build=i386-linux \
        --host=m68k-elf-linux \
        --target=m68k-elf-linux \
        --disable-nls \
        --enable-static"

./configure $CONFIG \
            CC=\"$CC\" \
            CFLAGS=\"$CFLAGS\" \
(Continue reading)

Permalink | Reply | 3 comments |
headers
nafiton smith | 3 Mar 2004 11:39

Re: Compiling freetype on uclinux


Werner LEMBERG wrote:

>>I untar the downloaded file and run the configure through this
>>script that I put on the untarred directory root:
>>    
>>
>
>I've modified your script, see below.  It works on my GNU/Linux box.
>Please try again.
>
>
>    Werner
>
>======================================================================
>
>#!/bin/sh
>rm -f config.cache config.status
>CC="m68k-elf-gcc"
>CFLAGS="-O2 -D__uClinux__ \
>        -I/home/nafi/uClinux-dist/lib/uClibc/include \
>        -I/home/nafi/uClinux-dist/linux-2.4.x/include \
>        -m5307 -Wa,-S -Wa,-m5307 -msep-data"
>LDFLAGS="-Wl,-elf2flt -Wl,-move-rodata \
>         -L/home/nafi/uClinux-dist/lib/uClibc/lib"
>LIBS="-lc"
>CONFIG="--prefix=/home/nafi/uClinux-dist/libfreetype \
>        --build=i386-linux \
>        --host=m68k-elf-linux \
>        --target=m68k-elf-linux \
(Continue reading)

Permalink | Reply | 2 comments |

Gmane