Great thanks!
On 8 Sep 2011, at 14:18, Sascha Zelzer wrote: > Hi, > > On 09/07/2011 03:49 PM, Clarkson, Matt wrote: >> >> 1.) As a developer, I compile everything in Debug mode, then using >> StartVS_Debug.bat to launch Visual Studio, i should be able to launch the >> application directly from within Visual Studio for debugging purposes. I >> don't need to run the startApplication_Debug/Release.bat file to launch my >> application as Visual Studio already has the correct path, so Visual Studio >> should run the binary directly. > Yes, completely correct. >> >> 2.) When it comes to a full "make install" or "make package", then I HAVE >> to be in Release mode, and the final application thats generated should be >> launched using the startApplication_Release.bat file? >> > The first part (about Release mode) is correct, but the installed/packaged > application should be launchable by double-clicking on its .exe file. There > also should not be startApplication_Release.bat file in the installation > folder. > > Since all libraries which are needed by the .exe file are copied into the > same folder as the .exe file during packaging/installation, Windows will find > the library dependencies by itself (it first looks in the application path). > > Best, > Sascha ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
