>
> |
Building our Software
Here are some ideas I have about building the C++ software tree:
Nightly builds
Check out the Nightly Builds page. -- JamesGallagher - 09 Apr 2004
GNU autotools
Start using automake and libtool.
Issue: netCDF does not support the latest autotools; when will this change? (Fixed, see following comment.)
The code now uses a limited set of the Unidata macros. The configure script now can be built using the latest autoconf. -- JamesGallagher - 09 Apr 2004
Issue: we should start with src/dap, but that's probably the hardest part to do. We may need to move the Perl code in etc into src/dap. That's OK but the Perl code is fragile, so this could be very time consuming. The lack of tests for the Perl code means that success will have to be measured by hand...
-- JamesGallagher - 15 Sep 2003
Directory reorganization
As part of this effort, break apart the various directories so that each product on the new web pages (http://www.opendap.org/) has its own CVS module.
- DAP: becomes one unit and contains libdap++, client toolkit and server toolkit. The server TK contains asciival, www_int and usage plus all the Perl code. Look at re-writing the Perl code now versus waiting and using the Java servlet code later (depends on which proposal(s) get funded and how much time will elapse before work starts).
- Server modules: One product/module or several?
- Each client should have its own module.
- Separate nc library from server!
-- JamesGallagher - 10 May 2004
|