Jonathan, > That's good news! > > What are your plans for the library under Windows? We have had partial > success rebuilding it using MinGW to supply the missing headers - this > produces a native dll which is relatively easy to invoke from .NET code > through the PInvoke mechanism (although unfortunately the more complex > functions are not working). I'm assuming the library will remain in C, > with converted header dependencies, rather than a full conversion to .NET. Correct. The library will remain in C. The netCDF-4 package has been successfully ported to Windows, so the same should be possible for UDUNITS. > Conversion to a platform-independent build chain sounds like a good idea. > Once that is complete, do you have any idea of the amount of effort that > will be required for the rest of the port? Having never done this, I have no idea how long it will take. Are you willing to contribute? > All the best, > Jonathan Ayling Regards, Steve Emmerson Ticket Details =================== Ticket ID: SEA-349902 Department: Support UDUNITS Priority: Normal 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.