GNOME Bugzilla – Bug 638322
[PATCH] use libtool for portability
Last modified: 2010-12-31 05:19:03 UTC
Created attachment 177235 [details] [review] libtool patch Using libtool is essential for portability to non-Linux systems. Patch for git master attached.
I'm not interested in using libtool. If you'd like to help me get dconf working on cygwin, please tell me what I have to do (other than use libtool).
I just remembered that I'm not interested in making dconf work on Windows at all, sorry. It does many things that simply will not work on Windows. There is a GSettings backend for the Windows registry for this reason.
1) this patch is necessary not only for Cygwin, but for most other non-Linux platforms (e.g. Darwin and most Unices, particularly HP-UX). Using libtool is the only way to support all those platforms with autotools. 2) Cygwin != Windows. Cygwin is a fully capable *NIX/X11 platform in its own right, and therefore dconf already works on Cygwin (I'm shipping 0.5.1 as part of GNOME 2.32).
dconf will not work with the Windows kernel. Cygwin is not capable of supporting even a very simple _essential_ requirement of dconf: the ability to rename over a file that is opened by another process. I understand that it may be desirable to run dconf on (real) non-ELF UNIX systems. I welcome patches for those, and I actually hope to see them. I do not agree with your assertion that libtool is "the only way". Please do not reopen this bug again.
(In reply to comment #4) > dconf will not work with the Windows kernel. Cygwin is not capable of > supporting even a very simple _essential_ requirement of dconf: the ability to > rename over a file that is opened by another process. This is no longer the case; since Cygwin 1.7, in-use files can be removed or replaced. > I understand that it may be desirable to run dconf on (real) non-ELF UNIX > systems. I welcome patches for those, and I actually hope to see them. I do > not agree with your assertion that libtool is "the only way". It is, so long as you are using autotools.