Hi, Great stuff here! A minor point: please add quotes to the copy path in post-build event. Often people (like me) will have spaces in the project path, e.g. C:\Users\jan\Documents\Visual Studio 2015\Projects\GDAL_2.1.x_VC-master\libgdal-2.1.1. copy $(Projectdir)$(PlatformShortName)\$(Configuration)\$(TargetName)$(TargetExt) $(SolutionDir)binaries\lib\$(PlatformShortName)\$(Configuration)\$(TargetName)$(TargetExt) becomes copy "$(Projectdir)$(PlatformShortName)\$(Configuration)\$(TargetName)$(TargetExt)" "$(SolutionDir)binaries\lib\$(PlatformShortName)\$(Configuration)\$(TargetName)$(TargetExt)" Can confirm it works fine in VS2015 and full lists of (re)source and header files are indeed present. Neat! Jan
On Fri, Aug 5, 2016 at 1:30 PM, Jeff McKenna <jmcke...@gatewaygeomatics.com> wrote: > On 2016-08-04 6:44 PM, Mateusz Loskot wrote: > >> >>> Can we make sure to document these steps, so they are not lost in emails? >>> Somewhere on the BuildHints wiki would be great. Possibly here? >>> https://trac.osgeo.org/gdal/wiki/BuildingOnWindows >>> >> >> https://trac.osgeo.org/gdal/wiki/BuildingOnWindows#Generatin >> gVisualStudioproject >> >> > Thanks. > > -jeff > > > > -- > Jeff McKenna > MapServer Consulting and Training Services > http://www.gatewaygeomatics.com/ > > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev