swift-haiku-build | Google Summer of Code repository
kandi X-RAY | swift-haiku-build Summary
kandi X-RAY | swift-haiku-build Summary
swift-haiku-build is a Shell library. swift-haiku-build has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
Google Summer of Code repository for building Swift 3.1, 4.x and higher for Haiku.
Google Summer of Code repository for building Swift 3.1, 4.x and higher for Haiku.
Support
Quality
Security
License
Reuse
Support
swift-haiku-build has a low active ecosystem.
It has 3 star(s) with 1 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
There are 1 open issues and 0 have been closed. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of swift-haiku-build is current.
Quality
swift-haiku-build has 0 bugs and 0 code smells.
Security
swift-haiku-build has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
swift-haiku-build code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
swift-haiku-build does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
swift-haiku-build releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of swift-haiku-build
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of swift-haiku-build
swift-haiku-build Key Features
No Key Features are available at this moment for swift-haiku-build.
swift-haiku-build Examples and Code Snippets
No Code Snippets are available at this moment for swift-haiku-build.
Community Discussions
No Community Discussions are available at this moment for swift-haiku-build.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install swift-haiku-build
You will find that the repository includes version-specific build scripts and patch files in their respective folders. Below is a short description of what they do:.
build-source.sh - Points to the master branch and compiles the toolchain from source using the swift-upstream patches for Haiku support.
build-source-X.Y.sh - Same as the build-source script but is version-specific and uses version-specific patches for Haiku specific changes. In this case build-source-3.0.sh compiles for Swift 3.
build-script.sh - The build script commands used to configure and build swift itself.
Whenever a new release or a new tag is out, it is possible to update the port by updating all the repositories and applying the patches automatically. Unless you are using the version-specific scripts 'build-source-X.Y.sh', you just update the tag from the releases page at apple/swift and replace it with the newest tag name, usually 'swift-DEVELOPMENT-SNAPSHOT-YYYY-MM-DD-a' in build-source.sh. Then you run either: * sh ./build-source.sh shallow - Which performs a shallow clone of the toolchain from the specified tag. Useful if you don't have a fast network connection nor you want to clone the entire commit history or perhaps saves you some disk space. * sh ./build-source.sh full - Performs a deep clone of the toolchain, with the entire commit history. * sh ./build-source.sh update - Makes it possible to pull all the newer commits prior to cloning from master. But this will reset any file modifications to prevent conflicts with edited files from HEAD.
Building a debug version of Swift (with LLVM even in release mode) will take as much as ~30GB of disk space! You would need to also build with -j1 when linking debug symbols as using multiple threads, will allocate more memory and exhaust your RAM space quickly when linking occurs. Follow steps 1-3 and right after the --stdlib-deployment-targets argument, append --debug-swift to debug the Swift compiler or for debugging the standard library --debug-swift-stdlib.
build-source.sh - Points to the master branch and compiles the toolchain from source using the swift-upstream patches for Haiku support.
build-source-X.Y.sh - Same as the build-source script but is version-specific and uses version-specific patches for Haiku specific changes. In this case build-source-3.0.sh compiles for Swift 3.
build-script.sh - The build script commands used to configure and build swift itself.
Whenever a new release or a new tag is out, it is possible to update the port by updating all the repositories and applying the patches automatically. Unless you are using the version-specific scripts 'build-source-X.Y.sh', you just update the tag from the releases page at apple/swift and replace it with the newest tag name, usually 'swift-DEVELOPMENT-SNAPSHOT-YYYY-MM-DD-a' in build-source.sh. Then you run either: * sh ./build-source.sh shallow - Which performs a shallow clone of the toolchain from the specified tag. Useful if you don't have a fast network connection nor you want to clone the entire commit history or perhaps saves you some disk space. * sh ./build-source.sh full - Performs a deep clone of the toolchain, with the entire commit history. * sh ./build-source.sh update - Makes it possible to pull all the newer commits prior to cloning from master. But this will reset any file modifications to prevent conflicts with edited files from HEAD.
Building a debug version of Swift (with LLVM even in release mode) will take as much as ~30GB of disk space! You would need to also build with -j1 when linking debug symbols as using multiple threads, will allocate more memory and exhaust your RAM space quickly when linking occurs. Follow steps 1-3 and right after the --stdlib-deployment-targets argument, append --debug-swift to debug the Swift compiler or for debugging the standard library --debug-swift-stdlib.
Support
This gist documents the progress made on porting Swift to Haiku and has detailed instructions on building the toolchain from source. Also, the sub-projects listed below show the progress of what has been completed so far in the Google Summer of Code (GSoC) period and their current statuses displayed below: (Excludes swift-llvm and swift-clang).
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page