Is a framework a LIB, or a DLL

[HelloKitty]

im from windows world, so using windows terms please,
Is a framework a LIB, or a DLL


I am currently using a framework as a dll replacement, i think.

I now want to make a LIB.
do I still make it a framework?


thanks

[DoG]

Originally posted by HelloKitty
im from windows world, so using windows terms please,
Is a framework a LIB, or a DLL


I am currently using a framework as a dll replacement, i think.

I now want to make a LIB.
do I still make it a framework?


thanks

if you need to make static libraries, you can, but a framework is a shared library + headers and version control.

Though, on MacOS X, making a shared lib is much easier than to make a DLL for Win32, as you don't have to deal with funky setup functions and symbol exporting. You just need to compile your code as a framework/shared library and link to it from your executable.

What IDE are you using?

[HelloKitty]

I am using project builder

Im a pc/linux programmer, and im being mentaly crushed by all the apple wierdness. :???:

the win32 version loads a LIB, which loads a DLL.

I have the DLL part already working as a framework on OSX.

I was/am confused about the LIB part now.

The project as a whole works as planned, I just havnt seperated out the code for the LIB on OSX yet.

so how should I make the LIB? as a framework, or a real static library.

how do you make a static library anyways?

thanks

[DoG]

Originally posted by HelloKitty
I am using project builder

...

how do you make a static library anyways?

thanks

You can just create a new static library target in your project, or a new project altogether, and make sure to link your executable with the built library (something.a).

And there is no apple weirdness here. You can build shared libraries as .dylib or .lib just as on any other BSD, if you don't want to use frameworks, though frameworks are the better option, since they are a little more sophisticated, yet just as easy to use.

As for how you should make the lib, I don't really see anything going against a shared library, since it can always be included within the executable's bundle, just in case its not installed on the system.