Ns-3 on Visual Studio
This is a page to summarize the Visual Studio compatibility work that Robert Ammon initiated during the ns-3.28 release cycle, and continues towards ns-3.29.
Some previous ports for older versions of Visual Studio (2010, 2012) can be found by searching the wiki, but are no longer maintained.
The ns-3 tracker issue is https://www.nsnam.org/bugzilla/show_bug.cgi?id=2726. A per-module status table can be found at https://www.nsnam.org/bugzilla/attachment.cgi?id=3088. As of ns-3.28 release (March 2018), the project is still working through the Phase 1 patches.
- 1 Summary of changes
- 1.1 Phase 1 – Visual Studio Compiler Warning Resolution
- 1.2 Phase 2 – Visual Studio Windows Conditional Compilation
- 1.3 Phase 3 – Visual Studio Class Declaration Changes
- 1.4 Phase 4 – NS-3 Implementation Changes for Visual Studio
Summary of changes
The following provides a summary of the changes for the Visual Studio Development environment. It highlights the changes necessary to the existing NS-3 files to support development for Windows using Visual Studio.
To support integration of the changes in a more manageable fashion, the changes necessary for the VS development environment are segregated into four phases. The four phases are defined as
- Phase 1 – Visual Studio Compiler Warning Resolution
- Phase 2 – Visual Studio Windows Conditional Compilation
- Phase 3 – Visual Studio Class Declaration Changes
- Phase 4 – NS-3 Implementation Changes for Visual Studio
Phase 1 – Visual Studio Compiler Warning Resolution
The changes in this phase are changes to the existing NS-3 source code files to eliminate compiler warnings under Visual Studio. Under the Visual Studio development environment, all compiler warnings are treated s errors. The changes for this phase eliminate the compiler warnings under Visual Studio. The changes mostly fall into the following categories:
- Elimination of automatic type casts to lower resolution data types (for example uint16_t to uint8_t)
- These changes either add static cast declarations or modify the code (if possible) to eliminate the need for a type case
- Elimination of unused function parameters
- These changes either eliminate the unused parameters (if possible) or add NS_UNUSED references to the parameter.
- Elimination of hidden variables (for example, a for loop using index i inside of a for loop using index i)
- These changes rename the inner variable that is hiding the outer variable.
The Phase 1 changes will be applied in first before the Phase 2, Phase 3 and Phase 4 changes. The Phase 1 changes apply to the majority of the NS-3 modules but not all modules.
Phase 2 – Visual Studio Windows Conditional Compilation
The changes in this phase are changes to the existing NS-3 source code files to add conditional code for the Visual Studio development environment. These changes add code that is executed under the Windows configuration only. The changes mostly fall into the following categories:
Code to the example programs to produce crashdump files under the Release configuration (similar to core files produced under the Unix variant operating systems).
Additional CrashHandler header
This includes adding an additional header file
#ifdef _WIN32 #include "CrashHandler.h" #endif
- Suggest adding this to
src/core/model/command-line.h, since all executables should (at least in the main tree) have a
CommandLineinstance. Pdbarnes (talk)
Instantiating the CrashHandler
And an additional installation function
#ifdef _WIN32 #ifndef _DEBUG CCrashHandler ch; ch.SetProcessExceptionHandlers(); ch.SetThreadExceptionHandlers(); #endif #endif
to each main program.
- What scope and lifetime does the
CCrashHandlerinstance require? Can it be a data member of
CommandLine? Or a global declared in
src/core/model/command-line.cc? Pdbarnes (talk)
Modification of existing code or addition of new code for the Windows configuration. For example
// Force DLLs to be loaded for modules loaded dynamically #ifdef _WIN32 LoadLibraryA("wimax.dll"); LoadLibraryA("uan.dll"); LoadLibraryA("wave.dll"); #endif
- Where does this stanza have to occur? In the main program? Can it occur in code in a dll itself (building dll A, which depends on dll B)? How can we leverage the module dependencies already captured in wscript files? Pdbarnes (talk)
The modifications in this phase affect a minority of the NS-3 source code files.
Phase 3 – Visual Studio Class Declaration Changes
While the Windows DLLs are similar to the Unix shared libraries, there are a couple of significant differences between them. One of the differences which cause changes in the NS-3 source code is items in a Windows DLL are hidden from consumers of the DLL unless specifically identified as exported items. This means that the classes in the NS-3 modules that are accessible by other NS-3 modules or user programs. This change adds a new DLL to the core module and an additional conditional declaration to each class declaration.
NS3DLL.H code fragment #ifndef NS3DLL_H #define NS3DLL_H #ifdef _WIN32 #ifdef _ANT #define NS3ANTLIB __declspec(dllexport) #else #define NS3ANTLIB __declspec(dllimport) #endif ... #else #define NS3ANTLIB ... #endif #endif /* NS3DLL_H */
NS3ANTLIBrefers to the antenna module. In the current proposal a stanza like this exists for every module. The build system toggles the
_MODULEflag for the module DLL currently being built, so its symbols are marked
dllexport, while symbols in all other headers (which this module depends on) are marked
dllimport. Pdbarnes (talk)
- Here's a decent discussion: https://gcc.gnu.org/wiki/Visibility Pdbarnes (talk)
Example class declaration
class NS3ANTLIB AntennaModel : public Object
The modifications in this phase affect almost every header file in the NS-3 source code.
Phase 4 – NS-3 Implementation Changes for Visual Studio
In a few of the NS-3 implementations, there are differences in the implementation between Linux and Windows. These are cases where the same source code does not produce the exact same results, either to differences in the OS, third party libraries of compiler code generation. For these changes, the source code has been modified to produce equivalent behavior on all platforms that matches the original implementation.
The number of changes in this phase are limited to a few examples.