mirror of
https://github.com/owasp-modsecurity/ModSecurity.git
synced 2025-08-16 16:06:12 +03:00
There are a ModSecurityIIS solution and project files, those were using hard coded paths to meet the dependencies. As consequence of the last update in our build scripts, now we are able to built the dependencies and load it to our Visual Studio project using relative paths.
27 lines
580 B
Batchfile
27 lines
580 B
Batchfile
cd "%WORK_DIR%"
|
|
|
|
@if NOT EXIST "%SOURCE_DIR%\%APACHE_BIN%" goto file_not_found_bin
|
|
|
|
7z.exe x "%SOURCE_DIR%\%PCRE%"
|
|
set PCRE_DIR=%PCRE:~0,-4%
|
|
|
|
mklink /D "pcre" "%PCRE_DIR%"
|
|
|
|
cd "%PCRE_DIR%"
|
|
CMAKE -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_SHARED_LIBS=True
|
|
NMAKE
|
|
cd "%WORK%"
|
|
|
|
copy /y "%WORK_DIR%\%PCRE_DIR%\pcre.dll" "%OUTPUT_DIR%"
|
|
copy /y "%WORK_DIR%\%PCRE_DIR%\pcre.pdb" "%OUTPUT_DIR%"
|
|
copy /y "%WORK_DIR%\%PCRE_DIR%\pcre.lib" "%OUTPUT_DIR%"
|
|
echo "a"
|
|
@exit /B 0
|
|
|
|
:file_not_found_bin
|
|
@echo File not found: "%SOURCE_DIR%\%PCRE%"
|
|
@goto failed
|
|
|
|
:failed
|
|
@exit /B 1
|