1 / 7

Building and running software on WNT with Visual Studio and CMT

A step-by-step recipe for building and running software on Windows NT using Visual Studio and CMT. Learn how to install the necessary tools and navigate the workspace for efficient development. Recommended for those who prefer debugging on Windows instead of Linux.

tomr
Download Presentation

Building and running software on WNT with Visual Studio and CMT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Building and running software on WNT with Visual Studio and CMT A step by step recipe

  2. Prerequisites • You need a PC running WNT.... • You need to install: • Windows AFS client • See a system manager • Visual Studio 6.0, service pack 2 • Available from NICE • Visual Fortran 6.1A • Available from NICE • CMT must be installed on disk visible from your PC • On the S: disk at CERN • Installation details at: • http://lhcb.cern.ch/computing/Support/html/DevStudio/

  3. Install CMT add-in • Tools Menu > Customise... > Add-Ins and Macro Files tab > Browse... Button • Browse to S:\LHCb\Software\NtUtils\CmtAddIn.v2.dll

  4. 1. getpack • Gets package tolocal CMT area • Creates DevStudioworkspace • Using CMT requirementsfile

  5. 2. Open the workspace • File > Open Workspace... Menu • navigate to the "Visual" subdirectory of your package • open file called <packagename>.dsw • Workspace must be updatedif requirements change: • Build MSDEV • Reload open projects

  6. 3. Build and execute • If package consists of only one project (i.e. library) • Menu: Build > Build <package> • or F7 shortcut, or “build” icon on the toolbar. • If it consists of several projects • can select the projects one by one, or • build them all in one go: Menu Build > Batch build... • If package is an application, now ready to execute • Make sure that correct environment variables are set: • click on SetEnvironment button of the CMT toolbar • only needed first time you execute a particular program, or each time requirements change (equivalent to "source setup.csh" on Unix) • Menu: Build > Execute <program> • or Ctrl+F5 shortcut, or the “execute program” icon on the toolbar. • N.B.: execution directory is, by default, the directory in which the executable resides (usually Win32Debug). • To change: modify the working directory using Menu: Project > Settings... and change the Working directory in the Debug tab.

  7. Conclusion • Initial installation takes some time • CMT add-in, plus AFS access, (plus WinCVS), make working with LHCb packages in Visual Studio a pleasure • Recommended to anyone who does not like debugging on Linux! • Looking into providing a batch build environment for people without access to a Windows PC. • No excuse for not testing software on both Linux and WNT...

More Related