>> I could not get your current wrappers working under my Cygwin environment.
Me either, since I went to Cygwin v.1. There are problems with it; look at their mail archive under the threads "Problems with sed, make and NT4 in general", "Post B20 Cygwin CRLF behavior" and, for that matter, "sin6_addr undefined", though that one was easy to fix. >> Have you looked into ImageMagick 5.2.0 configure code? It does a very nice >> job of creating MSVC project files, without going through the pain of >> hacking wrappers. The source code for "configure.exe" in Image Magick 5.2 >> has ImageMagick sources directories hard coded. It can be, with a little >> efforts, tweaked to create MSVC project files for OpenDX too. I haven't looked at that, no, but I'm going to get the wrappers working if it kills me. Its not the wrappers, its aclocal, autoheader, automake and autoconf on Cygwin. Perl. >> ActiveDX would be a great help for Windows users. If I understand correctly, >> users will still need MOTIF based UI (DXUI etc)? Thats right, to create apps. But not to *deliver* apps. >> One of the other thing I am very interested is in BXDX for Linux from you. >> I might help DX community with some add-on package for DX using BX? On the priority queue, but down a bit. Their latest version is pretty screwed up; they don't support the old method of adding widgets by compiling them in and the run-time load approach requires hacking wrl(?) files by hand, because the GUI tool has major bugs, including deleting files, and, besides, I never got it to work. >> BTW: I have one more question beside BXDX. What is best format for a > loadable module on Windows. Should they be compiled as *.exe or *.dll? I don't know; haven't tried it. Greg
