John Emmas wrote:
> functions contained in the other one). If I was programming in Microsoft
> VC++ I'd normally resolve this by exporting the relevant functions.
> Exporting them (I believe) tells the linker that any unresolved function
> addresses will be resolved at run time (hence, dynamic li
I'm trying to build a C++ project involving around 20 branches, the majority
of whose targets are shared library objects (DLLs). Two of the branches
seem to have circular dependencies (in other words, each one relies on
functions contained in the other one). If I was programming in Microsoft
VC+
2 matches
Mail list logo
