Releases: stackotter/swift-bundler
v1.4.3
Fixes the dynamic library copying step for universal builds.
v1.4.2
Fixes a bug that occurred when the path to a swift bundler project contained spaces. Spaces in file paths are now correctly escaped.
v1.4.1
Fixes an issue regarding dynamic linking. The bundler used to use DynamicLibraries
inside an app's contents as the location for dylibs. However the default location is lib
inside an app's contents and using a custom rpath lead to some issues.
Support dynamic libraries
Swift Bundler can now automatically detect dynamic libraries and copy them into the app bundle. The dynamic libraries are located at /path/to/YourApp.app/Contents/DynamicLibraries
. Framework resources are not supported and if a framework contains resources, swift-bundler will let you know by throwing an error and exiting.
1.3.0
Allows the executable target to be selected in Bundle.json
and removes a few janky bits of code. Someone was having an issue with swift-bundler crashing cause zsh could not be found so now sh is used for running shell commands.
v1.2.0
Fixes a bug with generate-xcode-support
and adds remove-file-headers
which removes all file headers of source files. File headers are the autogenerated comments Xcode puts at the tops of files and some people don't like them. Add the remove-file-headers command to a prebuild script to automatically remove new ones whenever you build.
v1.1.0
Xcode support has been completely changed. Now the swift bundler generate-xcode-support
will populate the .swiftpm/xcode directory with a scheme. .xcodeproj
s are no longer generated.
1.0.1
Fixes issues to do with universal builds.
- Progress bar now works properly for universal builds
- Bundles are now generated correctly for universal builds
1.0.0
Features
- Create macOS apps from Swift packages
- Almost seamless Xcode integration