shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

268
active users

#SwiftPM

0 posts0 participants0 posts today
Marcin Krzyzanowski<p>bonus point for mise, is support for <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> CLI tools installation. it allows to install swift package like this:</p><p>~ ❯ mise use -g spm:swiftwasm/WasmKit<br>~ ❯ wasmkit-cli --help<br>OVERVIEW: WasmKit WebAssembly Runtime</p>
Cihat Gündüz<p>This .editorconfig file should be added to every single <a href="https://iosdev.space/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> repo out there! 👇<br><a href="https://gist.github.com/Jeehut/e5b7559da355a1f243d9c012fe63edc4" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gist.github.com/Jeehut/e5b7559</span><span class="invisible">da355a1f243d9c012fe63edc4</span></a></p><p>It ensures that everyone editing the package in Xcode will get the same indentation settings avoiding mismatches with their global settings. 🥳</p><p>Add it now! 💯 <a href="https://iosdev.space/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOSDev</span></a> <a href="https://iosdev.space/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://iosdev.space/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftLang</span></a> <a href="https://iosdev.space/tags/XcodeTips" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>XcodeTips</span></a></p>
Christian Tietze<p><a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> with resources in production and test target work in Xcode.</p><p>`swift test` on the CLI fails to load NSColor from Asset catalog, though. The catalog is part of the library.</p><p>Is that some CLI thing?</p><p>Is Bundle.module pointing at the wrong one?</p>
Ma’moun<p>I occasionally hear the misconception amongst iOS devs that SwiftPM will resolve/clone every dependency in the graph, including test dependencies added by dependent packages. This is not true since SE-0226.</p><p>Since Swift 5.2, SwiftPM will compute the graph needed only by the specific products you add from a package. Because test dependencies will never be added to those production targets, they should never be included in resolved graph. </p><p><a href="https://mastodon.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swift</span></a> <a href="https://mastodon.social/tags/swiftpm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swiftpm</span></a></p>
Max Desiatov 🇺🇦<p>There's a new <a href="https://mastodon.social/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftLang</span></a> pitch authored by <span class="h-card" translate="no"><a href="https://det.social/@fbusch" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fbusch</span></a></span> that I had an opportunity to contribute to. If graduates to a proposal and is implemented as envisioned, it could become one of the most impactful changes in how one writes package manifests for <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> <a href="https://forums.swift.org/t/pitch-package-traits/72191" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">forums.swift.org/t/pitch-packa</span><span class="invisible">ge-traits/72191</span></a></p>
Christian Tietze<p>It's May 2nd!</p><p>Two days ago, the results were discouraging, so now that the deadline has passed, I ask again :)</p><p>Where can I steal *your* Privacy Manifest build step instructions for <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> packages and <a href="https://mastodon.social/tags/Xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xcode</span></a> frameworks?</p>
Christian Tietze<p>Did y'all write Privacy Manifests for your <a href="https://mastodon.social/tags/Xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xcode</span></a> / <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> projects?</p><p>Still need to update packages I use and/or maintain 😥</p>
Marcin Krzyzanowski<p>If you asked how @SwiftStudio going. Well... it been better. Apple <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Swift</span></a> just recently decided to shutdown <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> API I use (to make things CLI cannot provide). I find it unexpected (to me, not to apple) move after many years. <a href="https://github.com/apple/swift-package-manager/issues/7440" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/apple/swift-package</span><span class="invisible">-manager/issues/7440</span></a></p><p>I'm disappointed with a move in that direction and find that decision harmful for the third-party dev tooling ecosystem trying to adopt SwiftPM. IMHO.</p>
Marcin Krzyzanowski<p>No. 1 reason to "open source" <a href="https://mastodon.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swift</span></a> package for a company is because <a href="https://mastodon.social/tags/Xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Xcode</span></a> can't handle binary packages correctly, and Linux <a href="https://mastodon.social/tags/SwiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SwiftPM</span></a> don't support binaries at all.</p><p>it comes from a company being famously closed source and the biggest in the industry</p><p>it's not about the source, it's about tools.</p>
Uli Kusterer (Not a kitteh)<p>I don’t get why so many package managers use weird, wrong, or ambiguous file extensions for their depencency list file.</p><p>Package.swift<br>CMakeLists.txt<br>Podfile</p><p>How is anyone supposed to build a good client GUI app for them that associates with that file?</p><p>Just because a Package.swift happens to be parseable as swift code doesn't mean it shouldn’t have its own .swiftpm extension or so.</p><p><a href="https://chaos.social/tags/dependencyManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dependencyManager</span></a> <a href="https://chaos.social/tags/swiftPM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swiftPM</span></a> <a href="https://chaos.social/tags/CMake" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CMake</span></a> <a href="https://chaos.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>programming</span></a> <a href="https://chaos.social/tags/cocoaPods" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cocoaPods</span></a> <a href="https://chaos.social/tags/fileExtension" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fileExtension</span></a></p>
Uli Kusterer (Not a kitteh)<p>Reminder to self: If you have a branch-reference to a Swift Package and want to pull the newest changes, delete foo.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved and SourcePackages in DerivedData.</p><p>Otherwise it will stubbornly stick to pulling the same commit over and over again, even if you do "Update Packages", because "branch(foo)" is still the same version and doesn't need updating, apparently.</p><p><a href="https://chaos.social/tags/swiftlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swiftlang</span></a> <a href="https://chaos.social/tags/swiftpm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swiftpm</span></a> <a href="https://chaos.social/tags/xcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xcode</span></a></p>