NewLC - How to dump DLL exports using LIB files - Comments

> How to dump DLL exports using LIB files

Anonymous — Fri, 12 Jan 2007 05:44:37 +0100

Yes but CLIndex just provides a UI to the Microsoft dumpbin.exe executable.

> How to dump DLL exports using LIB files

Anonymous — Fri, 26 Nov 2004 15:44:43 +0100

Also check out the fabulous CLINDEX tool, completely free of charge from EMCC Software!

> How to dump DLL exports using LIB files

dmitril — Tue, 21 Sep 2004 02:28:45 +0200

Correction.

To handle files with extension .LIB as well as .lib, file 2 should be changed to:

File 2: epoc_dump_and_export.pl:

# Purpose: enumerates all EPOC .lib files in the given directory and dumps ordinal:name pairs # Usage: perl epoc_dump_and_export.pl directory # Requires EPOC version of objdump on the PATH, File::Basename Perl module and # epoc_exports.pl in the same directory as the present file. use File::Basename; $dir=shift(@ARGV); $our_dir=dirname($0); opendir(DIR, $dir) || die "can't opendir $dir: $!"; while(defined ($file = readdir(DIR))) { next unless $file =~ /\.lib$/i; $path = "$dir/$file"; print("$path\n"); system("objdump --disassemble-all --demangle $path | perl $our_dir/epoc_exports.pl > $file.exp"); } closedir DIR;

How to dump DLL exports using LIB files

jhnlmn — Wed, 15 Sep 2004 23:11:56 +0200

Sometimes it is necessary to figure out what system API functions my application is linked to. On other occasions it is needed to find an ordinal of an exported function. This ordinal can be passed to RLibrary::Lookup (TInt anOrdinal) for dynamic linking.