[GRASS-dev] Driver changes

GRASS GIS GRASS GIS developer
1

I've just committed some changes to the layout of the driver code.
Specifically, the display/drivers/lib directory has been moved to
lib/driver, while the bulk of the PNG driver has been moved into a
separate library in lib/pngdriver.

It shouldn't have any impact from the perspective of either
application code or the user, but the changes to the layout (and the
corresponding changes to the Makefiles) are signficant enough that I
could have missed something which could cause compilation problems.

I would appreciate it if people could report successful compilations
after having updated to the new code, so that I can get an idea of
when it's had a reasonable amount of testing. I don't want to commit
the next phase (integration of libpngdriver with libraster) until any
problems with the latest changes have been ironed out.

--
Glynn Clements <glynn@gclements.plus.com>

2

On Thu, 1 Jun 2006 19:25:39 +0100
Glynn Clements <glynn@gclements.plus.com> wrote:

I would appreciate it if people could report successful compilations
after having updated to the new code,

All OK for me. Using CVS from just a while ago. Not a single error
during configure or make.

Ubuntu 5.10 Breezy (Debian derivative).

./configure --with-cxx --without-odbc --with-sqlite
--with-tcltk-includes="/usr/include/tcl8.4/"
--with-postgres-includes="/usr/include/postgresql/" --with-freetype
--with-freetype-includes="/usr/include/freetype2/" --with-readline
--with-ffmpeg=yes --with-ffmpeg-includes=/usr/include/ffmpeg
--with-proj-share=/usr/local/share/proj/

Using gcc 3.4.5.

Maciek

--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/

3

hallo,

./configure --with-cxx --with-freetype
--with-tcltk-includes=/usr/include/tcl8.4/
--with-postgres-includes=/usr/include/postgresql/
--with-freetype-includes=/usr/include/freetype2/

compilation no problem

d.out.png all right

Jáchym

On Thu, Jun 01, 2006 at 07:25:39PM +0100, Glynn Clements wrote:

I've just committed some changes to the layout of the driver code.
Specifically, the display/drivers/lib directory has been moved to
lib/driver, while the bulk of the PNG driver has been moved into a
separate library in lib/pngdriver.

It shouldn't have any impact from the perspective of either
application code or the user, but the changes to the layout (and the
corresponding changes to the Makefiles) are signficant enough that I
could have missed something which could cause compilation problems.

I would appreciate it if people could report successful compilations
after having updated to the new code, so that I can get an idea of
when it's had a reasonable amount of testing. I don't want to commit
the next phase (integration of libpngdriver with libraster) until any
problems with the latest changes have been ironed out.

--
Glynn Clements <glynn@gclements.plus.com>

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Jachym Cepicky
e-mail: jachym.cepicky@centrum.cz
URL: http://les-ejk.cz
GPG: http://les-ejk.cz/gnupg_public_key/jachym_cepicky-gpg_public_key.asc
-----------------------------------------
OFFICE:
GDF-Hannover
Mengendamm 16d
30177 Hannover
Germany
e-mail: cepicky@gdf-hannover.de
URL: http://gdf-hannover.de
Tel.: +49 511-39088507

4

I've just committed some changes to the layout of the driver code.
Specifically, the display/drivers/lib directory has been moved to
lib/driver, while the bulk of the PNG driver has been moved into a
separate library in lib/pngdriver.

It shouldn't have any impact from the perspective of either
application code or the user, but the changes to the layout (and the
corresponding changes to the Makefiles) are signficant enough that I
could have missed something which could cause compilation problems.

I would appreciate it if people could report successful compilations
after having updated to the new code, so that I can get an idea of
when it's had a reasonable amount of testing. I don't want to commit
the next phase (integration of libpngdriver with libraster) until any
problems with the latest changes have been ironed out.

Can we tag 6.1.0 before the next lot of changes are committed?
It would make a common basis for before/after tests.

Hamish