On 05/11/14 09:23, Daniel Kolesa wrote: > 2014-11-05 8:30 GMT+00:00 Tom Hacohen <[email protected]>: > >> On 04/11/14 23:59, Daniel Kolesa wrote: >>> 2014-11-04 18:44 GMT+00:00 Adrien Nader <[email protected]>: >>> >>>> Hi, >>>> >>>> On Tue, Nov 04, 2014, Daniel Kolesa wrote: >>>>> 2014-11-04 14:17 GMT+00:00 Tom Hacohen <[email protected]>: >>>>> >>>>>> That's why autofoo has a variable for lib extension. Use it... >>>>>> >>>>> >>>>> I was thinking about doing that, but decided it was counter-intuitive. >>>> It'd >>>>> actually be more code to use that variable as well as make editing >> things >>>>> more painful (as I'd have to generate util.lua, which would have a need >>>> for >>>>> util.lua.in, which editors wouldn't recognize as lua... I'm not even >>>>> talking about that it's not only an extension thing, Windows uses >> foo.dll >>>>> pattern while other OSes typically use libfoo.ext). We don't currently >>>>> support any OSes that don't follow this pattern - and if we ever do, >>>> it'll >>>>> be very easy to detect and port, as that code path is triggered when >> you >>>>> build the EFL - as such, I'd opt for keeping the current code as it is, >>>> and >>>>> only use the variable if ever necessary (which I don't think will >>>> happen). >>>> >>>> Everything built through libtool, no matter if for Windows or not, will >>>> use the libfoo-X.bar pattern. In my builds for Windows, everything uses >>>> that except SDL and, of course, Qt. >>>> >>> >>> In that case, I will have to special-case Windows slightly more... >> >> You mean a little less? >> > > Not really. As the loader is a generic library loader, I need to support > both libfoo.dll and foo.dll pattern. On other platforms, only libfoo.ext. > The default luajit ffi.load doesn't support libfoo.dll (it probably > shouldn't, as default Windows LoadLibrary API doesn't) but not supporting > it would mean that we need to specialize all EFL lib loads in lua apps for > windows... which is not what should be happening.
Oh, that is right. Horrible. -- Tom. ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
