This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi, re: Can you verify that the ~mcidas/lib directory now has a copy of libjasper.a in it? > Indeed it does. Excellent! That was one of the other things that was not being done when the Jasper library was being put into the build-jasper/lib subdirectory. The changes I made were to basically do the copy from both directories, and ignore the case where libjasper.a was in the "other" subdirectory. It must be the case that SSEC's build environment for Ubuntu 20.04 under Windows WSL is different enough that they did not run into the "Jasper problem". It is not surprising that the setup in Unidata McIDAS needs to be tweaked since the set of OSes that Unidata McIDAS has supported has always been a superset of what SSEC supports, and this has always resulted in the need for slightly different procedures... sigh! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: SDI-707505 Department: Support McIDAS Priority: High Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.