On Wed, Mar 04, 2009 at 07:37:53PM +0000, Andrew Ross wrote: > On Wed, Mar 04, 2009 at 09:18:36AM -0800, Alan Irwin wrote: > > On 2009-03-04 10:58-0000 Andrew Ross wrote: > > > >> Thinking about it, get-drv-info is only extracting symbols for the > >> installed > >> drivers which are in the source code anyway. There is no reason we couldn't > >> have some alternative way of doing this using cmake or some scripting which > >> would not rely on compiling an executable. This would be more portable for > >> cross-compiling. > >> > >> I think the reason it might have worked in my case (I haven't checked) is > >> that both platforms were using elf format object code. No guarantees in > >> general though. > > > > Overnight, I have had similar thoughts. I agree with your previous post the > > ssh approach would not be a good general approach so let's forget it. Also, > > we should note that the current get-drv-info has two tasks that it does; (1) > > it checks that dynamic loading works for the plug-in, and (2) it generates > > the <driver>.rc file. > > > > Instead of this approach, I think we should simply store those <driver>.rc > > files in the drivers subdirectory of the source tree and let CMake install > > them or not depending on what drivers are configured. We could then rename > > get-drv-info to test-drv-info. Then test-drv-info would only be run for > > normal builds (and not for cross builds) and the tests that it would do > > would be (1) and (2) checking that the existing <driver>.rc file is correct. > > I like this approach. Going further down this route, we could > also commit the generated header files to svn. The tools to build > them could be kept for making updates, as we do with the Hershey > fonts for example. This would eliminate build time executables > altogether which is probably a good thing.
The only complication of this approach is what happens for drivers which support multiple devices (e.g. cairo) which can be independently turned on or off. The .rc file will change depending on options. The simple "commit the file" approach won't be adequate for this. Andrew ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
