I have an idea, which was already almost presented by some of you.
Based on an idea of restructuring our source tree (from some of devs included Amine, iirc), which consists in classifying our things into, e.g. : NTOS (for kernel + ntdll + some other things) Drivers Win32ss (win32k + user32 + winsrv / basesrv) Audio Applications Etc We could perhaps have a solution for each of these items, which would maybe shorten the time of loading. Hermès BÉLUSCA - MAÏTO De : ros-dev-boun...@reactos.org [mailto:ros-dev-boun...@reactos.org] De la part de Ged Murphy Envoyé : samedi 12 janvier 2013 01:51 À : ReactOS List Objet : 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.kreu...@web.de> Reply-To: ReactOS List <ros-dev@reactos.org> Date: Friday, 11 January 2013 21:16 To: ReactOS List <ros-dev@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@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
