Philippe Gerum wrote: > ... > Good idea. Just implemented as described, now in the CVS. Thanks for the > hint. Additional testing welcome. > > PS: *.mod files contents refer to the build directory, so I guess that > such information would not be useful for setups that only provide the > installed binaries (and not the initial build dir). But still, I have > nonetheless exported the symbols to $exec_prefix/symbols as proposed. >
That's good news. I started playing a bit with it and have two remarks so far: 1. As it seems that we will no longer be able to build *modules* against RTAI just by using the files from the installation directory, I see no need anymore to actually install the symbol files. Creating a link, just like "build", for "symbols" should be ok. 2. Should external projects assume that the symbol dir is always "symbols", or should rtai-config be extended to return it? I'm in no favour for any of the options, I just would like to know which one to implement. Jan
signature.asc
Description: OpenPGP digital signature
