On 11-02-11 06:56 PM, Tamas Szekeres wrote:
Frank,
While I'm not sure about what changes you intend to do here, I would
emphatically disagree removing the current approach with the ability of setting
the full path to the external configuration file from the nmake command line.
My build system is higly depend on this setting and if we don't have any
compelling reason I would like to avoid relocating this custom file (which is
anyway generated dynamically) into the gdal source tree.
Tamas,
I did not remove the support for EXT_NMAKE_OPT - the first stuff in
nmake.opt now looks like:
###############################################################################
# For convenience, user may put custom settings in a local settings file
# named nmake.local, or a name defined by the EXT_NMAKE_OPT option.
!IF EXIST("$(GDAL_ROOT)\nmake.local")
!INCLUDE $(GDAL_ROOT)\nmake.local
!ENDIF
# nmake -f makefile.vc EXT_NMAKE_OPT=mynmake.opt
!IFDEF EXT_NMAKE_OPT
!INCLUDE $(EXT_NMAKE_OPT)
!ENDIF
I believe this will serve both needs smoothly, albeit with a little
extra complication in the nmake.opt.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
