Hi Dan,
Thank you for sharing this.
On Thu, May 26, 2016 at 12:17 PM, Daniel Kovari <
[hidden email]> wrote:
> I've had some success compiling device adapters under Windows 10 using
> Visual Studio 2015 Community Edition and thought if might be useful to share
> my experiences.
>
> Under Windows 10 you cannot install the Windows7.1 SDK which means that you
> cannot easily compile the devices following the instructions posted on the
> micro-manager webpage.
>
> To get around this problem you need to do a few things.
>
> 1) After downloading the micro-manager source SVN, you need to get an
> updated copy of the boost libraries.
This is probably only necessary if the device adapter you're building
uses non-header-only parts of Boost. This is relatively uncommon but
definitely the case with a few.
[...]
> Be sure to change the toolset for all the dependent projects too:
> MMcore
> MMCoreTest
> MMDevice-SharedRuntime
> MMDevice-StaticRuntime
> LibraryTest
> DeviceTest
The only dependency of a device adapter is MMDevice-SharedRuntime
(except for some device adapters that use MMDevice-StaticRuntime
instead, for compatibility reasons).
[...]
> I haven't done a lot of testing yet, but so far the test programs and
> DemoCamera build without issue. The generated DemoCamera dll also appears
> to work with the current nightly build of Micro-Manager1.4
> (MMSetup_64bit_1.4.23_20160523), even though that build was probably
> compiled using the old (Win7sdk) toolset and boost 1.5.
The device interface is intensionally designed so that the compiler
version need not be equal. The official build statically links any
non-header-only parts of Boost, so there should be no clash there
either.
> I know that the development team is busy working on Micro-Manager2.0 but
> while that is in development I think it would be nice if we could update
> Micro-manager 1.4 to include a more recent version of boost by default.
> Assuming people will always be able to write new device adapters using VS
> 2010 isn't really an option as it appears that Microsoft is actively phasing
> it out. (Even under windows 7 it's really hard to get a copy of VS 2010
> express with Win7.1 sdk to install properly.)
We'll definitely update to VS2015 as soon we've released 2.0, and
probably update Boost at the same time (to make it one job instead of
two). Is there a particular reason why a newer Boost is needed for
VS2015? (I can see that you would need a Boost built with VS2015 if
using non-header-only parts, but that's different from the Boost
version.)
We'll probably also stop providing a Boost build of our own, instead
providing complete instructions or a script for building Boost on
Windows for use with Micro-Manager. (For terse notes on how the
current version was built, see
3rdpartypublic/boost-versions/build-1_55_0-VS2010.bat.)
Best,
Mark
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports.
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general