From: Mart K. <ma...@ke...> - 2008-11-28 07:54:15
|
Hi Jean-Philippe (and others), Op Thursday 27 November 2008 21:58:27 schreef Annick et Jean-Philippe: > Hi, Mart, and all. > > >> 5. Support for 3rd party robots... > > > > I have the following idea about this. Lets say I want to distribute a > > robot. Then I make the usual files (including CMakeLists.txt) and > > distribute a special FindTORCSNG.cmake file. That file is included in > > CMakeLists.txt or copied into CMakeLists.txt (in that case, it isn't > > distributed seperately). > > May be a separate distribution would be clearer to my mind : people would > copy the whole file in their robot source tree, with no modification needed > if it's well designed, and simply include it in their CMakeLists.txt. They can choose for themself. They can either copy the contents to the CMakeLists.txt, or distribute another file and include it. CMake does not see the difference anyway. > > FindTORCSNG.cmake search for the torcs-ng.cmake which is installed at the > > Torcs-ng datadir during torcs-ng installation. That file contains all the > > content of macros.cmake (such that every change in macros.cmake also > > applies to torcs-ng.cmake) with some variable settings (such as the place > > where the torcs-ng bin-dir, torcs include-dir and torcs-ng datadir is > > located. It also sets a variable to differ between something compiled > > inside the source tree (with macros.cmake) and outside the source tree > > (with torcs-ng.cmake). > > And what about : > - having torcs-ng.cmake simply include macros.cmake > (also copied at install time), and overwrite some default setting > of macros.cmake ? macros.cmake is a very bad name, centainly if its end up in /usr/share/cmake. Also, copiing the content isn't hard, and will have the same result. > - install these 2 files in "lib/torcs-ng" (I would find it a little better > that in "share/games/torcs-ng/data", as their are more related to the > code than to the data) It is definitly not a library. In /usr/lib, there usually are only libraries. All the cmake-files CMake distribute also goes to /usr/share (/usr/share/cmake/Modules, to be more exact). Torcs-ng does have a somewhat strange default share-path, but that doesn't change the situation. > - of course (you didn't say it, but ...) install the headers in "include" No, but I did write the code for it:) Maybe include/torcs-ng is better because some names can be quite general and we don't want end up overwriting some important system header file. > Mart, I think you've nearly already got it all ! > > A very good way to simplify robot development ! Not only robot development is affected. It can also be used to install cars and tracks into the right place. > Regards, > > Jean-Philippe. Regards, Mart |