Bochs

History

Bryce Denney 1ee55d9edb - move some makefile stuff that is common to all subdirs into common-make-defs.txt		2002-10-16 04:09:24 +00:00
..
Makefile.in	- move some makefile stuff that is common to all subdirs into	2002-10-16 04:09:24 +00:00
module1.cc	- rewrite DLL macros, now somewhat closer to how LT_SCOPE is written	2002-10-11 16:09:21 +00:00
module1.h	- change #warnings so that they are informative, instead of "case 1,2,3"	2002-10-11 16:25:49 +00:00
module2.cc	- rewrite DLL macros, now somewhat closer to how LT_SCOPE is written	2002-10-11 16:09:21 +00:00
module2.h	- change #warnings so that they are informative, instead of "case 1,2,3"	2002-10-11 16:25:49 +00:00
README	- in bochs-testing area, check in shared library tests that I wrote while	2002-10-11 14:51:27 +00:00
uselib.cc	- call exit(77) for success. 77 was chosen arbitrarily; it is unlikely that a	2002-10-16 04:07:58 +00:00
uselib.out.expected	- check in expected output from each program	2002-10-16 04:08:24 +00:00

README

test4-interdep

Can one module reference objects in another module? Yes.

module1 exports module_name and operate(int,int).
module2 exports n_operations and operation_occurred().

uselib.cc uses symbols and functions from both modules.
Module1 calls operation_occurred() in module2.

To do this, module2 must be built first.  Then module1 is linked
against module2 so that the missing symbols are available.  Then,
uselib is linked against both.

This shows that we can chain libraries.  I haven't seen any way to
resolve a circular dependency, where mod1 depends on mod2 and vice 
versa, in win32 DLLs.  Probably those are not supported.