If you really insist on circumventing Xcode, you should just go and use "make", which will probably be the same pain as trying to use Code :: Blocks. Although Xcode may seem strange at first, it really saves you a lot of headache to drink kool help and deal with it, especially if you plan to develop commercial VST plugins. For example, if you do not like the editor, then you can easily replace it with another choice. But, acting as the Mac VST developer here, the biggest advantage of Xcode is that it handles the “macrocentric” things well; those. creating the right bundles, universal binaries, editing resources, binding to system frameworks, etc. In addition, all the documentation,which you will find there (plus other online VST developer communities such as KVR) are Xcode users.
, , .:)
, VST , , IDE, , , . , , - VST , . VST SDK, :
- ApplicationService
- QuickTime
... , , , , Carbon . UB, , G4/5. PkgInfo, , : "BNDL????" ( , ). Info.plist , , , , Finder. , , , VST .