[OpenSPIM] All C++ developers: Transition to Visual Studio 2010

Mark Tsuchida marktsuchida at gmail.com
Wed Oct 9 12:32:50 CDT 2013


Hi All,

On Thu, Oct 3, 2013 at 6:34 PM, Mark Tsuchida <marktsuchida at gmail.com> wrote:
> Micro-Manager's Windows build is soon to make a long overdue switch from Visual
> Studio 2008 SP1 to Visual Studio 2010 SP1.
[...]
> Currently, I have a private branch of MM building with VS2010. The VS2010
> branch is maintained so that it is based off a recent head of the SVN trunk.
> I plan to merge this branch with the trunk, if nothing goes wrong, on
>
>   Thursday, October 10.
>
> The nightly builds will also switch to using VS2010 at that time.
>
> The consequence of the merge will be that all VS2008 project files (.vcproj)
> will be removed and corresponding VS2010 project files (.vcxproj) will be
> added. In addition, various changes will be made to allow MM to build with
> VS2010.
[...]
> The source code, patch set, and binary installers for the VS2010 branch are
> available here:
> http://valelab.ucsf.edu/~mtsuchida/ephemeral/expires-20131031/vs2010/

I have updated the patch set and installers (available from the same
link). The VS2010 test build now includes changes on the SVN trunk up
to yesterday (20131008 PDT).

I have also added a patch (22/22) that renames the Visual Studio
project files for some of the device adapters, where the name did not
match the name of the device adapter (the device adapter name is
generated from the project name in the Visual Studio solution used to
build, which, confusingly, can differ from the project filename). This
is a good opportunity to eliminate the inconsistency, since the
filenames are changing anyway (from .vcproj to .vcxproj). The
directory names containing the device adapter projects are also often
inconsistent with the project name and adapter name, but I'm leaving
this unchanged to prevent confusion (and repository administration
complexities).

All this will be merged to the trunk tomorrow (Oct 10). We may briefly
disable write access to the repository during the merge; progress will
be posted here.

Best,
Mark




More information about the OpenSPIM mailing list