My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Earlier this year

  • Apr 03, 2009
    r18 (updated copyright) committed by theicebreaker007   -   updated copyright
    updated copyright
  • Apr 03, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) commented on by dane.springmeyer   -   great, works well, thanks!
    great, works well, thanks!
  • Apr 03, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) commented on by theicebreaker007   -   I pushed out a fix for this, so just update your working copy.
    I pushed out a fix for this, so just update your working copy.
  • Apr 03, 2009
    r17 (added color support for LoadableModule) committed by theicebreaker007   -   added color support for LoadableModule
    added color support for LoadableModule
  • Apr 03, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) commented on by theicebreaker007   -   This is on MacOSX I guess, because I see the "dylib" :)) Are you compiling the shared library via SharedLibrary?
    This is on MacOSX I guess, because I see the "dylib" :)) Are you compiling the shared library via SharedLibrary?
  • Apr 03, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) commented on by dane.springmeyer   -   Hey, thanks that works great, good to know. The added benefit of this colorizing is making it dead simple to see errors/warnings in the build output. I noticed that we create a shared library whose output is not caught: {{{ [[...snip...] Compiling ==> 'osmparser.cpp' Linking shared object ==> 'libmapnik.dylib' Compiling ==> 'osm.cpp' g++ -o bindings/python/_mapnik.so -F/ -framework Python -bundle bindings/python/mapnik_color.os bindings/python/mapnik_coord.os bindings/python/mapnik_datasource.os bindings/python/mapnik_datasource_cache.os bindings/python/mapnik_envelope.os bindings/python/mapnik_feature.os bindings/python/mapnik_featureset.os bindings/python/mapnik_filter.os bindings/python/mapnik_font_engine.os bindings/python/mapnik_geometry.os bindings/python/mapnik_image.os bindings/python/mapnik_image_view.os bindings/python/mapnik_layer.os bindings/python/mapnik_line_pattern_symbolizer.os bindings/python/mapnik_line_symbolizer.os bindings/python/mapnik_map.os bindings/python/mapnik_parameters.os bindings/python/mapnik_point_symbolizer.os bindings/python/mapnik_polygon_pattern_symbolizer.os bindings/python/mapnik_polygon_symbolizer.os bindings/python/mapnik_proj_transform.os bindings/python/mapnik_projection.os bindings/python/mapnik_python.os bindings/python/mapnik_query.os bindings/python/mapnik_raster_symbolizer.os bindings/python/mapnik_rule.os bindings/python/mapnik_shield_symbolizer.os bindings/python/mapnik_stroke.os bindings/python/mapnik_style.os bindings/python/mapnik_text_symbolizer.os bindings/python/mapnik_view_transform.os bindings/python/python_cairo.os -Lagg -Lsrc -L/usr/local/lib - L/usr/lib -L/opt/local/lib -L/usr/X11/lib -L/usr/local/pgsql/lib -lmapnik -lpng -ljpeg -lboost_python-mt - licuuc -licudata -lboost_regex-mt -lboost_thread-mt -lcairomm-1.0 -lcairo Compiling ==> 'osm_datasource.cpp' Compiling ==> 'osm_featureset.cpp' [...snip..] }}} Any idea how that catch that?
    Hey, thanks that works great, good to know. The added benefit of this colorizing is making it dead simple to see errors/warnings in the build output. I noticed that we create a shared library whose output is not caught: {{{ [[...snip...] Compiling ==> 'osmparser.cpp' Linking shared object ==> 'libmapnik.dylib' Compiling ==> 'osm.cpp' g++ -o bindings/python/_mapnik.so -F/ -framework Python -bundle bindings/python/mapnik_color.os bindings/python/mapnik_coord.os bindings/python/mapnik_datasource.os bindings/python/mapnik_datasource_cache.os bindings/python/mapnik_envelope.os bindings/python/mapnik_feature.os bindings/python/mapnik_featureset.os bindings/python/mapnik_filter.os bindings/python/mapnik_font_engine.os bindings/python/mapnik_geometry.os bindings/python/mapnik_image.os bindings/python/mapnik_image_view.os bindings/python/mapnik_layer.os bindings/python/mapnik_line_pattern_symbolizer.os bindings/python/mapnik_line_symbolizer.os bindings/python/mapnik_map.os bindings/python/mapnik_parameters.os bindings/python/mapnik_point_symbolizer.os bindings/python/mapnik_polygon_pattern_symbolizer.os bindings/python/mapnik_polygon_symbolizer.os bindings/python/mapnik_proj_transform.os bindings/python/mapnik_projection.os bindings/python/mapnik_python.os bindings/python/mapnik_query.os bindings/python/mapnik_raster_symbolizer.os bindings/python/mapnik_rule.os bindings/python/mapnik_shield_symbolizer.os bindings/python/mapnik_stroke.os bindings/python/mapnik_style.os bindings/python/mapnik_text_symbolizer.os bindings/python/mapnik_view_transform.os bindings/python/python_cairo.os -Lagg -Lsrc -L/usr/local/lib - L/usr/lib -L/opt/local/lib -L/usr/X11/lib -L/usr/local/pgsql/lib -lmapnik -lpng -ljpeg -lboost_python-mt - licuuc -licudata -lboost_regex-mt -lboost_thread-mt -lcairomm-1.0 -lcairo Compiling ==> 'osm_datasource.cpp' Compiling ==> 'osm_featureset.cpp' [...snip..] }}} Any idea how that catch that?
  • Apr 03, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) Status changed by theicebreaker007   -   This works, you just have to find the right spot where to execute the colorize() call on the given environment. I attached my modified SConstruct for mapnik-0.6.0. The same thing should work with other versions as well.
    Status: Fixed
    This works, you just have to find the right spot where to execute the colorize() call on the given environment. I attached my modified SConstruct for mapnik-0.6.0. The same thing should work with other versions as well.
    Status: Fixed
  • Mar 31, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) commented on by dane.springmeyer   -   huh that got cut off... trying again, here is the error: scons: Building targets ... Linking library ==> 'libagg.a' Linking shared object ==> 'libmapnik.dylib' ld: in agg/libagg.a, archive has no table of contents collect2: ld returned 1 exit status scons: *** [src/libmapnik.dylib] Error 1 scons: building terminated because of errors. and then when I start back up freshly with the col.colorizer(env) call removed I get a build that works but the first SCon output is truncated, weird: $ scons scons: Reading SConscript files ... Welcome to Mapnik... Using previous successful configuration... Re-configure by running "python scons/scons.py configure". scons: done reading SConscript files. scons: Building targets ... ar rc agg/libagg.a agg/src/agg_arc.o agg/src/agg_arrowhead.o agg/src/agg_bezier_arc.o agg/src/agg_bspline.o agg/src/agg_curves.o agg/src/agg_embedded_raster_fonts.o agg/src/agg_gsv_text.o agg/src/agg_image_filters.o agg/src/agg_line_aa_basics.o agg/src/agg_line_profile_aa.o agg/src/agg_rounded_rect.o agg/src/agg_sqrt_tables.o agg/src/agg_trans_affine.o agg/src/agg_trans_double_path.o agg/src/agg_trans_single_path.o agg/src/agg_trans_warp_magnifier.o agg/src/agg_vcgen_bspline.o agg/src/agg_vcgen_contour.o agg/src/agg_vcgen_dash.o agg/src/agg_vcgen_markers_term.o agg/src/agg_vcgen_smooth_poly1.o agg/src/agg_vcgen_stroke.o agg/src/agg_vpgen_clip_polygon.o agg/src/agg_vpgen_clip_polyline.o agg/src/agg_vpgen_segmentator.o ranlib agg/libagg.a g++ -o src/libmapnik.dylib -Wl,-install_name,libmapnik.dylib -dynamiclib src/agg_renderer.os src/datasource_cache.os src/color.os src/envelope.os src/filter_factory.os src/font_engine_freetype.os src/font_set.os src/graphics.os src/image_reader.os src/image_util.os src/layer.os src/line_pattern_symbolizer.os src/map.os src/load_map.os src/memory.os src/params.os src/placement_finder.os src/plugin.os src/png_reader.os src/point_symbolizer.os src/polygon_pattern_symbolizer.os src/save_map.os src/shield_symbolizer.os src/text_symbolizer.os src/tiff_reader.os src/wkb.os src/projection.os src/proj_transform.os src/distance.os src/scale_denominator.os src/memory_datasource.os src/stroke.os src/symbolizer.os src/arrow.os src/unicode.os src/cairo_renderer.os src/libxml2_loader.os -Lagg -Lsrc -L/usr/local/lib -L/usr/lib - L/opt/local/lib -L/usr/X11/lib -L/usr/local/pgsql/lib -lagg -lxml2 -lpthread -liconv -lcairomm-1.0 -lcairo -lSM -lICE -lpixman-1 -lfontconfig -lexpat -lfreetype -lpng12 -lXrender -lX11 -lm -lltdl -lpng -ltiff -lz - ljpeg -lproj -licuuc -licudata -lboost_system-mt -lboost_filesystem-mt -lboost_regex-mt - lboost_iostreams-mt -lboost_program_options-mt -lboost_thread-mt -lgdal -lpq -lsqlite3 scons: done building targets.
    huh that got cut off... trying again, here is the error: scons: Building targets ... Linking library ==> 'libagg.a' Linking shared object ==> 'libmapnik.dylib' ld: in agg/libagg.a, archive has no table of contents collect2: ld returned 1 exit status scons: *** [src/libmapnik.dylib] Error 1 scons: building terminated because of errors. and then when I start back up freshly with the col.colorizer(env) call removed I get a build that works but the first SCon output is truncated, weird: $ scons scons: Reading SConscript files ... Welcome to Mapnik... Using previous successful configuration... Re-configure by running "python scons/scons.py configure". scons: done reading SConscript files. scons: Building targets ... ar rc agg/libagg.a agg/src/agg_arc.o agg/src/agg_arrowhead.o agg/src/agg_bezier_arc.o agg/src/agg_bspline.o agg/src/agg_curves.o agg/src/agg_embedded_raster_fonts.o agg/src/agg_gsv_text.o agg/src/agg_image_filters.o agg/src/agg_line_aa_basics.o agg/src/agg_line_profile_aa.o agg/src/agg_rounded_rect.o agg/src/agg_sqrt_tables.o agg/src/agg_trans_affine.o agg/src/agg_trans_double_path.o agg/src/agg_trans_single_path.o agg/src/agg_trans_warp_magnifier.o agg/src/agg_vcgen_bspline.o agg/src/agg_vcgen_contour.o agg/src/agg_vcgen_dash.o agg/src/agg_vcgen_markers_term.o agg/src/agg_vcgen_smooth_poly1.o agg/src/agg_vcgen_stroke.o agg/src/agg_vpgen_clip_polygon.o agg/src/agg_vpgen_clip_polyline.o agg/src/agg_vpgen_segmentator.o ranlib agg/libagg.a g++ -o src/libmapnik.dylib -Wl,-install_name,libmapnik.dylib -dynamiclib src/agg_renderer.os src/datasource_cache.os src/color.os src/envelope.os src/filter_factory.os src/font_engine_freetype.os src/font_set.os src/graphics.os src/image_reader.os src/image_util.os src/layer.os src/line_pattern_symbolizer.os src/map.os src/load_map.os src/memory.os src/params.os src/placement_finder.os src/plugin.os src/png_reader.os src/point_symbolizer.os src/polygon_pattern_symbolizer.os src/save_map.os src/shield_symbolizer.os src/text_symbolizer.os src/tiff_reader.os src/wkb.os src/projection.os src/proj_transform.os src/distance.os src/scale_denominator.os src/memory_datasource.os src/stroke.os src/symbolizer.os src/arrow.os src/unicode.os src/cairo_renderer.os src/libxml2_loader.os -Lagg -Lsrc -L/usr/local/lib -L/usr/lib - L/opt/local/lib -L/usr/X11/lib -L/usr/local/pgsql/lib -lagg -lxml2 -lpthread -liconv -lcairomm-1.0 -lcairo -lSM -lICE -lpixman-1 -lfontconfig -lexpat -lfreetype -lpng12 -lXrender -lX11 -lm -lltdl -lpng -ltiff -lz - ljpeg -lproj -licuuc -licudata -lboost_system-mt -lboost_filesystem-mt -lboost_regex-mt - lboost_iostreams-mt -lboost_program_options-mt -lboost_thread-mt -lgdal -lpq -lsqlite3 scons: done building targets.
  • Mar 31, 2009
    issue 1 (Odd problem where colorizer seems to bork build process) reported by dane.springmeyer   -   Cool little project. But I just tried it with Mapnik's SConstruct and when I add the scolorizer code as described on the GettingStarted page I get this error: {{{ $ scons
    Cool little project. But I just tried it with Mapnik's SConstruct and when I add the scolorizer code as described on the GettingStarted page I get this error: {{{ $ scons
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Jan 11, 2009
    scolorizer-0.2.tar.gz (v0.2) file uploaded by theicebreaker007   -  
    Labels: OpSys-All Type-Archive Featured
    Labels: OpSys-All Type-Archive Featured
  • Jan 11, 2009
    r11 (major re-write v0.2) committed by theicebreaker007   -   major re-write v0.2
    major re-write v0.2
  • Jan 11, 2009
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007

