Generate C++ code from your IDL file with the following command (replace the architecture namei86Linux3gcc4.8.2 with the name of your own architecture):

> rtiddsgen -ppDisable              \
	-language C++                \
	-example i86Linux3gcc4.8.2   \
	-replace                     \
	HelloWorld.idl

The generated code publishes identical DDS data samples and subscribes to them, printing the received data to the terminal. Edit the code to modify each DDS data sample before it's published: Open HelloWorld_publisher.cxx. In the code for publisher_main(), locate the "for" loop and add the bold line seen below, which puts "Hello World!" and a consecutive number in each DDS sample that is sent.2If you are using Visual Studio, consider using sprintf_s instead of sprintf: sprintf_s(instance->msg, 128, "Hello World! (%d)", count);

for (count=0; (sample_count == 0) || (count < sample_count); ++count) { 
	printf("Writing HelloWorld, count %d\n", count); 
	/* Modify the data to be sent here */
          	sprintf(instance->message, "Hello World! (%d)", count);

	retcode = HelloWorld_writer->write(*instance, instance_handle);
	if (retcode != DDS_RETCODE_OK) { 
		printf("write error %d\n", retcode); 
	}
	NDDSUtility::sleep(send_period);
}

Generate C++03 or C++11 code from your IDL file with the following command (replace the architecture name i86Linux3gcc4.8.2 with the name of your own architecture):

> rtiddsgen -ppDisable               \
	-language C++03              \
	-example i86Linux3gcc4.8.2   \
	-replace                     \
	HelloWorld.idl

Or:

> rtiddsgen -ppDisable               \
	-language C++11              \
	-example i86Linux3gcc4.8.2   \
	-replace                     \
	HelloWorld.idl

The only differences between using C++03 or C++11 is that the latter creates a different subscriber example and adds a flag to enable C++11 in supported compilers that require explicit activation. This also activates C++11 features in the DDS API headers. See the API Reference HTML documentation (Modules > Conventions) for more information.

The generated code publishes identical DDS data samples and subscribes to them, printing the received data to the terminal. Edit the code to modify each DDS data sample before it's published: Open HelloWorld_publisher.cxx. In the code for publisher_main(), locate the "for" loop and add the bold line seen below, which puts "Hello World!" and a consecutive number in each DDS sample that is sent.3If you are using Visual Studio, consider using sprintf_s instead of sprintf: sprintf_s(instance->msg, 128, "Hello World! (%d)", count);

for (int count = 0; count < sample_count || sample_count == 0; count++) {
    // Modify the data to be written here
    sample.message("Hello World! (" + std::to_string(count) + ")");
    std::cout << "Writing MyOtherType, count " << count << "\n";
    writer.write(sample);
    rti::util::sleep(dds::core::Duration(4));
}

Generate Java code from your IDL file with the following command4The argument -ppDisable tells the code generator not to attempt to invoke the C preprocessor (usually cpp on UNIX systems and cl on Windows systems) on the IDL file prior to generating code. In this case, the IDL file contains no preprocessor directives, so no preprocessing is necessary. However, if the preprocessor executable is already on your system path (on Windows systems, running the Visual Studio script vcvars32.bat will do this for you) you can omit this argument. (replace the architecture name i86Linux3gcc4.8.2 with the name of your own architecture):

> rtiddsgen -ppDisable                  \
	-language Java                  \
	-example  i86Linux3gcc4.8.2 \
	-replace                        \
	HelloWorld.idl

The generated code publishes identical DDS data samples and subscribes to them, printing the received data to the terminal. Edit the code to modify each DDS data sample before it's published: Open HelloWorldPublisher.java. In the code for publisherMain(), locate the "for" loop and add the bold line seen below, which puts "Hello World!" and a consecutive number in each DDS sample that is sent.

for 
(int count = 0; sampleCount == 0) || (count < sampleCount); ++count) {
	System.out.println("Writing HelloWorld, count " + count); 
	/* Modify the instance to be written here */
	instance.msg = "Hello World! (" + count + ")";
	/* Write data */ 
	writer.write(instance, InstanceHandle_t.HANDLE_NIL);
	try { 
		Thread.sleep(sendPeriodMillis); 
	} catch (InterruptedException ix) { 
		System.err.println("INTERRUPTED");
		break;
	}
}

Generate Ada code from your IDL file with the following command (replace the architecture name x64Linux2.6gcc4.4.5 with the name of your own architecture):

rtiddsgen -ppDisable -language Ada \
   -example x64Linux2.6gcc4.4.5 -replace HelloWorld.idl

Notes:

• Ada support requires a separate add-on product, Ada Language Support.
• The generated publisher and subscriber source files are under the samples directory. There are two generated project files: one at the top level and one in the samples directory. The project file in the samples directory, samples/helloworld-samples.gpr, should be the one that you will use to compile the example.
• The generated Ada project files need two directories to compile a project: .obj and bin. If your Ada IDE does not automatically create these directories, you will need to create them outside the Ada IDE, in both the top-level directory and in samples directory.

With the NDDSHOME environment variable set, start Visual Studio and open the rtiddsgen-generated solution file (.sln). Select the Release configuration in the Build toolbar in Visual Studio5The Connext DDS .NET language binding is currently supported for C# and C++/CLI.. From the Build menu, select Build Solution. This will build two projects: <IDL name>_publisher and <IDL name>_subscriber.

