The .sln will use .vcxproj files that will be generated by some method other than CMake. It would generate a single hierarchical solution, that contains 1 .sln file, and 800 .vcxproj files. What the user sees while using Visual Studio would have a one-to-one correlation with what the user would see by using Windows Explorer to view the ReactOS repository on this. I would do this for two types of developers:
1. those who only know Visual Studio, and therefore prefer Visual Studio
2. those who know Visual Studio and other development environments, but still prefer Visual Studio
-John
From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Conan Kudo (???·???)
Sent: Saturday, January 12, 2013 11:34 PM
To: ReactOS Development List
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS - Take III
So if I understand this correctly, the solution file will use vcxproj files generated by CMake to create a truly hierarchical Visual Studio development and build environment suitable for new developers who are only familiar with Visual Studio and using the IDE for development?
On Sat, Jan 12, 2013 at 1:47 PM, J. C. Jones <jaibuduvin@gmail.com> wrote:
Hi All,
I had quick chat with Amine and others, and for the time being, I will pick up where I let off in creating a Visual Studio ReactOS.sln with the following features:
1. A single ReactOS.sln file that is interchangeable between Visual Studio 2010 and Visual Studio 2012.
2. A single ReactOS.sln file that incorporates all 800+ .vcxproj files and allows all 800+ project to be viewable within a single session of Visual Studio.
3. No (serious) performance problems with load of the ReactOS.sln file or .vcxproj files.
4. An arrangement in the Solution Workspace that mirrors the structure of the ReactOS repository on disk.
5. The ability to build all applications or drivers by right-clicking, within Solution Workspace, on the folder named applications or drivers and doing clicking Build.
6. Visibility of the lang directories in the Solution Workspace.
7. Visibility of all SVN files in the Solution Workspace, including CMakeLists.txt files.
8. Support for Debug and Release project configurations.
9. Support for x86_32, x86_64, ARM platform configurations.
10. Self-relative paths for all .h’s and .libs’s so that solution can be moved by the developer on his/her local hard disk without consequence.
11. No need to download any extraneous tools. User should be able to type in SVN URL, either from within Visual Studio, or with Windows Explorer, pull ReactOS repository, load ReactOS.sln, and start editing/compiling/linking, debugging.
With the CMakeLists.txt files, the information needed is already present. With Amine’s latest work of actually generating the .vcxproj files, things become even easier. However, as I have two other moderate projects going concurrently, one of which I just started, this will take some time. I will provide updates as I go along.
Cheers,
-John
_______________________________________________
Ros-dev mailing list
Ros-dev@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: 2638/6030 - Release Date: 01/13/13