Skip to content

Files

Latest commit

Jan 30, 2025
28d604a · Jan 30, 2025

History

History

win

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Feb 23, 2023
Jun 14, 2024
Aug 9, 2024
Jan 25, 2024
Aug 9, 2024
Jan 30, 2025
Jan 30, 2025
Jan 25, 2024
Jun 14, 2024
Nov 7, 2024
Nov 7, 2024
Aug 9, 2024

README.md

Windows build scripts for GDAL

Table of contents

Table of contents generated with markdown-toc.

In this folder contains Powershell and NMake scripts for building Windows runtime packages.

Prerequisites:

  1. Visual Studio Build Tools (with ATL). Recommended versions - vs16.0(2019) and vs17.0(2022) or greater (nmake and to retarget libpng to v143 toolset)

  2. .NET Core SDK and Nuget.exe - for building and publishing packages respectively.

Building: (in PowerShell)

  1. Call ./install.ps1 to install all required packages and tools.
    Possible options:
     [bool] $cleanGdalBuild = $true,  # clean gdal-build folder (output) before build
     [bool] $cleanGdalIntermediate = $true, # clean gdal-cmake-temp (cache) folder
     [bool] $cleanProjBuild = $true, # clean proj-build folder (output) before build    
     [bool] $cleanProjIntermediate = $true, # clean proj-cmake-temp (cache) folder
     [bool] $bootstrapVcpkg = $true, # bootstrap VCPKG from scratch
     [bool] $installVcpkgPackages = $true, # install VCPKG packages
     [bool] $isDebug = $false # build debug version of packages
    Example:
    ./install.ps1 -cleanGdalBuild:$true -cleanGdalIntermediate:$true -isDebug:$true

This will install all required VCPKG packages and tools, build GDAL and PROJ, and build runtime and core packages.

  1. Call ./test.ps1 to test runtime and core packages.
    If everything runs smoothly, you can use a local nuget feed to include packages in your project.

Troubleshooting dependencies:

Use dumpbin or dependency walker to check gdal's dependencies. Please ensure the tests are passing before bringing them to prod.

Have fun)

Contact me: Telegram - MaxRev