Stingray Studio : Getting Started Guide : Chapter 2 Building the Libraries
Chapter 2 Building the Libraries
Quick Start
Pre-built libraries are not shipped with the Stingray installer, but it is easy to build them using Stingray Studio Assistant (accessible from the Start menu). From Assistant, you can select which libraries to build and launch Visual Studio with the desired solution file.
You can also build the libraries directly from Visual Studio. Use the solution (.sln) and project (.vcxproj) files found in <stingray-installdir>\Src to build the libraries. You can build each Stingray component individually using the component’s solution file, <Component><MFC version>.sln (Chart16.sln for instance), or build all components using the StingrayLibraries<MFC version>.sln solution file. Projects for base libraries (Foundation and RWUXTheme) are included into solutions for components and should not be built separately as a rule.
NOTE >> Do not use the Build Wizards. For most users they are not necessary at all.
When using Visual Studio, keep the following things in mind:
*You MUST run Visual Studio as an administrator. If you launch Visual Studio from Assistant, it launches in administrator mode by default.
*Upon launch, select the solution platform (Win32 or x64). Please note that if you are using a 32-bit product key for Stingray, building with x64 will fail.
*Solution configurations have various combinations of release, debug, ANSI, Unicode, static, and dynamic link to Stingray and the MFC libraries. For the first build, try Stingray DLL MFC DLL Debug (asd).
*To avoid possible Stingray build errors in Visual Studio, go to Tools->Options->Projects And Solutions->Build and Run and set “maximum number of parallel project builds to 1.
*Libraries are moved to a corresponding folder in <stingray-installdir>\Lib. For example, if you build with Visual Studio 2019 (VC++ 16) and x64, the libraries are in <stingray-installdir>\Lib\vc16\x64. You can also check on these libraries using the Lookup tab in Stingray Studio Assistant.
After building libraries, we recommend trying our shipped samples to verify the libraries were built correctly. Before running any samples with a dynamic link to Stingray libraries, make sure the path to the libraries with the correct solution platform was set in the system path. You can set the path environment variable directly or set the corresponding compiler version in Assistant.