Fix install dir of CycloneDDSConfig.cmake (#321)
Installing Cyclone DDS for multiple architectures with the same installation prefix gave problems because the CMake configuration files ended up overwriting each other. This brings it in line with the recommended locations. Thanks to @hansfn. Signed-off-by: Erik Boasson <eb@ilities.com>
This commit is contained in:
		
							parent
							
								
									3da21315f2
								
							
						
					
					
						commit
						e43bdb73c7
					
				
					 9 changed files with 34 additions and 38 deletions
				
			
		| 
						 | 
				
			
			@ -206,13 +206,12 @@ look in the default locations for the code:`CycloneDDS` package.
 | 
			
		|||
 | 
			
		||||
.. _`IdlcGenerate`:
 | 
			
		||||
 | 
			
		||||
The :code:`CycloneDDS` package provides the :code:`ddsc` library
 | 
			
		||||
that contains the DDS API that the application needs. But apart
 | 
			
		||||
from that, it also contains helper functionality
 | 
			
		||||
(:code:`idlc_generate`) to generate library targets from IDL
 | 
			
		||||
files. These library targets can be easily used when compiling
 | 
			
		||||
an application that depends on a data type described
 | 
			
		||||
in an IDL file.
 | 
			
		||||
The :code:`CycloneDDS` package provides the :code:`ddsc` library that
 | 
			
		||||
contains the DDS API that the application needs. It also provides a
 | 
			
		||||
component "idlc" that provides helper functionality for generating
 | 
			
		||||
library targets from IDL files (:code:`idlc_generate`). These library
 | 
			
		||||
targets can be easily used when compiling an application that depends on
 | 
			
		||||
a data type described in an IDL file.
 | 
			
		||||
 | 
			
		||||
Two applications will be created, :code:`HelloworldPublisher`
 | 
			
		||||
and :code:`HelloworldSubscriber`. Both consist only out of one
 | 
			
		||||
| 
						 | 
				
			
			@ -241,7 +240,7 @@ Here, we can let CMake configure the build environment for
 | 
			
		|||
us by typing:
 | 
			
		||||
::
 | 
			
		||||
 | 
			
		||||
    cmake ../
 | 
			
		||||
    cmake ..
 | 
			
		||||
 | 
			
		||||
.. note::
 | 
			
		||||
    CMake does a pretty good job at guessing which generator to use, but some
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue