Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Content-class: urn:content-classes:message
Subject: RE: duplicate error message in Windows builds
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Dec 2006 13:12:43 +0200
Message-ID: <F92433E3D38672499C549EB615AFADA0AC04CB@exkiv.kyiv.vdiweb.com>
Thread-Topic: duplicate error message in Windows builds
Thread-Index: AccZbCKkh0DjgJatQ0O9G7K7joxUPAAfNRxg
From: "Farid Zaripov" <FaridZ@kyiv.vdiweb.com>
To: <stdcxx-dev@incubator.apache.org>

> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]=20
> Sent: Wednesday, December 06, 2006 9:23 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: duplicate error message in Windows builds
>=20
> I don't think that's necessary. If dependencies among=20
> projects in the solution are set up correctly the Build=20
> method should be able to compute the number of failed=20
> projects simply by incrementing the counter for each project=20
> one or more whose dependencies it already tried to build and failed.
>=20
> Can you tell if our dependencies are set up correctly?

  Yes. MSVC project system have two way to setup project dependency:
"Project Dependencies" and "Project References". I don't know what the
difference,
except the project dependencies are stored in the solution file (.sln)
and project
references are stored in the project file (.vcproj). If I create
solution with 2 projects
(static library with exported function and executable project which is
uses that
exported function) and setup dependency or reference (or both) then MSVC
link
the executable with the library implicitly.

  We have the following dependencies:
- .stdlib depends on .configure;
- util_exec depends on .configure;
- .rwtest, util_localedef, util_locale, all examples projects depends on
.stdlib;
- .stdcxx_utils depends on util_exec, util_localedef, util_locale;
- .stdcxx_examples depends on all examples projects and util_exec;
- all tests projects depends on .stdlib and .rwtest;
- .stdcxx_tests depends on all tests projects and util_exec;
- all locales projects depends on util_localedef;
- .stdcxx_locales depends on all locales projects;
- all locale tests projects depends on util_exec, util_locale,
util_localedef;
- .stdcxx_testlocales depends on all locale tests projects.

  All dependencies established using both project dependencies and
project references
when possible (MSVC7.0 doesn't support project references; MSVC 7.1 and
MSVC 8.0 doesn't support project references in non-C++ projects
(.configure,
.stdcxx_utils, .stdcxx_examples, .stdcxx_tests, .stdcxx_locales,
.stdcxx_testlocales,
all locales projects and all locale tests projects);

> I think the best way to confirm whether it is or isn't=20
> possible to skip building projects whose dependencies failed=20
> is to create a small toy example solution with a couple of=20
> projects one of which depends on the other and see if=20
> invoking the Build method causes both of them to be build or just one.

  The example shows that both projects are trying to be build.

  BTW when single project is built, the all source files are compiled,
even if some errors
were found in the first compiled source file. I think situation with
building the solution
with a couple of projects is the same.

Farid.