is because some build systems seem to mess up the parallel build of these two
things and sometimes rebuild and potentially clobber object files during the
parallel build.  I haven't seen this result in a problem, but the race
condition does seem to exist in some build systems.  So this should force the
two top level targets to be build sequentially rather than in parallel, thus
avoiding any possible race condition.

arbitrary matlab objects.

doesn't work correctly in visual studio since visual studio doesn't define __cplusplus
to 201103 even though the current version ostensibly supports C++11.

Fix #363 by not setting CUDA_HOST_COMPILER when targeting Visual Studio

Fix Visual Studio build by not setting CUDA_PROPAGATE_HOST_FLAGS to OFF

Solution: don't set CUDA_PROPAGATE_HOST_FLAGS to OFF when using Visual Studio

using train_one_step(), you will get the behavior of automatic disk syncs at
the end of training.

partial C++11 support and funny cmake behavior of clang on OS X.

to new versions of clang on OSX, without this extra statement C++11 wasn't
being enabled.

map_output_to_input() in the concat_ layer.