From: Geoff H. <ghu...@ws...> - 2004-07-29 15:29:43
|
> I've done some work on the new conversion framework. Could I ask > for some further help to try it, particularly on non-Windows systems? Well, I guess that's where I come in, since no one else has stepped forward. :-) > output the file remains well-formed. The multiple file feature > currently > works in Windows but a little extra work is required for other systems > because it needs platform specific code. No, that's not needed under UNIX. The shell should simply pass a pile of arguments to the command-line tool. So we don't have to do any expansion ourselves -- it's handled for us for the most part. > wildcard searching and shared library handling which I should be > appropriate: dlhandler_unix.cpp. But since I don't have I'll take a look at the shared library bits -- though much of this can be handled on UNIX systems through the libtool code. > The different (and very religious) culture in unix makes it difficult > for me > to carry over the design. I'm really not sure what you mean by "very religious" UNIX culture. But I digress. The key thing I'd like is a better idea of which exact files are new and what your general directory layout is. Since the CVS tree has progressed since your code, differences exist in many of the files -- so it would help me a great deal if I knew which files you modified and had a slightly better roadmap of how your directory/build structure works. There are quite a few files which you haven't mentioned... Basically, I'm trying to avoid duplicated effort. I'm happy to adapt UNIX build support -- but I'd rather not obliterate your Windows builds if/when we rearrange directories, etc. Thanks, -Geoff |