On Tue, Jul 23, 2013 at 3:47 AM, Graham Reeds <graham.re...@gmail.com>wrote:
>
> Will you be pushing a version that does not need to be linked to U: drive?
>
The U: drive part is an artifact of using CMake to generate all of those.
See https://github.com/unittest-cpp/unittest-cpp/issues/47. Unfortunately I
do not current have a Windows development environment so I can't regenerate
or even load those; any changes I make would be by hand. I think at this
point I'm leaning towards option 2) on
https://github.com/unittest-cpp/unittest-cpp/issues/42.
On the topic of folder layout I was wondering about combining the x86 and
> x64 projects into one and adding the $(PlatformName) to the end of the
> project.
>
Another artifact of switching to CMake. See above.
> Can someone tell me what happens if you open a project which has
> information for x64 on an x86 system? Will there be any warnings/errors?
>
I don't remember with certainty, but I think everything works just fine,
since the MSVC toolchain can be all 32-bit applications. However, it may
not link and it certainly won't be able to run the UTs.
pj
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
unittest-cpp-devel mailing list
unittest-cpp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
