Re: Post Build - Multiple Projects/Platforms

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Mon, 26 Mar 2007 16:51:27 -0700

Message-ID:

<eWaKsGAcHHA.4632@TK2MSFTNGP03.phx.gbl>

Consider externalizing those DLLs as a separate deliverable.
Then you never compile them - a separate team is responsible
for that and you only import their output - headers and implibs.
Essentially that's like a third party library you depend upon
with the only difference being that the library (libraries in your
case) is developed in house.

Since I know very few details about your environment, you'll
likely have to adapt my advice to your unique situation...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Yudi" <yudilevi@gmail.com> wrote in message
news:1174831642.576540.44280@p15g2000hsd.googlegroups.com...

Hello,

I'm trying to figure out how to set a project which is dependent on a
dll, and compile that dll only once.

I would still like to use visual studio's (I'm using VS 2005)
mechanism of copying the dll in the post build step to the output
folder of the main project, since I'm working with multiple platforms
(win32, PPC etc) and it's very convenient that the dll is
automatically copied to the output folder based on the active platform
- manually copying it every time is a pain.

I'm looking for such a solution since we are several people that are
working on the same solutions and there's no need for us to compile
the dlls (there are several of these) every time we want a full build
- we want these to be pre compiled once, and then just copied to the
output folders each time we build our main project.

Any idea how to set this up?