All geek questions in one place

Cocoa without Xcode

I would like to develop Mac applications, but I do not want to use Xcode. I have many reasons ...

  • It is very slow ...
  • Difficult...
  • The Builder interface looks like a hoax and not so nice. (I know the old school)
  • The whole set of developer tools takes up a lot of space and takes a lot of time to load (meanwhile slowing down the rest of my computer).

I know this is possible because I saw some scripts compiled with gcc. Are there any textbooks? Are there any tips? I know how to run it, but I just need help to find out how to use it without Xcode code for me. Is this a good plan, or is it just for failure?

+6
source share
4 answers

AppCode

AppCode is a development environment for Objective-C developers creating native Cocoa applications for MacOS X or iOS that seek to improve coding performance and better code quality.

EditRocket .

EditRocket can compile and execute Objective-C programs. EditRocket uses the gcc compiler to compile Objective-C programs

GNUstep .

GNUstep provides a robust implementation of the AppKit and Foundation libraries, as well as development tools available on Cocoa, including Gorm (InterfaceBuilder) and ProjectCenter (ProjectBuilder / Xcode).

THE COCOTRON

Cocotron is an open source project whose goal is the cross-platform Objective-C API, similar to that described by Apple Inc. Cocoa This includes AppKit, Foundation, Objective-C runtimes, and supporting APIs such as CoreGraphics and CoreFoundation.

.
Take a look at creating and running a Cocoa Mac application on the command line .
Xcode Alternatives for iPhone Design? (OR: how to make Xcode suck less?) .

+12
source

I'm not sure what code you think Xcode generates for you, but if you want to use a different IDE, then you are free. Xcode includes all the standard UNIXy command line tools (although from 4.3 you can explicitly make them available by running Xcode exactly once and checking the box in the settings), so you should use standard GCC methods.

In addition to the observation cited, for example, here , which you want to link to the Foundation base, there really is not much to say.

For the record, the interface designer does not generate any code and therefore no more "deceives" than using a paint package to draw your graphics.

+5
source

or is it just for failure?

Maybe. Apple makes the development of OS X and iOS very tightly tied to the use of Xcode, especially if you intend to send applications to any store. You will spend a lot of time on how to do something non-Xcode.

Looking at your glasses in turn:

  • More than using x many different tools to achieve the same thing?
  • See 1.
  • You do not need to use an interface constructor if you do not want this, but your reason (“trick”) is meaningless.
  • In most cases, this is the documentation that you will need in any case. It is very well integrated into the editor if you use Xcode.
+5
source

you are going to spend more time massaging your custom environment than you will be spending just drinking kool help.

It is wise to use some other text editor and use xcode to edit your build environment, then you could freely execute builds from the command line .........

+1
source

Source: https://habr.com/ru/post/908727/

More articles:


All Articles