c++ - How to test compiled DLLs in Visual Studio (or produce several executables)? -
i'm developing shared library needs tested , profiled regularly. main target platform linux (generally) our team chose autotools (auto[scan,conf,make] + libtool + pkg-config) buildsystem. client decided wants software on windows too. added visual studio solution. library compiles, links , works on windows too, though development cycle lacks proper testing on windows.
i'm using automake's test suits on linux , test this:
make check -j2
which compiles 10 executables (client server pairs) linked library (which built on same buildsystem) , runs them (in pairs, ordered). output is:
make[3]: entering directory 'somefakepath/libfoo/test' pass: tcp_client pass: tcp_server pass: tcp_client_control pass: tcp_server_control pass: udp_client pass: udp_server pass: udp_client_raw pass: udp_server_raw skip: udp_client_rtp skip: udp_server_rtp ======================================================== testsuite summary libfoo 5.0.1 ======================================================== # total: 10 # pass: 8 # skip: 2 # xfail: 0 # fail: 0 # xpass: 0 # error: 0 ========================================================
the problem can't find way same in visual studio. i'm okay adding project solution (to make executables not libraries) though far know, it's not possible produce several executables single project in visual studio [1], [2]. , not feel right add ten projects, many configuration parameters set same values every single 1 of them... , choice of having single executable many threads not (i have change many lines, merge many[=10] files).
so how test library on visual studio? or maybe generate more 1 exetable several files in single project? ( can run them manually)
if difference between executables conditional compilation macros should create single executable project several configurations (i.e. udp_client_raw configuration, udp_server_raw configuration , on). if different in other aspects may still need create separate project. notice there no need set many configuration parameters same value - can make property sheet once , attach projects.
there no problem produce several executables single project. need build multiple configurations @ once using either batch build within visual studio or using msbuild command line. possible set project launch them in pairs testing purposes.
Comments
Post a Comment