Mac creating simple dylib? - objective-c

I need to create a dylib using XCode for my client. The dylib will have only two function start, and stop. The people i m making this for use mono and they will call this dylib. How can I create this?
Thanks.

Xcode has project templates for Cocoa, C++ and C dynamic libraries. Just create one of these and add you functions to it.

Related

Binding Objective C Reference

I'm trying to use a binding library (an Objective-C library) in my Xamarin Project. I followed all the instructions in the documentation.
When I try to use it I can't find it in the edit References/Projects. What do I need to do so that it shows up?
If the projects are in the same solution, and both projects are of the same type (Xamarin.iOS vs classic) Then it will show up under projects and you can reference it. Try making sure both of the projects have Xamarin.iOS in the references.

How can I use jEdit editor to code in Objective C on Windows

I'm new to Objective C.
I've installed jEdit on windows 7 and the gcc compiler too.
I need to know how to use jEdit to develop Objective C applications on windows
Thank you.
You just write the code in jEdit(with .m extension for files) and compile it. If you want to develop iPhone apps, you would have to do some other stuff because it would require extra libraries that's native to Macs. Easiest way would be to get a Mac, or you can look here for some info on doing it in windows:
http://www.taranfx.com/how-to-develop-iphone-apps-on-windows
You'll need an Objective C compiler, plus a set of frameworks like GNUstep. You can get both at http://www.gnustep.org. Work is ongoing, but there's a lot left to do, especially on Windows.

How do I create a Cocoa (Obj-C) Dynamic Library for OS X?

So basically I want to create a Dynamic Library in OS X that is built utilizing Cocoa (In Obj-C, not C or C++). My question is - how do I do this?
Ultimately I want the library to be loaded by another application (which I know how to do). I just don't know how to create a module utilizing Objective-C.
Thanks!
I suggest creating your own framework instead of a library.
Guide 1
Guide 2
If you're bent on making a Dynamic Lib then check this Guide 3 out. I recommend against dynamic libs because I believe they're banned/frowned upon by Apple when approving iPhone apps.
Frameworks will give you the same functionality, plus a ton more options for resources, headerfiles, etc. Plus, you'll be following Apple's design patterns which means your code will run better.

creating a reusable library in XCode 3.2

How do I create a reusable library/module in XCode 3.2? What I want to do is create a bunch of classes that provide certain functionality compile them into some kind of library, add such a library to an existing xcode project and use the classes in it.
I come from .NET world so what I want to do is basically to create an equivalent of 'assembly' and then reference it somehow in my XCode project.
I am developing for iOS btw.
If you add a target called static library you will get the equivalent of an assembly, just put all the sources in the target and decide what headers should be published and what should be hidden to the user of your library.
What you are looking to do is create a 'framework'.
This page has some useful information.
http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFrameworks/Frameworks.html

How do I start a new Obj-C library project with Xcode?

I am new to Xcode (and Objective C in general) and I want to create a new Objective-C Library (Framework?) which will be used by some of our iPhone applications in the future.
Which type of project should I choose when Xcode shows the new project dialog? I tried selecting "Blank Project" but then I faced some issues in defining the target, dependencies, etc.
I want my project to be easily re-usable in the future both in code form and as a .dylib.
I would appreciate some help with this. Links to online docs are welcome.
Since version 3 of the SDK you are able to create library projects in Xcode. However, those projects do not create .dylib libraries, but static .a libraries.
You cannot create Frameworks for iOS, as Apple's own App Store rules state that apps sold through the App Store cannot load code dynamically, which is what Frameworks are for. Libraries are designed to be statically linked.