gltt-devel Mailing List for GLTT
Brought to you by:
gerard
Menu
▾
▴
gltt-devel — For developers. Discussion of patches, new functionality, etc.
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Anton <hic...@ma...> - 2010-02-13 03:42:07
|
Hello, Anton Demidov has added you as a friend on the website VK.com VK.com is a website that helps dozens of millions of people find their old friends, share photos and events and always stay in touch. You can log in and view your friends` pages using this link: http://vk.com/reg65892119 Good luck! |
|
From: Gerard L. <ger...@ya...> - 2001-11-12 20:27:20
|
--- Ross Golder <ro...@go...> wrote: > I have been looking into adding automake/autoconf support to the OpenGC > project, which uses gltt. I would like to help gltt improve it's > autoconf/automake scripts so that gltt can more easily be built and > installed as a seperate library, with the header files and shared > libraries all layed out in the right place, to make developing > applications that depend on gltt easier. > ... > Please let me have your comments. GREAT! Can you send me a 2.5.1 .tar.gz? .rpm too, if you want. I'll put them up on the GLTT download page. > > Also, is there a CVS repository somewhere? No. But I'm not making any modifications to GLTT, so there is no merging to worry about. -Gerard __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com |
|
From: Ross G. <ro...@go...> - 2001-11-10 16:49:17
|
I have been looking into adding automake/autoconf support to the OpenGC project, which uses gltt. I would like to help gltt improve it's autoconf/automake scripts so that gltt can more easily be built and installed as a seperate library, with the header files and shared libraries all layed out in the right place, to make developing applications that depend on gltt easier. I have had several problems using the released gltt_2_5.tar.gz file under RedHat 7.2 without applying some fixes from another OpenGC developer, plus my own extensions to the acinclude.m4 code for locating the freetype headers and libraries. I've attached the patch I've used to get it to build correctly so far, plus the other files. Some of it is my work, some of it is the work of others. The result of including the attached files is that you can do the following : $ ./autogen.sh --prefix=/usr (runs aclocal; autoconf; automake etc) $ make dist (produces gltt-2.5.1.tar.gz) For RedHat users: $ rpm -ta gltt-2.5.1.tar.gz (produces gltt-2.5.1.*.rpm) Please let me have your comments. Also, is there a CVS repository somewhere? -- Ross |
|
From: Gerard L. <ger...@ya...> - 2001-02-13 22:20:56
|
--- David A Bagley <ba...@tu...> wrote: > Hi > > I maintain xlock and use gltt to compile and link in the text3d mode. > > I always had trouble using CC (SunC++) to build xlock with this mode. > Building gltt with CC (instead of g++) solves this. Many years ago, I had the identical problem with Irix CC vis g++. Also, the autoconf/libtool was so badly broken on Irix 6.2 that I just plain bailed out and wrote my own makefile by hand. Not a big deal at all. > Here are the steps > that > worked for me (there are probably better ways): > > configure --with-ttf-includes=/usr/openwin/include/freetype > --with-ttf-libraries=/usr/openwin/lib > (I dropped FreeType 1.3.1 in /usr/openwin) > change g++ reference in generated Makefile to CC > change .la references to .a in Makefile to produce a libgltt.a > remove -Wall to get rid of warnings in Makefile > change compiler_o_lo="no" for libtool > remove -fPIC to get rid of warnings in libtool So, are you using CC but still using libtool, or are you bypassing libtool altogether? Just curious. > I would be interested in a gltt for FreeType 2.0. I was going to > see what was involved in converting but You're the second person in the last 3 months to ask about this. I'm curious myself to know how much work is involved. From my initial browse of the FT 2.0 API, it appears that the new API is somewhat more simplified than before. That's good news. The bad news is that the API is different enough to require a substantial re-write of GLTT. Is there some functionality in FT 2.0 that you are particularly interested in? Stephane Rehel's coding style leaves much to be desired. Consider yourself warned! > http://www.freetype.org/ always refuses my connections. Try http://freetype.sourceforge.net/, and follow the link through to get to http://freetype.sourceforge.net/old_index.html Those work for me - I just tried them. A word of warning: The SourceForge/GeoCrawler list archiving system is notoriously unreliable. If you received an email from any of the GLTT mailing lists, and you think it is something important, you should save it off on your system for future reference. If anyone has a suggestion for a more reliable host for the mailing lists, please let me know! -Gerard __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
|
From: David A B. <ba...@tu...> - 2001-02-13 21:07:36
|
Hi
I maintain xlock and use gltt to compile and link in the text3d mode.
I always had trouble using CC (SunC++) to build xlock with this mode.
Building gltt with CC (instead of g++) solves this. Here are the steps that
worked for me (there are probably better ways):
configure --with-ttf-includes=/usr/openwin/include/freetype --with-ttf-libraries=/usr/openwin/lib
(I dropped FreeType 1.3.1 in /usr/openwin)
change g++ reference in generated Makefile to CC
change .la references to .a in Makefile to produce a libgltt.a
remove -Wall to get rid of warnings in Makefile
change compiler_o_lo="no" for libtool
remove -fPIC to get rid of warnings in libtool
I would be interested in a gltt for FreeType 2.0. I was going to see what was
involved in converting but http://www.freetype.org/ always refuses my
connections.
--
Cheers,
/X\ David A. Bagley
(( X ba...@tu... http://www.tux.org/~bagleyd/
\X/ xlockmore and more ftp://ftp.tux.org/pub/tux/bagleyd
|
|
From: Gerard L. <ge...@la...> - 2000-12-20 02:55:21
|
It took several tries, but I got GeoCrawler to fix the list archives. -Gerard |
|
From: Gerard L. <ger...@ya...> - 2000-11-21 23:52:51
|
[Test #2] The archive system may or may not be functioning properly. Sometimes it is necessary to have one or more messages in the archive in order for the archive to be accessible. This is a test message to verify that the message archives are working properly. -Gerard __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ |
|
From: Gerard L. <ger...@ya...> - 2000-11-21 19:56:02
|
The archive system may or may not be functioning properly. Sometimes it is necessary to have one or more messages in the archive in order for the archive to be accessible. This is a test message to verify that the message archives are working properly. -Gerard __________________________________________________ Do You Yahoo!? Yahoo! Shopping - Thousands of Stores. Millions of Products. http://shopping.yahoo.com/ |
|
From: Christophe T. <ch....@co...> - 2000-11-01 23:32:14
|
Hello folks. I'd like to comment on the tweak to compile gltt under RH 7.0, since I ran into the problem myself. Gerard had to make the following change to compile under RH7.0: diff GLTTGlyphPolygonizer.C /usr/local/src/gltt-2.5/ 184c184,185 < typedef void CALLBACK (*glu_callback)(CALLBACKARG); --- > typedef void (*glu_callback)(); > // typedef void CALLBACK (*glu_callback)(CALLBACKARG); As you may know, RedHat has made a highly controversial move by shipping a new version of gcc (actually the snapshot of a work in progress) with the 7.0 distribution. It is labeled "2.96". This had the sad effect, among other things, to break a lot of C++ code around. However, given the large base of RedHat users, we may want that those who want can compile gltt effortlessly, while at the same time keeping people using another compiler happy. The problem would have surfaced at one time or another anyway, with the upcoming of the new gcc compiler. So, I would (humbly) suggest to alter the conditional around CALLBACKARG, as shown by the patch at the end of this message. Best regards, PS: I'm heading to Asia for two weeks, so I may not respond to my emails soon. -- Christophe Tronche ch....@co... marchFIRST (France) http://tronche.com/ ====================================================================== --- gltt-2.5/GLTTGlyphPolygonizer.C Sun Nov 21 02:04:43 1999 +++ gltt-2.5-new/GLTTGlyphPolygonizer.C Thu Nov 2 00:03:56 2000 @@ -107,7 +107,7 @@ #endif // IMHO, the (...) vs. (void) warning is due to GNU-C/C++. -#if defined(__GNUC__) || defined(_GNUG_) +#if (defined(__GNUC__) || defined(_GNUG_)) && !__GNUC_PREREQ(2,96) #define CALLBACKARG ... #else #define CALLBACKARG void |
