[OpenSPIM] Fwd: Re: [micro-manager-general] Building MM in VS2012 on Win8 Issues and fixes (and understanding why)

[Johannes Schindelin]

Hi Luke,

I re-Cc:ed the list because I feel it to be inappropriate to keep this
conversation a secret from our collaborators.

On Fri, 14 Jun 2013, Luke Stuyvenberg wrote:

> [...] our rebase is going to be painful.

Not really, *iff* we wait until Mark switches their HEAD to 2010, and
*iff* you simply delete all of our changes to .vcxproj files.

> Personally, I'd like to suggest we just accept Micro-Manager's changes
> to all vcxproj and sln files (or not apply any of our own, as the case
> may be), then fix our build when the dust settles. It isn't ideal, but
> at least this way we have a well-defined conflict resolution for those
> files...

Right. That's what I meant by: our work was basically wasting time because
we cannot continue to use those changes.

Unless you disagree, let's focus more on early collaboration on things
that are not specific to OpenSPIM.

> While we're on the topic of the build system, I wanted to run an idea
> past you -- that is, adding VS projects for the Micro-Manager plugins
> and acquisition engine. For people less inclined to build from the
> command line, it may be helpful to create these projects and add them to
> our working solution (most likely after the VS2010 update and our
> rebase). The basic idea is much like that of Micro-Manager; I will
> probably just have the project use NMake to call the ant build files of
> the plugins and acquisition engine. (Especially considering since we say
> 'press F7 to build it all', it would make sense to do this.)

I agree. The easier it is to build it all, the better. Remember: I want
Jenkins to build this thing eventually.

Ciao,
Dscho