From mboxrd@z Thu Jan 1 00:00:00 1970 From: Axel Siebenwirth Subject: Re: .so, .a and .o-files Date: Thu, 15 Aug 2002 19:19:50 +0200 Sender: linux-newbie-owner@vger.kernel.org Message-ID: <20020815171950.GA28935@prester.freenet.de> References: <20020815153420.GA10981@prester.freenet.de> <5.1.0.14.1.20020815083919.02181c50@celine> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <5.1.0.14.1.20020815083919.02181c50@celine> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Ray Olszewski Cc: linux-newbie@vger.kernel.org Hi Ray! On Thu, 15 Aug 2002, Ray Olszewski wrote: > .o is an object file. It represents the intermediate step in the > compile-and-link process for a program. .so is a shared object file (i.e., > a library); their linking (at runtime) is managed by ld.so . Ok. So I compile from sources many .o's and link them together into an .so and I have a shared library. > Depends on how you link. Modern linking is done dynamically (only one copy > of the library is loaded into memory and shared by all apps that use it), > using .so libraries. Older linking was done statically (each app loaded its > own personal copy of the library into memory), using .a libraries. I figured out that when a program is statically linked, the libraries are in the executable itself so no additional libraries are required...? Regards, Axel - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs