SwiftXMLParserDemo

This is a demo for the SwiftXMLParser.

Build with swift build -c release.

Give the path to an XML file as argument to the program and it prints infos about the parts of the XML document the parser finds.

Add the argument "-c" and the elements and all parse events are counted without further output.

Give a second path as second argument to the program and the XML document will be written to this second path.

This demo is published under the Apache License 2.0. For questions or remarks see my contact information on my website.

Usage on Windows

First we describe how to install Swift on Windows.

1. The Swift Package Manager uses symbolic links, but Microsoft has decided that symbolic links might be harmful (see there under "Create symbolic links"). You need the SE_CREATE_SYMBOLIC_LINK privilege in Windows to use symbolic links, you can set this privilege for the user using the gpedit.msc tool (execute as Administrator). (Note that other security policies for your computer might overwrite this setting.) If you have the Home edition of of Windows, you first have to get this tool from Microsoft using the following script (open the command line window as Administrator):

@echo off 

pushd "%~dp0" 

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt 

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt 

for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\%%i" 

pause

You can then set the privilege in the gpedit.msc tool under Computer Configuration / Windows Settings / Security Settings / Local Policies / User Rights Assignment (use a right-click for the listed setting and choose Properties / Enhanced / Search to add yourself as user). Then restart ypour computer. As a test, try to set a link via mklink LinkFile TargetFile.

2. Install Visual Studio (get it from https://visualstudio.microsoft.com).

3. Install the Swift toolchain (get it from https://swift.org/download). Swift will be installed to C:\Library. In a newly opened comamnd line windows, the command swift -version should then print the Swift version.

4. You will have to make the Windows SDK accessable to Swift. Open the x64 Native Tools for VS2019 Command Prompt with Administrator rights (via the context menu of the entry for x64 Native Tools for VS2019 Command Prompt in the start menu) and inside it, execute the following commands. (Please also see the documentation https://swift.org/getting-started/ in case something has changed.)

copy %SDKROOT%\usr\share\ucrt.modulemap "%UniversalCRTSdkDir%\Include\%UCRTVersion%\ucrt\module.modulemap"
copy %SDKROOT%\usr\share\visualc.modulemap "%VCToolsInstallDir%\include\module.modulemap"
copy %SDKROOT%\usr\share\visualc.apinotes "%VCToolsInstallDir%\include\visualc.apinotes"
copy %SDKROOT%\usr\share\winsdk.modulemap "%UniversalCRTSdkDir%\Include\%UCRTVersion%\um\module.modulemap"

Next, we describe to use this Swift package in the Clion IDE. If you do not want to change this package but only would like to build and run it as-is, instead of using Clion you could just run the command swift build -c release from within the package to build it.

5. Different options could be considered for editing Swift source code. We describe the usage of CLion, a commercial IDE. You can get the installer from https://www.jetbrains.com/clion.

6. Start Clion.

7. Add the Swift plugin via the CLion Settings dialog.

8. Configure the Swift toolchain in CLion (the settings for the Swift plugin might be the last entry in the Settings dialog). Choose the toolchain under C:\Library\Developer\Toolchains (select the subdirectory in Toolchains).

9. Check-out this Swift package and open in in CLion (open Package.swift in CLion and choose "open as project").

10. Click the Run symbol in CLion. (You can also execute swift build -c release for building or swift run -c release for also running inside your package. The Swift plugin for CLion is quite new, so this might even be necessary.) With the current state of the project (May 11, 2021) the document should then get validated, validation errors printed, and entity definitions and their usage will be displayed.