".having one for each major area of the build but anything more would be
detrimental to the advantages of using VS."
Why?
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Ged Murphy
Sent: Friday, January 11, 2013 6:51 PM
To: ReactOS List
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
Having a solution for each project is like having a separate build system
for each project.
You could probably break it down to between 5-10 solutions, having one for
each major area of the build but anything more would be detrimental to the
advantages of using VS.
From: Timo Kreuzer <timo.kreuzer(a)web.de>
Reply-To: ReactOS List <ros-dev(a)reactos.org>
Date: Friday, 11 January 2013 21:16
To: ReactOS List <ros-dev(a)reactos.org>
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
Am 11.01.2013 06:48, schrieb BinSys:
I suggest a sln file in each directory. Only a sln file is too big, very
slow to load.
I agree, but before changing this, we should measure a possible performance
impact on the configure operation. (We are talking about generating a few
hundred solution files)
I don't know if it has any impact at all (especially for non-VS build), but
you never know...
_______________________________________________ Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
_____
No virus found in this message.
Checked by AVG -
www.avg.com
Version: 2013.0.2890 / Virus Database: 2637/6025 - Release Date: 01/11/13