|
From: Adam M. <mi...@oc...> - 2016-12-30 15:08:13
|
Hi Zareen,
On 12/30/2016 12:07 AM, zareen wrote:
> Just a gentle reminder regarding the previous issue about the July
> 2010 article on OpenDDS compatibility. I would like to know about any
> proceedings regarding the same.
I was able to build the sample code with OpenDDS 3.9 and Visual Studio
2010 after making the following changes:
1. DDSCodeGen.mwc
Replace two instances of the keyword "specific" with any other
identifier (for example "c_sharp" and "visual_basic"). MPC uses
"specific" for a different purpose at this place in the file.
2. DDSCodeGenBase.mpb
Add the following lines at the same scope as the similar lines for "libout":
Release::libpaths = $(DDSCODEGEN_ROOT)/Output/Release
Debug::libpaths = $(DDSCODEGEN_ROOT)/Output/Debug
After making changes to MPC's input files (*.mwc, *.mpc, *.mpb), make
sure to re-generate the Visual Studio solution.
3. Remove OpenDDS 2.x transport configuration
In Common/Common.h, remove the #include line that ends with
TheTransportFactory.h.
In Common/DDSBase.h, remove statements containing TheTransportFactory
and related code ("attach").
4. In the OpenDDS source code, make the change that David Cornelius
suggested in order to work-around a bug in Visual C++ compiler with
/clr. Build OpenDDS and the MNB example code.
> Also, there was no follow up of the mail sent by Steve Bowman.
I was told that he has been in contact with someone from your company
but we can handle that off of the mailing list.
Thanks,
Adam Mitz
Principal Software Engineer
Object Computing, Inc.
|