static-libraries

I'm trying to understand this LIB file business on Microsoft Windows, and I've just made a discovery that will - I hope - dispel the confusion that hitherto has prevented me from getting a clear grasp of the issue. To wit, LIB files are not the one kind of file that their file extension suggests they are. :: cd "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib" :: lib /nologo /list Ad1.Lib obj\i386\activdbgid.obj obj\i386\activscpid.obj obj\i386\ad1exid.obj obj\i386\dbgpropid.obj obj\i386\dispexid.obj :: lib /nologo /list oledb.lib o:\winmain.obj.x86fre\enduser\…\oledb\uuid\objfre\i386

I have a problem with linking my mixed language framework to a project. 1) I create framework with Swift and Objective-C classes. 2) Main logic was stored in Swift file. For example the class with method that calls NSLog("Swift log was called"). 3) Objective-C file has class that has method in which I create an instance of Swift class and call Swift-log method. 4) I link this framework with my Objective-C project, I can call all what I need in this project, but when I want to build this project I receive error " linker command failed with exit code 1 (use -v to see invocation) " And warnings:

I have a library I am building. All of my objects compile and link successively when I run either one of: ar rcs lib/libryftts.a $^ gcc -shared $^ -o lib/libryftts.so in my Makefile. I also am able to successfully install them into /usr/local/lib When I test the file with nm, all the functions are there. My problem is that when I run gcc testing/test.c -lryftts -o test && file ./test or gcc testing/test.c lib/libryftts.a -o test && file ./test it says: test: ELF 64-bit LSB shared object instead of test: ELF 64-bit LSB executable as I would expect. What am I doing wrong? What am I doing wrong?