www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript

c++ - lib files

↑ ↓ ← "Roger Scudder"<r.scudder rcn.com> writes:
How can I get more information about the lib files that are not documented?  In
particular what is the fastest way to determine the target platform and memory
model?  


-Roger 
Sep 01 2003
↑ ↓ → "Walter" <walter digitalmars.com> writes:
The first thing is to generate a .lst file from them using lib. Next,
extract one of the .obj files from it and run dumpobj on it. One of the
coment blocks should contain the memory model.

"Roger Scudder" <r.scudder rcn.com> wrote in message
news:bj07tb$2euj$1 digitaldaemon.com...
 How can I get more information about the lib files that are not

 particular what is the fastest way to determine the target platform and

 model?


 -Roger

Sep 01 2003