Menu
▾
▴
lcd4linux-devel — lcd4linux development team
You can subscribe to this list here.
| 2004 |
Jan
(57) |
Feb
(71) |
Mar
(80) |
Apr
(40) |
May
(49) |
Jun
(20) |
Jul
(3) |
Aug
(9) |
Sep
(8) |
Oct
(2) |
Nov
|
Dec
(11) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(10) |
Feb
(25) |
Mar
(24) |
Apr
(26) |
May
(71) |
Jun
(35) |
Jul
(5) |
Aug
(3) |
Sep
(18) |
Oct
(4) |
Nov
(5) |
Dec
(2) |
| 2006 |
Jan
(50) |
Feb
(12) |
Mar
(7) |
Apr
(24) |
May
(1) |
Jun
(17) |
Jul
(51) |
Aug
(38) |
Sep
(38) |
Oct
(33) |
Nov
(8) |
Dec
(13) |
| 2007 |
Jan
(44) |
Feb
(25) |
Mar
(21) |
Apr
(68) |
May
(52) |
Jun
(24) |
Jul
(17) |
Aug
(12) |
Sep
(4) |
Oct
(14) |
Nov
(1) |
Dec
(3) |
| 2008 |
Jan
(9) |
Feb
(1) |
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(5) |
Oct
(5) |
Nov
(1) |
Dec
|
| 2009 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(21) |
Jun
(5) |
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
(15) |
Feb
(36) |
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(3) |
| 2011 |
Jan
(22) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(25) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2012 |
Jan
(14) |
Feb
(6) |
Mar
(20) |
Apr
(12) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2013 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
(1) |
May
(9) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2014 |
Jan
(1) |
Feb
(1) |
Mar
(3) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
(11) |
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2016 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Stefan K. <ste...@cr...> - 2006-07-17 16:46:25
|
Hi Xavier, Xavier Vello schrieb am 17.07.2006 18:06: > > I think you can use a knoppix live-cd as it contains gcc, autoconf and every > build-dependancy for lcd4linux. I tried it with knoppix 5 - there is no aclocal-1.9. I tried it on the developer-server from fli4l/eisfair - there comes this: make cd . && aclocal-1.9 /usr/share/aclocal/libmcrypt.m4:17: warning: underquoted definition of AM_PATH_LIBMCRYPT run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.in:25: error: Autoconf version 2.59e or higher is required configure.in:25: the top level autom4te: /usr/bin/m4 failed with exit status: 63 aclocal-1.9: autom4te failed with exit status: 63 make: *** [aclocal.m4] Error 63 |
|
From: Xavier V. <ge...@gm...> - 2006-07-17 16:06:30
|
Hello Stefan > is there a linux-live-cd which is able to compile and statically link > lcd4linux for me? > Or would you compile me a serdisplib-enabled lcd4linux binary? I think you can use a knoppix live-cd as it contains gcc, autoconf and every build-dependancy for lcd4linux. -- Xavier Vello <ge...@gm...> Blog : http://gemegik.bulix.org |
|
From: Michael R. <re...@eu...> - 2006-07-17 15:55:00
|
Hi Stefan, > is there a linux-live-cd which is able to compile and statically link > lcd4linux for me? I don't know. > Or would you compile me a serdisplib-enabled lcd4linux binary? Sure I could do so. But why the heck don't you compile yourself? Do you need or have a special setup? bye, Michael -- Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Michael R. <re...@eu...> - 2006-07-17 15:53:45
|
Hi Stefan, > is there a linux-live-cd which is able to compile and statically link > lcd4linux for me? I don't know. > Or would you compile me a serdisplib-enabled lcd4linux binary? Sure I could do so. But why the heck don't you compile yourself? Do you need or have a special setup? bye, Michael -- Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Stefan K. <ste...@cr...> - 2006-07-17 14:02:25
|
Hi, is there a linux-live-cd which is able to compile and statically link lcd4linux for me? Or would you compile me a serdisplib-enabled lcd4linux binary? Regards Stefan |
|
From: Jay C. <jay...@ya...> - 2006-07-14 12:14:54
|
Hence the: > the only problem i can see is how you play nice with > the rest of the system. so i guess you can get keypress from X, if you want command line support you will have to play around with the keymap files __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: antst <an...@ma...> - 2006-07-14 10:03:26
|
Jay Coles wrote: > Glad to see the seg faults are fixed and the input > stuff is a nice supprise > > as far as i know the uinput framework is used for > insernting keypresses, if you want to read them then > you read from the /dev/event interfaces, each one > corrisponding to a specific device. > > using this means that you could prot lcd screen > buttons to do key presses which can then be used by > any other program and then have a module that works > and responds on key presses > > basicaly you could use any button to change the LCD > screen content > > the only problem i can see is how you play nice with > the rest of the system. > Hm...I don't see the way, how it is going to work, when eventX is already used by some program (X server, for example) Anton |
|
From: antst <an...@ma...> - 2006-07-14 09:56:26
|
> Now this sounds like a great idea! > > Q: are there any prerequisites for using uinput? Kernel version? We > should add some checks to configure, I'm afraid.... > I think it is standard in 2.6 kernels. It just should be switched on. (I think on most distros it is default option) "CONFIG_INPUT_UINPUT=y" in ".config" > I don't know anything about the linux's uinput layer, but would it be > possible to use this stuff for all other displays with keys, too? > There's already a generic key handler in lcd4linux, which does nothing > at the moment but emit a debug message "key xy pressed". Should be easy > to integrate the passing to uinput.... > Yes, this can be done, very easy. I'll try to write patch at weekend. > on the other hand, is it possible to "get" generic keypresses from > uinput, too? this way, lcd4linux would benefit from other keys (probably > some unused keys from your keyboard, joystick, ..) > Hm...don't know does it work in back direction :) never thought :) > Thanks again. I know of this problem for months, but couldn't find the > time to hunt it. I moved your signal() to a seperate function > 'thread_destroy()', which is at least a bit less ugly :-) > :)) Anton. |
|
From: Jay C. <jay...@ya...> - 2006-07-13 07:34:37
|
Glad to see the seg faults are fixed and the input stuff is a nice supprise as far as i know the uinput framework is used for insernting keypresses, if you want to read them then you read from the /dev/event interfaces, each one corrisponding to a specific device. using this means that you could prot lcd screen buttons to do key presses which can then be used by any other program and then have a module that works and responds on key presses basicaly you could use any button to change the LCD screen content the only problem i can see is how you play nice with the rest of the system. another usless ramble by: Jay Coles jay...@ya... aka Da_Blitz __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Michael R. <re...@eu...> - 2006-07-13 05:29:10
|
Hi Anton, > There is a patch for G15 driver (CVS) which is Thanks a lot for your contribution! Patch has been applied and checked in. > 1) fix three bugs in the code which were reason for segfaults(arrays > boundaries) Great! Benjamin, does this fix your problems? > 2) add support for extra keys on keyboard (G1-G18, M1-M3,MR and 5 extra > keys above multimedia keys, I call them L0-L4). It requires "uinput" to > be switched on in kernel (if you don't want support for keys - just > comment out "UInput" parameter in config file). BTW, > "lcd4linux.conf.sample" is also patched to include device definition for > G15. Now this sounds like a great idea! Q: are there any prerequisites for using uinput? Kernel version? We should add some checks to configure, I'm afraid.... I don't know anything about the linux's uinput layer, but would it be possible to use this stuff for all other displays with keys, too? There's already a generic key handler in lcd4linux, which does nothing at the moment but emit a debug message "key xy pressed". Should be easy to integrate the passing to uinput.... on the other hand, is it possible to "get" generic keypresses from uinput, too? this way, lcd4linux would benefit from other keys (probably some unused keys from your keyboard, joystick, ..) Any input would be greatly appreciated! > Also here is some (ugly?) patch for plugin_exec, which force all child > processes to be killed when main process is terminated. Thanks again. I know of this problem for months, but couldn't find the time to hunt it. I moved your signal() to a seperate function 'thread_destroy()', which is at least a bit less ugly :-) Thanks again, Michael -- Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Stefan K. <ste...@cr...> - 2006-07-12 15:49:22
|
Hi Luis, Luis.F.Correia schrieb am 10.07.2006 15:13: > > Will you accept a hand drawn one? Yes, sure. >> Meanwhile, I started a wiki-page at >> http://wiki.port23.de/index.php?title=LC-Display_f%C3%BCr_das_WRAP >> >> I collect all the stuff here. > > It's in German... i can only read 2% of what's written there :( One of my beer-mates translated it into english. Go here for the WRAP-enclosure: http://wiki.port23.de/index.php/WRAP_enclosure Go here for the WRAP-display: http://wiki.port23.de/index.php/LC-Display_for_WRAP |
|
From: Maxime P. <max...@bu...> - 2006-07-12 00:07:00
|
Hi everybody. I'm very, very sorry for the extended downtime Bulix.org suffered last week. My gateway's harddrive failed and now refuses to start. I tweaked my infrastructure to make the services up again and I'll rebuild my gateway system this summer. Check www.bulix.org for updates. - Sam -- Maxime Petazzoni (http://www.bulix.org) -- gone crazy, back soon. leave message. |
|
From: Xavier V. <xav...@fr...> - 2006-07-11 11:19:25
|
Hello everyone. Sam (bulix.org's owner) left Belfort last week and won't be back before the end of the month. Of course, Murphy's law is proved once more : his server's primary hard disk is dead since friday. I'm sorry for the inconvenience and I'll try to keep the team informed as soon as the situation evolves. Xavier (yes, I'm back) -- Xavier Vello <ge...@gm...> Blog : http://gemegik.bulix.org |
|
From: Luis.F.Correia <Lui...@se...> - 2006-07-11 07:58:26
|
Hi! to all list members, sorry for the 20k attachment. > -----Original Message----- > From: Stefan Krister [mailto:ste...@cr...] > Sent: Monday, July 10, 2006 10:52 AM > To: lcd...@li... > Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how > fast is i2c? ho w good is the lpc connector? > > > Hi Luis, > > > This affirmation was done my heart, as I don't have the breadboard > > assembly with me right now. But can confirm later on today. > > may I ask you for a circuit-schematic? I will probably able to provide one, but just not for the moment. In the mean time, here is the driver you'll need to use to prepare an AccessBus I2C driver, that will work with the I2C HD44780 lcd4linux implementation i've made. Please letme know of whatever difficulties you may encounter. Luis |
|
From: Stefan K. <ste...@cr...> - 2006-07-11 06:36:01
|
Hi Luis, > Is it me (and this part of the planet) or the new lcd4linux.bulix.org > webserver is down? confirmed - since last friday I think. MfG Stefan |
|
From: Luis.F.Correia <Lui...@se...> - 2006-07-11 03:36:21
|
Hi! > -----Original Message----- > From: Stefan Krister [mailto:ste...@cr...] > Sent: Monday, July 10, 2006 10:52 AM > To: lcd...@li... > Subject: Re: [Lcd4linux-devel] display on WRAP-Board - how > fast is i2c? ho w good is the lpc connector? > > > Hi Luis, > > > This affirmation was done my heart, as I don't have the breadboard > > assembly with me right now. But can confirm later on today. > > may I ask you for a circuit-schematic? Well, i don't have then done with any schematic software... Will you accept a hand drawn one? > > Of course other display controllers could be supported, > provided that > > someone writes the driver code :P > > Sure. I know that I have to do it. 3 weeks ago I started to > write a wrapd witch is able to light the WRAP-LEDs and reacts > on pressing the WRAP-push-button. Bevore that, I havn't > written any line of c-code for 10 or 15 years. I have written a device driver for it, and is included in our small router distribution, Bering uClibc. Maybe we could combine efforts to produce a much better one. http://leaf.cvs.sourceforge.net/leaf/src/bering-uclibc/apps/wrap1c/ It exposes the LED's and the button in a /proc interface > > It was pretty hard to learn that stuff again ... but now it's > included into fli4l as wrap-addon. If you like, get the > source from the .zip here: > http://extern.fli4l.de/fli4l_opt-db3/search.pl?pid=433 > > > The +5v line in the WRAP board is almost unuseable, > speccially if you > > use a miniPCI card that draws some power from it. > > Yes, i totally agree. > > > I also had some thoughts on using the GPIO pins, but found > it way too > > tricky to be done correclty (at least from me). > > ;-)) > > I'll see, what I get during programming ... I hope, my > coworkers at fli4l will help me on that. > > Do you know how many milliamps are allowed to get out of the > GPIO-header? Not many, but probably not enough to drive a LCD controller... Ask Pascal Dornier, the engineer of the WRAP boards, he is quite responsive to direct hw queries. > > Meanwhile, I started a wiki-page at > http://wiki.port23.de/index.php?title=LC-Display_f%C3%BCr_das_WRAP > > I collect all the stuff here. It's in German... i can only read 2% of what's written there :( Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu |
|
From: antst <an...@ma...> - 2006-07-11 03:03:27
|
Hi! There is a patch for G15 driver (CVS) which is 1) fix three bugs in the code which were reason for segfaults(arrays boundaries) 2) add support for extra keys on keyboard (G1-G18, M1-M3,MR and 5 extra keys above multimedia keys, I call them L0-L4). It requires "uinput" to be switched on in kernel (if you don't want support for keys - just comment out "UInput" parameter in config file). BTW, "lcd4linux.conf.sample" is also patched to include device definition for G15. With this patch keys produce some keycodes, which later can be used. For example, in X you can see keycodes with "xev" and bind them with "xbindkeys", like any other keys. Or use "xmodmap". Also here is some (ugly?) patch for plugin_exec, which force all child processes to be killed when main process is terminated. Anton. |
|
From: Luis C. <lfc...@lf...> - 2006-07-10 22:31:21
|
Hi! Is it me (and this part of the planet) or the new lcd4linux.bulix.org webserver is down? Luis |
|
From: Till H. <ti...@ha...> - 2006-07-10 16:53:23
|
Hi, On Saturday 08 July 2006 20:05, Stefan Krister wrote: > too complicatet. The WRAP-USB is also limited to 100mA - no way to drive > a LCD and the interface. The interface won't add noticable current. My LCD incl. the interface and a LED backlight draws less than 75mA. Till -- Dr.Ing. Till Harbaum <ti...@ha...> http://www.harbaum.org/till |
|
From: Stefan K. <ste...@cr...> - 2006-07-10 09:52:04
|
Hi Luis, > This affirmation was done my heart, as I don't have the breadboard > assembly with me right now. But can confirm later on today. may I ask you for a circuit-schematic? > Of course other display controllers could be supported, provided that > someone writes the driver code :P Sure. I know that I have to do it. 3 weeks ago I started to write a wrapd witch is able to light the WRAP-LEDs and reacts on pressing the WRAP-push-button. Bevore that, I havn't written any line of c-code for 10 or 15 years. It was pretty hard to learn that stuff again ... but now it's included into fli4l as wrap-addon. If you like, get the source from the .zip here: http://extern.fli4l.de/fli4l_opt-db3/search.pl?pid=3D433 > The +5v line in the WRAP board is almost unuseable, speccially if you u= se > a miniPCI card that draws some power from it. Yes, i totally agree. > I also had some thoughts on using the GPIO pins, but found it way too > tricky > to be done correclty (at least from me). ;-)) I'll see, what I get during programming ... I hope, my coworkers at fli4l will help me on that. Do you know how many milliamps are allowed to get out of the GPIO-header? Meanwhile, I started a wiki-page at http://wiki.port23.de/index.php?title=3DLC-Display_f%C3%BCr_das_WRAP I collect all the stuff here. MfG Stefan |
|
From: Luis.F.Correia <Lui...@se...> - 2006-07-10 09:09:36
|
Hi Stefan! > -----Original Message----- > From: Stefan Krister [mailto:ste...@cr...] > > Hi, > > I wish to connect a lcd to my WRAP-Board. I'm currently > examining on what connector the best results there will be. > > I2C - the last I read here was "and beware! we are planning > new and unlikely features to this interface (yes, we are also > adding the kitchen sink)" - one year ago. What happened > meanwhile? Are there any circuit diagrams available? Nothing much has happened since that statement, as both me and Paul have been busy with some other stuff. I2C is usable, but need some tweaking in the driver as the AccessBus controllers are not in any of the default IOport locations. (i can point you to this modified driver location if needed) Then, a simple I2C 8 bit I/O extender is needed, we have successfully used the PCF8574. No 3.3-5v level adapter are needed as the PCF can be driver exclusively at 3.3v, while the outputs to the LCD display fall within the TTL levels. This affirmation was done my heart, as I don't have the breadboard assembly with me right now. But can confirm later on today. The hardware is very simple, with support for a 4bit HD44780, which is also the only type of display controller that is supported under the I2C interface. Of course other display controllers could be supported, provided that someone writes the driver code :P > USB - I read about the thing, Till Harbaum developed, but I > think, it's too complicatet. The WRAP-USB is also limited to > 100mA - no way to drive a LCD and the interface. The +5v line in the WRAP board is almost unuseable, speccially if you use a miniPCI card that draws some power from it. A 7805 can be added to the board (some tricky soldering involved) or the board can be converted to work from +5V directly (no PoE possible). Only with these two options you can consider to use the USB interface. > I prefer - until now - using the "J2" - LPC-Expansion on my > WRAP-Board. > There are enough GPIO-Pins and a 3.3V power supply. Is > lcd4linux already able to support this way? I also had some thoughts on using the GPIO pins, but found it way too tricky to be done correclty (at least from me). > But that would not be enough for me .-)) > > I want also to have a RGB-backlight. Take a look at > http://www.lcd-module.de/eng/dog/dog.htm - theese "display on glas" > modules are running with 3.3V, there are many colors and > backlight-colors available and - a RGB-backlight. > > I think, the power consumption is o.k. for the WRAP-connector. > > So, how to interface with that beast? I will use 2 shift registers > (74HC595) what gives me 16 lines - D0 ... D7, E, RW, and RS. > The remaining 5 lines will be good for colorizing the > backlight in 32 different colors. > > >From my WRAP I will make use of 4 GPIO lines. 2 for the input of the > shift registers, 1 for both clock inputs and 1 for the latch. > > So, how far is that possible with lcd4linux? I couldn't took > a look into the lcd4linux-source - it seems the server is > down for the last few days ... if anybody please could mail > me - thanks. > Everything is possible to do with Lcd4Linux... provided that you write some code :) Luis Correia Bering uClibc Team Member PGP Fingerprint: BC44 D7DA 5A17 F92A CA21 9ABE DFF0 3540 2322 21F6 Key Server: http://pgp.mit.edu |
|
From: Stefan K. <ste...@cr...> - 2006-07-08 18:29:05
|
Hi, I wish to connect a lcd to my WRAP-Board. I'm currently examining on what connector the best results there will be. I2C - the last I read here was "and beware! we are planning new and unlikely features to this interface (yes, we are also adding the kitchen sink)" - one year ago. What happened meanwhile? Are there any circuit diagrams available? USB - I read about the thing, Till Harbaum developed, but I think, it's too complicatet. The WRAP-USB is also limited to 100mA - no way to drive a LCD and the interface. I prefer - until now - using the "J2" - LPC-Expansion on my WRAP-Board. There are enough GPIO-Pins and a 3.3V power supply. Is lcd4linux already able to support this way? But that would not be enough for me .-)) I want also to have a RGB-backlight. Take a look at http://www.lcd-module.de/eng/dog/dog.htm - theese "display on glas" modules are running with 3.3V, there are many colors and backlight-colors available and - a RGB-backlight. I think, the power consumption is o.k. for the WRAP-connector. So, how to interface with that beast? I will use 2 shift registers (74HC595) what gives me 16 lines - D0 ... D7, E, RW, and RS. The remaining 5 lines will be good for colorizing the backlight in 32 different colors. >From my WRAP I will make use of 4 GPIO lines. 2 for the input of the shift registers, 1 for both clock inputs and 1 for the latch. So, how far is that possible with lcd4linux? I couldn't took a look into the lcd4linux-source - it seems the server is down for the last few days ... if anybody please could mail me - thanks. |
|
From: Michael R. <re...@eu...> - 2006-06-25 15:35:36
|
Hi there,s
I just switched to automake-1.9 here, and tested it with lcd4linux. Runs
fine here. Some minor modifications have been checked into CVS.
there's one thing I dislike with automake-1.9: the compiler messages
take several lines, so one may miss compiler warnings. And I definitely
don't like compiler warnings.
When the old make looked like this:
gcc [options] -o file1.o file1.c
gcc [options] -o file2.o file2.c
gcc [options] -o file3.o file3.c
...
the new run looks like this:
if gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -Wall -W -g -O2 -MT
lcd4linux.o -MD -MP -MF ".deps/lcd4linux.Tpo" -c -o lcd4linux.o
lcd4linux.c; \
then mv -f ".deps/lcd4linux.Tpo" ".deps/lcd4linux.Po"; else rm
-f ".deps/lcd4linux.Tpo"; exit 1; fi
if gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -Wall -W -g -O2 -MT
cfg.o -MD -MP -MF ".deps/cfg.Tpo" -c -o cfg.o cfg.c; \
then mv -f ".deps/cfg.Tpo" ".deps/cfg.Po"; else rm -f
".deps/cfg.Tpo"; exit 1; fi
Is there a way to make the output look a bit nicer?
btw, some of you may already have noticed that SourceForge has changed
their CVS infrastructure, so that the old CVS paths did no longer work.
Basicalle, they changed from cvs.sourceforge.net to
lcd4linux.cvs.sourceforge.net. I've corrected the wiki, too (thanks,
Norbert!)
btw #2, I added a file "smoketest.sh", it does nothing but call
"configure --with-drivers=<name>; make" for every single driver, so that
compiler/linker issues which affect a single driver only should show up.
Any feedback with this script would be very welcome!
bye, Michael
--
Michael Reinelt <re...@eu...>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781
|
|
From: Michael R. <re...@eu...> - 2006-06-21 05:19:44
|
Hi Sam, > #ifdef GD2_ID > #if GD2_ID == "gd2" > echo "gd2 present." > #else > echo "gd2 not present." > #endif > > This constant is available at the very end of /usr/include/gd.h, you > may want to take a look (and check my syntax here, I'm doing it > on-the-fly). Thanks a lot! checked in... -- Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
|
From: Maxime P. <max...@bu...> - 2006-06-20 14:48:09
|
* Michael Reinelt <re...@eu...> [2006-06-20 13:08:38]:
> > I wonder if there is a way to distinguish libgd from libgd2 ... ?
> Me too. any hints, anybody out there?
#ifdef GD2_ID
#if GD2_ID == "gd2"
echo "gd2 present."
#else
echo "gd2 not present."
#endif
This constant is available at the very end of /usr/include/gd.h, you
may want to take a look (and check my syntax here, I'm doing it
on-the-fly).
- Sam
--
Maxime Petazzoni (http://www.bulix.org)
-- gone crazy, back soon. leave message.
|
163 messages has been excluded from this view by a project administrator.
