[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: DLL creation and static libs
From: |
Charles Wilson |
Subject: |
Re: DLL creation and static libs |
Date: |
Wed, 03 Nov 2010 23:52:58 -0400 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 |
On 11/3/2010 12:23 PM, Matěj Týč wrote:
> On 2 November 2010 13:26, Charles Wilson wrote:
>> On 11/2/2010 2:14 AM, Ralf Wildenhues wrote:
>> ...
>> the problem is there are TWO different libuuid's. There's the one that
>> is part of the win32 api, and simply contains a number of static objects
>> that represent UUIDs of elements of the Windows OS. [1] Then, there's
>> the unix-derived one that provides routines for *generating* new UUIDs. [2]
>
> I thought of the nm tool. It could be used to identify which library
> is which, although AFAIK, it can't be used to generally identify
> libraries that contain data only. Is that correct?
Well, as long as we're special casing, we can look for a *specific*
public read-only data item:
nm -B libuuid.a | grep ' R _IID_IUnknown'
that should only appear in the w32api version, and not in the unixy one.
--
Chuck