mapnik-org/mapnik — Issue #555: Current SVN trunk(r1800) does not compile
Author: artemp
Created: 2011-10-11 08:01:44+00:00
State: closed
Labels: Core_Library

Trying to compile current SVN trunk (r1800) I get:
In file included from agg/include/agg_rasterizer_scanline_aa.h:32,
from include/mapnik/svg/agg_svg_path_renderer.h:30,
from src/agg_svg_path_renderer.cpp:22:
agg/include/agg_rasterizer_cells_aa.h: In member function ‘void agg::rasterizer_cells_aa	::line(int, int, int, int)’:
agg/include/agg_rasterizer_cells_aa.h:328: error: there are no arguments to ‘abs’ that depend on a template parameter, so a declaration of ‘abs’ must be available
agg/include/agg_rasterizer_cells_aa.h:328: note: (if you use ‘-fpermissive’, G++ will accept your code, but allowing the use of an undeclared name is deprecated)
agg/include/agg_rasterizer_cells_aa.h:328: error: ‘INT_MAX’ was not declared in this scope
agg/include/agg_rasterizer_cells_aa.h:328: error: there are no arguments to ‘abs’ that depend on a template parameter, so a declaration of ‘abs’ must be available
agg/include/agg_rasterizer_cells_aa.h:329: error: there are no arguments to ‘abs’ that depend on a template parameter, so a declaration of ‘abs’ must be available
agg/include/agg_rasterizer_cells_aa.h:329: error: there are no arguments to ‘abs’ that depend on a template parameter, so a declaration of ‘abs’ must be available

And also an error in include/mapnik/svg/agg_svg_path_renderer.h:
In file included from src/agg_svg_path_renderer.cpp:22:
include/mapnik/svg/agg_svg_path_renderer.h:168: error: redefinition of ‘double rx’
include/mapnik/svg/agg_svg_path_renderer.h:168: error: ‘double rx’ previously declared here
src/agg_svg_path_renderer.cpp:169: error: prototype for ‘void agg::svg::path_renderer::arc_to(double, double, double, bool, bool, double, double, bool)’ does not match any in class ‘agg::svg::path_renderer’
include/mapnik/svg/agg_svg_path_renderer.h:168: error: candidate is: void agg::svg::path_renderer::arc_to(double, double, bool, bool, double, double, bool)

The attached patch fixes both errors.