If you are having problems building the Stingray Studio libraries, try these solutions to common problems.
Make sure you are using a supported release of Visual Studio. For details, see http://www.roguewave.com/products/stingray.aspx, then click on Supported Platforms.
Stingray Studio libraries will not compile if the MFC source code is not installed.
The Build Wizard executable is in the utils directory. It can also be executed from the Program Group for the product. This executable generates the makefile for building the Stingray Studio libraries. For more information, refer to Section 2.2, "Build Wizard."
Click on Tools | Options… and select the Directories tab, and make sure that all of the directory settings are correct for your setup. It is not only important to make sure the include and lib paths are correct, but the executable path must also point to the Visual Studio bin directory in order to execute nmake.exe.
Also, make sure that the include and lib paths include only the directories of the current installation of Stingray Studio. Your directory settings may differ (depending on how your products were installed), but some sample directory settings are provided below.
Sample Executable path directory settings:
General directory structure:
<MicrosoftVisualStudioDirs> <stingray-installdir>\Bin C:\Windows\System32\msagent // 32-bit OS C:\Windows\System32\msagent64 // 64-bit OS |
<MicrosoftVisualStudioDirs> for VC++ 8.0 and 9.0:
$(VCInstallDir)bin; $(WindowsSdkDir)\bin; //1 $(VSInstallDir)Common7\Tools\bin; $(VSInstallDir)Common7\tools; $(VSInstallDir)Common7\ide; $(VSInstallDir); //2 $(VSInstallDir)\SDK\v2.0\bin; //3 $(FrameworkSDKDir)bin; $(FrameworkDir)$(FrameworkVersion); C:\Program Files\Microsoft Platform SDK\Bin; C:\Program Files\Microsoft Platform SDK\Lib; C:\WINDOWS\system32; C:\WINDOWS; C:\WINDOWS\System32\Wbem; |
| //1 | VC++ 9.0 on Vista/Windows 2008 Server only |
| //2 | VC++ 8.0 only |
| //3 | VC++ 8.0 and 9.0 only |
Sample Include path directory settings:
General directory structure:
<MicrosoftVisualStudioDirs> <stingray-installdir>\Include <stingray-installdir>\Regex\Include // optional <stingray-installdir>\RWUXTheme\Include |
<MicrosoftVisualStudioDirs> for VC++ 8.0 and 9.0:
$(VCInstallDir)include $(VCInstallDir)atlmfc\include $(WindowsSdkDir)include //1 $(VCInstallDir)PlatformSDK\include //2 $(VCInstallDir)PlatformSDK\common\include //3 $(FrameworkSDKDir)include C:\Program Files\MSXML 6.0\inc //4 C:\Program Files\Microsoft SDKs\Windows\v6.1\Include //4 C:\Program Files\Microsoft Platform SDK\Include //4 |
| //1 | VC++ 9.0 on Vista/Windows 2008 Server only |
| //2 | VC++ 8.0 only |
| //3 | VC++ 8.0 only |
| //4 | VC++ 8.0 and 9.0 only |
Sample Lib path directory settings:
General directory structure:
<MicrosoftVisualStudioDirs> <stingray-installdir>\Lib\<compiler_version>\<architecture> |
<MicrosoftVisualStudioDirs> for VC++ 8.0 and 9.0:
$(VCInstallDir)lib $(VCInstallDir)atlmfc\lib // 32-bit compilers $(VCInstallDir)atlmfc\lib\amd64 //1 (64-bit compilers) $(VCInstallDir)lib\amd64 //1 (64-bit compilers) $(VCInstallDir)PlatformSDK\lib $(VCInstallDir)PlatformSDK\common\lib //1 $(FrameworkSDKDir)lib C:\Program Files\MSXML 6.0\lib //1 C:\Program Files\Microsoft SDKs\Windows\v6.1\Lib //1 C:\Program Files\Microsoft Platform SDK\Lib //2 |
| //1 | VC++ 8.0 and 9.0 only |
| //2 | Common to VC++ 8.0 and 9.0 |
Sample Source directory settings:
General directory structure:
<MicrosoftVisualStudioDirs> <stingray-installdir>\Src <stingray-installdir>\Regex\Src // optional <stingray-installdir>\RWUXTheme\Src |
<MicrosoftVisualStudioDirs> for VC++ 8.0 and 9.0:
$(VCInstallDir)atlmfc\src\mfc $(VCInstallDir)atlmfc\src\atl $(VCInstallDir)crt\src C:\Program Files\Microsoft Platform SDK\src |
Notes:
$(VS_macro_name) are literals, are typed as shown, and are defined by the Microsoft IDE. Refer to Microsoft MSDN documentation for details of these IDE macro names.
The Regex paths are required only if the Regex checkbox in either the Objective Toolkit or Objective Edit build wizard is checked.
<compiler_version> represents "vc8" or "vc9" and <architecture> represents "x86" or "x64".
Beginning with Microsoft Visual Studio 2010, there is no longer support for global IDE directory paths, meaning that Tools| Options | VC++ Directories no longer exists. These settings have been moved to the project level as *.vcxproj file properties. To access these settings, go to Project | Properties | Configuration Properties | VC++ Directories. Please review the Migrating to Microsoft Visual Studio 2010.pdf document in the <stingray-installdir>\Docs directory for further details.
To facilitate the addition of paths to project files, Stingray projects add two property sheets to every VS2010 project: SS-Win32-PropSheet and SS-X64-PropSheet. The IDE paths for Stingray Studio have been added to those property sheets so the appropriate paths are picked up when a project is compiled. These property sheet files are located in the <stingray-installdir>\Src directory.
Property sheets are provided for all Stingray libraries and shipped samples for Visual Studio 2010, but if you are adding a new project or porting an old project to Visual Studio 2010, you need to add a relevant property sheet. To add our property sheet(s) to a project:
Select the Property Manager tab or go to to View | Property Manager.
Right click on the project and select Add New Project Property Sheet... or Add Existing Property Sheet.
Navigate to <stingray-installdir>\Src directory to select the desired Stingray Studio specific property sheet file.
The VC++ 10.0 library and associated VC++ 10.0 sample solutions use the following Stingray Studio specific property sheets:<stingray_installdir>\Src\SS-Win32-PropSheet.props
<stingray_installdir>\Src\SS-X64-PropSheet.props
You may use the Stingray Studio specific property sheets in your new or newly ported applications that link to Stingray Studio libraries. If you need to modify these files, we strongly recommend copying and renaming them before using them in your application in order to prevent Stingray VC++ 10.0 library and sample build errors.
View property sheets by going to the Property Manager tab. To edit an existing property sheet, open an appropriate configuration such as Debug, expand the project and the configuration, right click on the property sheet and select Properties. On the Property Pages dialog you can change project settings as needed. Keep in mind that changes made to a property sheet affect all configurations that contain the same property sheet.The property sheets for setting paths have been added to all shipped samples through their *.vcxproj project files. Here is an example of the entries pointing to these files:
<Import Project="..\..\..\..\..\Src\SS-X64-PropSheet.props" /> <Import Project="..\..\..\..\..\Src\SS-Win32-PropSheet.props" /> |
Note that if you wish to move a sample to another location or edit the sample's property sheet, the relative paths above may not be correct for the new location or new property sheet. Each build configuration's property sheet should be removed from the project using the Property Manager, and then re-added with the new location or new property sheet. This way, Visual Studio can adjust the path and filename to use the new file. Alternatively, the sample's *.vcxproj file may be edited manually.
Property sheets are added to each configuration in the project. It may be necessary to delete property sheets for configurations that do not require them. After a new property sheet is created, any available settings that are changed are applied to all configurations that contain that property sheet.
After loading the Stingray Studio project, be sure the desired library configuration is selected by clicking Build | Set Active Configuration.
You can also optionally add a selection control to one of your toolbars. Click Tools | Customize... on the Commands tab, choose the Build category. You should now see buttons that pertain to the build process. You should also see a selection control on the right side that you can drag to a toolbar. This control will display the current build configuration, and will allow you to change it quickly.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and Stingray, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.