Ok. VS2010+ it will be. J
I will do a quick review to make sure that we can get all the multiple-CPU
development features, etc. and report back.
Cheers.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Aleksey Bragin
Sent: Friday, January 04, 2013 1:25 PM
To: ReactOS Development List
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
It's up to you of course, but VS2008 is too dated, and VS2012 is "too new"
indeed, so many devs will cry about incompatible project files.
So, VS2010 would be the ideal bet, as Ged said.
Regards,
Alex Bragin
On 04.01.2013 23:21, J. C. Jones wrote:
Yes.
But initially, I wanted to make it so that anyone, especially a newbie,
could go from discovering ReactOS, to an edit-compile-link-debug cycle of
"Hello, World!" within the IDE in 30 minutes or less (not the OS, just a
single app). That means accommodating whatever version of Visual Studio they
are using. VS2008 is safe, because, no matter which version they are using:
VS2008, VS2010, VS2011, or VS2012, the conversion would be done
automatically, on their machine, and since the project files in SVN would be
locked, there'd be no harm done to SVN using this method. However, if I
start out with VS2012, for example, then, sure, they could go and download
VS2012 alongside say, VS2010.but my goal was to present a totally new user
with the SVN URL for ReactOS, and say, "Here is is. Give it a try!", and
remove all excuses for them trying it out. [I figured that having to install
a 1GB+ tool alongside a very similar tool was a bigger excuse for most
newbie developers than having to wait < 5 minutes to watch the VS2012 do its
conversion.]
That said, if Visual Studio users came back and said, "We're not using
VS2008 anyway!" then I would change it, and I am definitely open to ideas on
this.
Sent: Friday, January 04, 2013 3:43 AM
To: 'ReactOS Development List'
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
VS2008?
Shouldn't you be doing this in 2012, especially considering the much
improved support for kernel mode projects.
At the very least you should be using 2010 as 2012 can open 2010 project
without modification to project files.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of J. C. Jones
Sent: 04 January 2013 02:40
To: 'ReactOS Development List'
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
Yes, it is one thing to create a project file, which takes 15-30 seconds. It
is another thing to get the configuration right. Fortunately, there are
copious notes and highly-readable scripts in the tree which practically say
what needs to be done, so I do not anticipate any major hurdles.
I spent a little time in the source tree today. I integrated a few modules
into Visual Studio 2008, an tested calc, by buiding it from within Visual
Studio for x86-32 and x86-64. It ran fine, thanks to the author(Mr. Carlo
Bramini) who left good notes in his source code. Just for kicks, I also
created an ARM-based project that would run on the Raspberry Pi, compiled it
from within VS2008, and ran it inside the emulator that comes with VS2008.
That ran fine also. Tomorrow I will ask a colleague to try the following:
1. Pull the repository to his local hard disk from inside Visual
Studio.
2. Hit Build.
3. Run calc in an edit- compile-debug loop.
From: ros-dev-bounces(a)reactos.org [mailto:ros-dev-bounces@reactos.org] On
Behalf Of Timo Kreuzer
Sent: Thursday, January 03, 2013 2:18 AM
To: ReactOS Development List
Subject: Re: [ros-dev] Notice Of Intent - Visual Studio Build of ReactOS
Am 02.01.2013 19:04, schrieb J. C. Jones:
It would take 2-3 hours to create VS projects for all user-mode modules.
No offence, but I think you are highly underestimating the magnitude of our
codebase. We are talking about several hundred modules. And you probably
also overestimate the pace at which you can create project files. I did that
myself for a much smaller project, so I know what I'm talking about.
But maybe I'm wrong and they call you "The Machine" :D
_____
_____
No virus found in this message.
Checked by AVG -
www.avg.com
Version: 2013.0.2805 / Virus Database: 2637/6008 - Release Date: 01/03/13