Ada support requires a separate add-on product, Ada Language Support.

Use the generated Ada project file to compile an example on any system.

Note: The generated project file assumes the correct version of the compiler is already on your path, NDDSHOME is set, and $NDDSHOME/lib/gnat is in your ADA_PROJECT_PATH.

gmake -f makefile_HelloWorld_<architecture>

After compiling the Ada example, you will find the application executables in the directory, samples/bin. The build command in the generated makefile uses the static release versions of the Connext DDS libraries. To select dynamic or debug versions of the libraries, change the Ada compiler variables RTIDDS_LIBRARY_TYPE and RTIDDS_BUILD in the build command in the makefile to build with the desired version of the libraries. For example, if the application must be compiled with the relocatable debug version of the libraries, compile with the following command:

gprbuild -p -P samples/helloworld-samples.gpr -XOS=Linux \
  -XRTIDDS_LIBRARY_TYPE=relocatable -XRTIDDS_BUILD=debug -XARCH=${ARCH}

First, start the subscriber application, HelloWorld_subscriber:Use the generated makefile to compile a C or C++ example on a UNIX-based system or a Java example on any system. Note: the generated makefile assumes the correct version of the compiler is already on your path and that NDDSHOME is set.

gmake -f makefile_HelloWorld_<architecture>

After compiling the C or C++ example, you will find the application executables in a directory objs/<architecture>.

The generated makefile includes the static release versions of the Connext DDS libraries. To select dynamic or debug versions of the libraries, edit the makefile to change the library suffixes. Generally, Connext DDS uses the following convention for library suffixes: "z" for static release, "zd" for static debug, none for dynamic release, and "d" for dynamic debug. For a complete list of the required libraries for each configuration, see the RTI Connext DDS Core Libraries Platform Notes.

For example, to change a C++ makefile from using static release to dynamic release libraries, change this directive:

LIBS = -L$(NDDSHOME)/lib/<architecture> \ 
	-lnddscppz -lnddscz -lnddscorez $(syslibs_<architecture>) 

to:

LIBS = -L$(NDDSHOME)/lib/<architecture> \ 
	-lnddscpp -lnddsc -lnddscore $(syslibs_<architecture>)

First, start the subscriber application, HelloWorld_subscriber:

./objs/<architecture>/HelloWorld_subscriber

In this command window, you should see that the subscriber wakes up every four seconds to print a message:

HelloWorld subscriber sleeping for 4 sec... 
HelloWorld subscriber sleeping for 4 sec... 
HelloWorld subscriber sleeping for 4 sec... 

Next, open another command prompt window and start the publisher application, HelloWorld_publisher. For example:

./objs/<architecture>/HelloWorld_publisher

In this second (publishing) command window, you should see:
Writing HelloWorld, count 0 Writing HelloWorld, count 1 Writing HelloWorld, count 2

Look back in the first (subscribing) command window. You should see that the subscriber is now receiving messages from the publisher:

HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {0}“ 
HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {1}“ 
HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {2}“

You can run the generated applications using the generated makefile. On most platforms, the generated makefile assumes the correct version of java is already on your path and that the NDDSHOME environment variable is set6 One exception on LynxOS systems; see Getting Started on Embedded UNIX-like Systems in the Getting Started Guide, Addendum for Embedded Platforms..

First, run the subscriber:

gmake -f makefile_HelloWorld_<architecture> HelloWorldSubscriber

In this command window, you should see that the subscriber wakes up every four seconds to print a message:

HelloWorld subscriber sleeping for 4 sec... 
HelloWorld subscriber sleeping for 4 sec... 
HelloWorld subscriber sleeping for 4 sec...

Next, run the publisher:

gmake -f makefile_HelloWorld_<architecture> HelloWorldPublisher

In this second (publishing) command window, you should see:

Writing HelloWorld, count 0
Writing HelloWorld, count 1
Writing HelloWorld, count 2

Look back in the first (subscribing) command window. You should see that the subscriber is now receiving messages from the publisher:

HelloWorld subscriber sleeping for 4 sec...
	msg: “Hello World! {0}“
HelloWorld subscriber sleeping for 4 sec...
	msg: “Hello World! {1}“
HelloWorld subscriber sleeping for 4 sec...
	msg: “Hello World! {2}“

Ada support requires a separate add-on product, Ada Language Support.

First, start the subscriber application, helloworld_idl_file-helloworld_subscriber:

./samples/bin/helloworld_idl_file-helloworld_subscriber

In this command window, you should see that the subscriber wakes up every four seconds to print a message:

HelloWorld subscriber sleeping for 4.000000000 sec.
HelloWorld subscriber sleeping for 4.000000000 sec.
HelloWorld subscriber sleeping for 4.000000000 sec.

Next, open another command prompt window and start the publisher application, helloworld_idl_file-helloworld_publisher. For example:

./samples/bin/helloworld_idl_file-helloworld_publisher

In this second (publishing) command window, you should see:

Writing HelloWorld, count 0
Writing HelloWorld, count 1
Writing HelloWorld, count 2

Look back in the first (subscribing) command window. You should see that the subscriber is now receiving messages from the publisher:

HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {0}“ 
HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {1}“ 
HelloWorld subscriber sleeping for 4 sec... 
	msg: “Hello World! {2}“