Re: Using other projects

• Previous message: Victor Bazarov: "Re: Using other projects"
• In reply to: Victor Bazarov: "Re: Using other projects"
• Messages sorted by: [ date ] [ thread ]

Date: Fri, 14 May 2004 12:31:13 -0700

Victor Bazarov wrote:
> A Workspace defines dependencies. Dependencies are between
Projects.
> Projects are single-level subordinates of a Workspace. Workspaces
cannot
> depend on other workspaces. Does that answer your question?

Yes. Its a shame though. Having to duplicate a build definition
(workspace) everywhere it is used is a pain, especially when it
changes. Oh well...

> Static libraries don't use other libs. Strictly speaking, code may
> reference some external symbol, but where the symbol comes from is
not
> necessarily known until the link time (and libs are not linked by
> themselves, only exe's are linked). That said, see below.
> ...

Sorry, I'm aware of the technical details behind linking, I should
have been more explicit in my phrasing and in the reason I wanted
this. In many projects I always use specific libraries to resolve
external symbols for that project. I was hoping there was a way to
specify this in library's project definition in order to ease the use
of these libraries.

> #pragma comment(lib, "def.lib")

Thanks for the pointer. I probably wont use this since I don't want
to add this to the source code, but good info none the less.

Thanks Victor,
Josh

• Previous message: Victor Bazarov: "Re: Using other projects"
• In reply to: Victor Bazarov: "Re: Using other projects"
• Messages sorted by: [ date ] [ thread ]