Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://www.mrao.cam.ac.uk/~bn204/alma/sweng/ccmtoolsintro.html
Дата изменения: Mon Apr 4 13:47:51 2016 Дата индексирования: Sun Apr 10 09:51:54 2016 Кодировка: ISO8859-5 Поисковые слова: р с п п п п п п п п п п п п п п п п п |
The auxiliary xml file is searched for in the current directory!
Successfully call, with casaimager.xml in same directory as ccmtools:
CCMTOOLS_HOME=/home/bnikolic/d/p/cs /home/bnikolic/d/p/cs/bin/ccmtools -Xms1024M -Xmx1024M c++local c++python --overwrite -Ixmlcasa/i\
dl --coda=xmlcasa/xml/conversions.xml -o build/test/xmlcasa/gcode build/test/xmlcasa/gcode/casaimager.idl
Note: tool names have to have “casa” prepended to them, otherwise the aux xml file is nto found.
Note: some idl files include other idls (notable casameasurs) so the aux xml file has to be put into the root directory too!
This file contains the homes (this is a CCMTools-specific concept as far as I can make it) for the tools which are passed to ccmtools command line. Therefore, for all of the tools to be included in this file, they need to be all passed to the ccmtools at the same time on the command line.
Probably it is not possible to absolutely reliably regenerate the
bindings for just one of the files. The old casa build system I think
does try to do this by moving the casac_python files away before
calling ccmtools
and then reinstating them.
Since CCMTools generates many files from each invocation, it is not trivial to tell the build system what files will be generated by the call. One solution is to capture the output to the console of an invocation and parse this to determine what targets are generated. I take both files that are described as writing and Skipping as being targets.
Warning
I haven’t figured out yet why some files are indicated as skipping by CCMTools
Files generated by CCMTools with names ending in “_cmpt.cc” are not used by the build. Instead, equivalently named static files checked into the repository are compiled and linked into the library instead. The reason is presumably that some hand-modification are necessary for these files.
Building CCMTools as required by CASA
A prototype build system for CASA using SCons
The search results are restrict to these pages only