home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.programmer.misc
- From: tfj@apusapus.demon.co.uk (Trevor Jenkins)
- Path: sparky!uunet!pipex!demon!apusapus.demon.co.uk!tfj
- Subject: .OBJ file format
- Distribution: world
- References: <1992Dec11.101344.2664@neptune.inf.ethz.ch>
- Organization: Job hunters use Parachute
- Lines: 33
- Date: Fri, 11 Dec 1992 20:24:38 +0000
- Message-ID: <724105478snx@apusapus.demon.co.uk>
- Sender: usenet@demon.co.uk
-
-
- In article <1992Dec11.101344.2664@neptune.inf.ethz.ch> bronstei@inf.ethz.ch writes:
-
- >
- > Is there anywhere a complete description of the .OBJ file format for
- > progs supposed to link correctly with MS C 7.0 files?
-
- I found a very useful file with this information in by calling up the
- Microsoft BBS on +1-503-645-6275. The file name was something line
- "SS036.EXE". The major omission is any real discussion of CodeView specific
- records.
-
- > This is for
- > writing an Oberon compiler and the resulting .OBJ files should be linkable
- > with modules written in C. The executables are supposed to run under
- > Windows 3.1.
-
- The document(s) from the above file don't cover the instruction sequences
- that you ought to be generating for W3.1 compliant calls. I found some of
- the required info in "The Windows Programmer's Guide to DLL and Memory
- Management" by Mike Klien published by Sams (ISBN 0-672-30236-5).
-
- > Any help?
-
- Hope that's useful.
-
- Regards, Trevor.
-
- ---------------------------------------------------------------------------
- Trevor Jenkins Re: "deemed!"
- 134 Frankland Rd, Croxley Green, Rickmansworth, WD3 3AU, England
- email: tfj@apusapus.demon.co.uk radio: G6AJG
- phone: +44 (0)923 776436
-