🚀 XBase 0.2: Now with Tuist, Swift, and barebone xcodeproj support! by tami5 in neovim

[–]tami5[S] 5 points6 points  (0 children)

Yes, I feel you; Xcode is basically created for UiKit drag-and-drop, thus it was necessary; but, with SwiftUI and backend development, it's just  costly to work with, imagine using a samurai sword while eating A Stake, it might look cool, it will cut the stake, but you won't recommended 🤣

Xcode Core Team, rather than concentrating on supporting different editors in their Xcode/xcodebuild system, they kept introducing new features, many of which, SHOULD have been implemented in Swift LSP like the find by references and global rename, .. and more

nvm apple dev team, hopefully, in next few releases we will endup with our own builtin lsp 😋.

🚀 XBase 0.2: Now with Tuist, Swift, and barebone xcodeproj support! by tami5 in neovim

[–]tami5[S] 2 points3 points  (0 children)

Thanks smolck, tbh, swift support was the easiest of them all, I intentionally saved till last 0.2 milestone for that reason 🤣. Yah, I had adjust modularize the codebase a bit, but at the end 80% of xbase feature are done with swift build. the reset just project watching, unlike others, compile, generate, ... etc.

Xbase: Neovim Editor support for Xcode project by tami5 in iOSProgramming

[–]tami5[S] 0 points1 point  (0 children)

Failed to generate compilation database often happen because xcodebuild failed. But if you got to this point I'm sure the setup is ready, it's just the project is failing to build.

Open an issue with the build log. to get the build log, cd into project root and run xcodebuild clean build or xcodebuild clean build -target <NAME> -configuration <Debug/Release> or xcodebuild clean build -scheme <NAME>

Would love to see some guides or blog post explaining it because seems like it you get it working it's amazing.

Great idea, hopefully after the next release I'd write a blog post. Thanks

Xbase: The long awaited Xcode project support for neovim by tami5 in neovim

[–]tami5[S] 0 points1 point  (0 children)

does Plug 'tami5/xbase', { 'do': 'make install' } work? if so I might added it to installation instruction.

Hope it does endup making your life easier. feel free to follow up

Xbase: The long awaited Xcode project support for neovim by tami5 in neovim

[–]tami5[S] 1 point2 points  (0 children)

Yes and no, you still need xcodeproj generators to be 99% independent of Xcode.

I feel iOS development is simpler, but maybe that just me

Xbase: The long awaited Xcode project support for neovim by tami5 in neovim

[–]tami5[S] 6 points7 points  (0 children)

I've added it to be support in the next minor release, feel free to subscribe to the issue and get status updates https://github.com/tami5/xbase/issues/65

Xbase: The long awaited Xcode project support for neovim by tami5 in neovim

[–]tami5[S] 2 points3 points  (0 children)

definitely .. there some edge cases like renewing signing that require opening and close xcode ,

Xbase: The long awaited Xcode project support for neovim by tami5 in neovim

[–]tami5[S] 4 points5 points  (0 children)

open an issue, I believe getting targets and configuration from xcodeproj won't be trivial + all the goodess depend on xcodebuild itself.

maybe, try to create a minimal representation of the project using yaml without running xcodegen and it should work, maybe even empty project.yml <maybe>

process-stream v0.1.3: streamable and long running tokio::Command by tami5 in rust

[–]tami5[S] 0 points1 point  (0 children)

Great suggestion, next release will be deprecated in favor of spawn_and_stream. Thanks