Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS

[Hermès BÉLUSCA - MAÏTO]

>   If you would like to change the structure of the
> existing ReactOS 
repository for a different reason, well, OK…but if the load time is the only
reason…

No of course ! If you can arrange this problem in a more elegant way. But I
was also referring to a project some devs had in mind, in case it would be a
“solution” to the problem.

 

Hermès

 

 

De : ros-dev-bounces(a)reactos.org [mailto:[e-mail]] De la
part de J. C. Jones
Envoyé : samedi 12 janvier 2013 20:09
À : 'ReactOS Development List'
Objet : Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS

 

The problem with the load time exists because we are not doing something
that we should be doing. If we do that thing, the problem goes away. If you
would like to change the structure of the existing ReactOS repository for a
different reason, well, OK…but if the load time is the only reason…

 

[Remember what I said to you about French versus American bread, Hermès. J]

 

-John

 

From: ros-dev-bounces(a)reactos.org [mailto:[e-mail]] On
Behalf Of Hermès BÉLUSCA - MAÏTO
Sent: Saturday, January 12, 2013 7:48 AM
To: 'ReactOS Development List'
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS

 

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-bounces(a)reactos.org [mailto:[e-mail]] 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.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