nanogui: amd64, freetype and t1lib


Previous by date: 25 May 2011 17:52:16 -0000 mw-0.91 to current tarball, white is blue?, Joseph Lopes
Next by date: 25 May 2011 17:52:16 -0000 Re: Compile with DJGPP or MSC, Georg Potthast
Previous in thread: 25 May 2011 17:52:16 -0000 Re: amd64, freetype and t1lib, Greg Haerr
Next in thread: 25 May 2011 17:52:16 -0000 Re: amd64, freetype and t1lib, sibu xolo

Subject: Re: [nanogui] amd64, freetype and t1lib
From: sibu xolo ####@####.####
Date: 25 May 2011 17:52:16 -0000
Message-Id: <201105251858.54705.sibxol@btconnect.com>

On Sunday 22 May 2011 19:10:17 Greg Haerr wrote:
> : a) cpu -amd64,  64-bit cblfs linux, kernel-2.6.38.2
> 
> Microwindows is 64-bit clean for the nano-X api and
> all nano-X applications, which I assume you're using.
> Win32 applications using older constructs like SetWindowLong
> have some issues with offsets and pointer lengths, but these
> aren't portable in Win32 without modifying the storage to
> always allocate space for 64 bit pointers at all times.  Win32
> apps can be fixed with no modifications by compiling for 32 bits.
> 
> > gcc-4.5.2,
> 
> I haven't tested with this but don't forsee any problems, as most
> changes in gcc are in C++ not C.
> 
> : b) freetype -2.4.4, t1lib-5.1.2.
> 
> T1lib has been tested with that version, and I would think that
> freetype 2.4.4 should run without issues.  The last version
> I tested with was 2.3.12.  Freetype issues arise when their structure
> members change names without introducing a new API, which has
> occured regularly in the 2.2-2.3 series.
> 
> Overall, should be no problems.  Use v0.92 or CVS.
> 
> Regards,
> Greg


Thanks for the advioce.

Here is what I have done so far.-
i)  I downloaded the most recent CVS sources of microwindows.   
ii) I tried building on a computer with these:-
--o/s linux cblfs64-bit 
--CPU  amd64 2 cores 
--compiler gcc-4.5.2, 
--xwindows Xorg-7.6
--vnc libVNCserver{and client}-0.9.8 verified below

root [ /tmp ]# 
root [ /tmp ]# ls /usr/lib/*vnc*
/usr/lib/libvncclient.a   /usr/lib/libvncclient.so.0      
/usr/lib/libvncserver.la    /usr/lib/libvncserver.so.0.0.0
/usr/lib/libvncclient.la  /usr/lib/libvncclient.so.0.0.0  
/usr/lib/libvncserver.so
/usr/lib/libvncclient.so  /usr/lib/libvncserver.a         
/usr/lib/libvncserver.so.0
root [ /tmp ]# 


To build microindows I did he following:-

A)  cp src/Configs/config.x11 src   OR
B)  edit src/config  ( changing /usr/local/lib/libfreetype.a  to 
/usr/lib/libfreetype.a )  THEN
C)  (in either case )  run make   



#-----------------------make ends lile so:-

make[3]: Circular /tmp/microwin-full-snapshot/src/lib/ <- /tmp/microwin-full-
snapshot/src/lib/ dependency dropped.
Compiling demos/vnc/vncviewer/args.c ...
Compiling demos/vnc/vncviewer/rfbproto.c ...
Compiling demos/vnc/vncviewer/sockets.c ...
Compiling demos/vnc/vncviewer/vncviewer.c ...
Compiling demos/vnc/vncviewer/nanox.c ...
make[3]: *** No rule to make target `/tmp/microwin-full-
snapshot/src/lib/libvncauth.a', needed by `/tmp/microwin-full-
snapshot/src/bin/vnc'.  Stop.
make[2]: *** [subdir-/tmp/microwin-full-snapshot/src/demos/vnc/vncviewer/] 
Error 2
make[1]: *** [subdir-/tmp/microwin-full-snapshot/src/demos/vnc/] Error 2


Advice ould be appreciated

Sincerely
Sibu



Previous by date: 25 May 2011 17:52:16 -0000 mw-0.91 to current tarball, white is blue?, Joseph Lopes
Next by date: 25 May 2011 17:52:16 -0000 Re: Compile with DJGPP or MSC, Georg Potthast
Previous in thread: 25 May 2011 17:52:16 -0000 Re: amd64, freetype and t1lib, Greg Haerr
Next in thread: 25 May 2011 17:52:16 -0000 Re: amd64, freetype and t1lib, sibu xolo


Powered by ezmlm-browse 0.20.