On 2009-03-10 20:07-0700 Alan W. Irwin wrote:

> To finish up this effort, I plan to rename get-drv-info as test-drv-info and
> make a series of tests comparing its output with the *.rc files that are
> configured by CMake.

DONE (revision 9725).  The TEST_DYNDRIVERS option is ON by default and is
always run.  It sets up a custom target test_dyndrivers which compares the
*.rc output of test-drv-info with the *.rc file created by the CMake
configuration logic to be sure the dynamic device has been built correctly.

So from now on if there is any *.rc.in file missing from drivers, you should
get a test failure.  Subsequently (assuming you have enabled all devices
for that particular device driver) all you have to do is copy the *.rc file
from drivers/test_dyndrivers_dir back to drivers/*.rc.in, and commit the
result.  Then touch cmake/modules/drivers-finish.cmake (or probably any
other CMake file) to convince cmake to re-run to generate the correct
*.rc file.  All should be well from then on.

I have just exercised this method with the Tk-related *.rc.in files which
were missing, and it works as described.

>
> Andrew, I leave it to you to follow up by simplifying the cross-build logic
> now that the *.rc files are configured rather than generated by an executable
> that must be built and run.

I have done this as well since it turned out to be so easy. I stripped all
the old cross-build logic out and created the above target only for the case
of TEST_DYNDRIVERS AND NOT CMAKE_CROSSCOMPILING.

(I did a similar thing for test_nistcd as well and also changed to always
running that test.)

Unless anybody else has problems with the *.rc files that cannot be corrected
as indicated above, I think this mini-project has been completed.  (And
similarly with the libnistcd mini-project.)

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Plplot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to