Older

  • Dec 15, 2008
    r9 (added possibility to disable colors, but leave the customize...) committed by theicebreaker007   -   added possibility to disable colors, but leave the customized output
    added possibility to disable colors, but leave the customized output
  • Dec 15, 2008
    GettingStarted (Getting started using scolorizer) Wiki page edited by theicebreaker007
  • Dec 15, 2008
    scolorizer-0.1.tar.gz (Initial release) file uploaded by theicebreaker007   -  
    Labels: Type-Source OpSys-All Featured
    Labels: Type-Source OpSys-All Featured
  • Dec 15, 2008
    GettingStarted (Getting started using scons output colorizer) Wiki page edited by theicebreaker007
  • Dec 15, 2008
    GettingStarted (Getting started using scons output colorizer) Wiki page edited by theicebreaker007
  • Dec 15, 2008
    GettingStarted (Getting started using scons output colorizer) Wiki page added by theicebreaker007
  • Dec 15, 2008
    r3 (removed temporary file) committed by theicebreaker007   -   removed temporary file
    removed temporary file
  • Dec 15, 2008
    r2 (initial import) committed by theicebreaker007   -   initial import
    initial import
  • Dec 15, 2008
    Project scolorizer created by theicebreaker007   -   Scons output colorizer
    Scons output colorizer
 
Hosted by Google Code