From: Hoehle, Joerg-C. <Joe...@t-...> - 2006-02-01 15:51:36
|
Hi, am I the only user with a MS-VC6 installation & interest in CLISP? I'd like to know, because it may very well happen that MS-VC support = gets rapidly dropped, visible in the unability to build the FFI (esp. = ffcall) with MS-VC and afterwards possibly nobody caring for MS-VC = patches in the main trunk of CLISP... That's pure theory. I'm not the maintainer. Reasons: o Since MS-VC7, the change in the MS license prohibits redistribution = of files needed to comply with GPL, I've heard (from what I understood, = the startup code/dll is at cause). Cf. clisp/win32msvc/INSTALL MS-VC6 is not affected. The copyright was different. The library is = different. Who has MS-VC6? Who has MS-VC7 and uses it to buid a personal, non redistributable = clisp, and an interest in continued ability to do so? o All GNU efforts on MS-Windows head at -mingw, gcc infrastructure etc. = That's what ffcall supports. GNU is where ffcall feels at home :) I'm no lawyer, and all the above is my paraphrasing. Why am I asking anyway? I'm going to make changes to the FFI to = restore/install support for LONG LONG types. MS-VC has __int64 instead = of long long. ffcall does not support that, and I'm not going to add = that myself. Independently, the FFI needs some changes in that area = and I'd like to know whether to invest time to find out how to still = make things work with MS-VC, or drop it RSN (which would cost me *much = less time* -- in fact, code is there on HD, but lacking smoe testing). Regards, J=F6rg H=F6hle. |