2010年5月4日星期二
emacs: window下使用sdcv
1.先编译sdcv
由于sdcv需要glib2和其它一些UNIX下常用函数，在mingw下编译比较麻烦，就在Cygwin下编译了。
需要注意的是Cygwin下编译时，需要将src/Makefile.in中
sdcv_LDADD = @SDCV_LIBS@ @LIBINTL@ @LIBREADLINE@ lib/libstardict.a
改为
sdcv_LDADD = lib/libstardict.a @SDCV_LIBS@ @LIBINTL@ @LIBREADLINE@
即将静态库放到前面，否则链接时会报告一大堆函数找不到，这是移植程序到Cygwin常碰到的一个问题（另一个问题是Windows下动态库不能引用任何编译时找不到的函数/变量，而Linux下可以支持运行期解析，即可以直接在插件中使用主程序的函数/变量或者早先加载的其它动态库里的函数/变量）
2.开始试的是emacswiki.org上的 sdcv.el, 但它死活不能正常工作， *FIXME*原因似乎是: 它有指定词典的功能，但这个词典名通过命令行传递时，会出现编码不被sdcv.exe识别的问题(不是这个原因?)
<2010-05-05 >: 调试了一下，发现是sdcv-search-detail函数的问题，导致了两次调用shell（第二次还传了个奇怪的参数进去)注释掉361行即可。但没看懂代码的意图，还不明白具体错在什么地方。
3.然后找到了 http://code.google.com/p/sdcv-mode 上的sdcv-mode.el，这个库比较简单，安装上之后直接load-library 'sdcv-mode, 然后就可以调sdcv-search命令了
注: Cygwin会检测cygwin1.dll重复的问题，如果将X:/cygwin/bin加入PATH后就可能会因这个问题而拒绝工作。这种情况下改用一个sdcv.bat来包装一下sdcv.exe，就没有这个现象了
2008年11月16日星期日
Weekly Twitter 2008 #46
| |
| |
| |
| |
|
2007年1月17日星期三
cygwin port of xfce4 and claws-mail (site moved)
我提供的一些cygwin包移动到了 http://bamanzi.inlsd.org/cygwin.
只保留了xfce4和claws-mail. 其它的没有精力维护了 :-(
而且xfce4也只保留了4.2.3和4.4rc2，更老的版本删除了。
claws-mail倒是更新到了最新版本2.7.1.
(原来的空间http://www.amazepc.com/bamanzi 是网友古公友情提供的，很感谢他提供了这么久。
以前的一些有价值的东西，我会陆续放到新的站点。)
只保留了xfce4和claws-mail. 其它的没有精力维护了 :-(
而且xfce4也只保留了4.2.3和4.4rc2，更老的版本删除了。
claws-mail倒是更新到了最新版本2.7.1.
(原来的空间http://www.amazepc.com/bamanzi 是网友古公友情提供的，很感谢他提供了这么久。
以前的一些有价值的东西，我会陆续放到新的站点。)
2006年11月17日星期五
写了个小脚本下载cygwin ports
为了给朋友提供一份cygwin,我从下面这个地方下载了一份ISO(自己用cygwin的安装工具下载实在是很受不了的):
http://inst.eecs.berkeley.edu/~instcd/iso/然后就想着再把cygwin ports也下载一份，但其服务器慢得要命，而且常常断链，镜像网站也没有。最后只好祭出wget大法，用了个小脚本来搞。
(外一则)今天Nick Hodges的blog上说到:
有人在留言中说:You know what I hate? I hate it when Windows tells me that it has installed new updates, and then it keeps insisting I have to reboot. If I say reboot later, it gives me like a five minute grace period and 'reminds' me again. I should be able to reboot when I want to reboot, not when Windows insists that I reboot. Very irritating.
What I hate - you leave a long download going overnigt, and you get up the next morning and your computer has been rebooted by Windows Update.
嘿，跟我在下载cygwin ports中碰到的问题一样: 开始Windows Update每隔5分钟问我一次要不要重启，烦死我了；后来配好了下载脚本，本来放心地去睡了，第二天早上一看，就下载了3%, 机器被Windows Update自作聪明地重启了 
。只是没想到这些高手也会被这个问题所困扰。
首先:
wget ftp://sunsite.dk/projects/cygwinports/setup.bz2
bunzip2 -dc setup.bz2 > setup.ini
然后就可以不断使用这个脚本了:
#!/bin/sh |
User Comments
关不掉windows update的重启提示 [
Reply] bamanzi | 17 十一月, 2006 21:40
在网上收了一阵，说是运行gpedit.msc，然后设置某个选项即可关掉。但我这里没有gpedit.msc，说是XP Home版本没有这个东西。唉!
anony | 21 十一月, 2006 15:51
我用的cygwin是这个版本:cygwin-cd-release-20060906.iso.全部安装,在下载好cygwin ports,全部安装.安装的时候看到cygwin自动把旧的gnome/xorg什么的卸载掉了,装好后,运行gnome/kde都不成功 (startgnome,startkde),老是提示: _X11TransOpen: transport open failed for local _X11TransOpen: transport open failed for tcp ,并且xterm都不能打开,can't open display 127.0.0.1:0,但是明明X是起来的,telnet能直接联上127.0.0.1:6000.是因为cygwin版本太低了么?
.还是不行,估计是cygwin ports的问题.唉2006年7月15日星期六
搞定xfce-4.4beta2的cygwin移植版本
有4.4beta1在前，这个版本(4.4beta2，即4.3.90.2)搞起来就容易多了，回头整理一下patch，看看有哪些可以提交给upstream.
前 段时间有两个网友问那些free software是不是直接在cygwin下编译一下就可以用了，我说也可以说是，也不是。虽然cygwin对POSIX的模拟和众多cygwin包的贡 献使得移植工作已经相当容易了，还是有些细节(比如fork啊，named pipe啊，文件命名啊，文件权限啊，动态库符号解析啊)方面折腾起来比较麻烦。
其中一位想干脆在mingw下编译一下GNOME桌面然后 跑起来，但目前似乎只有GNOME的一些核心库(即platform部分)已经一直过来了，而bindings似乎只有跟gtk+相关的一部分，至于 desktop部分似乎一直过来也没有意义, admin部分就更不用提了。
2006年2月26日星期日
Cygwin port of Sylpheed-Claws 2.0.0
Finally the cygwin port of sylpheed-claws-2.0.0 is out. And I made a brief page to give some info about which packages you need to download and how to install it.
Sylpheed -Claws年前就出2.0了，但一直没有什么时间来编译cygwin版本(其实刚出来也试图马上更新cygwin版本的，但前面某位针对mingw做了改进，但对于PLATFORM_WIN32和OS_WIN区分不清楚，导致我原来针对cygwin的补丁几乎不能用了)。
今天终于有半天时间，把它搞定了。这次是想一劳永逸，直接修改了configure.ac和Makefile.am，将补丁发给了Paul. 我是不想以后每次有新版本都在Makefile上折腾半天了——也早该这样了，只是原来对于autoconf和automake的了解太少，而且要提交补丁给上游(upstream)还得考虑不能干扰其他平台。
Sylpheed -Claws年前就出2.0了，但一直没有什么时间来编译cygwin版本(其实刚出来也试图马上更新cygwin版本的，但前面某位针对mingw做了改进，但对于PLATFORM_WIN32和OS_WIN区分不清楚，导致我原来针对cygwin的补丁几乎不能用了)。
今天终于有半天时间，把它搞定了。这次是想一劳永逸，直接修改了configure.ac和Makefile.am，将补丁发给了Paul. 我是不想以后每次有新版本都在Makefile上折腾半天了——也早该这样了，只是原来对于autoconf和automake的了解太少，而且要提交补丁给上游(upstream)还得考虑不能干扰其他平台。
2005年12月18日星期日
My Cygwin Repository Updated
Updated: xfce4-4.2.3.2(except for xffm and xfce-icon-themes)
Updated: sylpheed-claws-gtk2-1.9.100-1t (testing)
Updated: gtkpod-0.99.2 (and libgpod-0.3.0)
2005年11月18日星期五
Cygwin Ports
早在cygwin的主页上看见了Cygwin Ports的公告，说是提供了近700个包，还包括GNOME 2和xfce4！
但原来一直访问不畅，所以也没有特别注意。
昨天又试了一下，发现不仅有GNOME 2.10，而且pygtk2, python-gnome2以及很多应用程序(比如devhelp, gnochm, stardict, gaphor, sodipodi, bmp)都有。爽啊！
2005年10月11日星期二
My Cygwin Repository Updated
Updated: sylpheed-claws-gtk2-1.9.15
New: tilda-0.09.1
New: xfdiff-4.3.4
Now split into stable(1.9.15-1 this time) and testing(1.9.15-1t this time). At present, the testing version has gnomeprint support, some cygwin specific modifications and my undelete patch.
Note you need to update your libetpan to 0.39.
Note you need to update your libetpan to 0.39.
New: tilda-0.09.1
Tilda is a Linux terminal taking after the likeness of many classic terminals from first person shooter games, Quake, Doom and Half-Life to name a few, where the terminal has no border and is hidden from the desktop till a key or keys is hit.
New: xfdiff-4.3.4
xfdiff was a component of xffm, but now returns as an independant tool.
2005年8月31日星期三
porting xffm-4.3 to cygwin
在GnomeFiles上看见了xffm-4.3.3的出现，我对xfce4的印象还不错，尤其在Cygwin上没有其他桌面环境(DE)可以用的情况下，于是拉下来编译。
xffm4的名声似乎一直不太好，所以也是后来xfce4开发小组一直说要重点改进的。这个4.3是个测试版本，相对前一版本而言，增加了不少功能，比如新增了iconview和deskview(就是windows那样放在桌面的应用程序启动程序)，一个applicatios模块(支持标准的.desktop文件)。
我对xffm的功能齐全还是比较满意，这么点大的程序有书签、查找、垃圾筒、文件比较、fstab、recent各项功能。只是界面却越来越显得混乱，原来只有treeview模式还好一点，但现在4.3又添加了deskview、iconview并且将这二者改为缺省了，进来就觉得有些乱，而一个文件夹从iconview转到detailed view时居然还需要另外打开一个窗口。另外有些地方(比如Goto, Run的输入条)明显是rox的风格，但rox用起来明显简洁多了。
虽然xffm的代码结构经过大幅调整，在Cygwin编译它仍然是一个恶梦，因为xffm对于应用程序、静态库、动态库、插件根本没有一个明确的划分，按原来的编译方式得有大约12个库文件生成到/usr/lib下。我不得不大幅更改Makefile.am， 将libs下的所有库编译到一个libxffm.la的动态库中去，其他的再链接到这个库。附带的一个收获是增加了对automake的了解 :-)。(过两天整理一下放上来)
2005年8月15日星期一
PuttyCYG
Carlos Liu的blog上贴了一篇用 PuTTYcyg 替代 Windows 命令行窗口，这里做个书签。
这个小工具确实不错，比用rxvt 好的是可以即时修改一些设置，比如字体、颜色什么的，还可以全屏。
2005年7月22日星期五
My Cygwin Repository Updated
New:
- vim-gtk2-6.3.071
- dia-0.94 Dia is a gtk+ based diagram creation program (screenshots)
- leafpad-0.8.2
- notecase-0.9.3
- gtkpod-0.94.0
2005年6月11日星期六
Cygwin rxvt here
I added a context menu item 'Cygwin shell here' for Windows' Explorer.
--- e:/cygwin/rxvt-here.reg --- 8< ------
[HKEY_CLASSES_ROOT/Drive/shell/bashHere]
@="Shell: Cygwin shell here"
[HKEY_CLASSES_ROOT/Drive/shell/bashHere/command]
@="E://Cygwin//rxvt-here.bat /"%1/""
[HKEY_CLASSES_ROOT/Directory/shell/bash/Here]
@="Shell: Cygwin shell here"
[HKEY_CLASSES_ROOT/Directory/shell/bash/Here/command]
@="E://Cygwin//rxvt-here.bat /"%1/""
-------------------------------- >8 -------
(注: 上述斜线均应该为反斜线，这里的blog不支持反斜线，只好这样了)
--- e:/cygwin/rxvt-here.bat ---- 8< -----
@echo off
E:
chdir /cygwin/bin
echo.exe -n "cd " > cygwin/tmp/cygwin_here.rc
cygpath -u %1 >> cygwin/tmp/cygwin_here.rc
start rxvt -bg black -fg white -sr -sl 3000 -fn Courier-12 -geometry 100x400 -e /bin/bash -login
-------------------------------- >8 -------
(注: 上述斜线除最后的/bin/bash外均应该为反斜线，这里的blog不支持反斜线，只好这样了)
--- ~/.bash_profile ------- 8< -----
...[snip]
[ -r /tmp/cygwin_here.rc ] && . /tmp/cygwin_here.rc && rm -f /tmp/cygwin_here.rc
--------------------------- >8 -----------
--- e:/cygwin/rxvt-here.reg --- 8< ------
[HKEY_CLASSES_ROOT/Drive/shell/bashHere]
@="Shell: Cygwin shell here"
[HKEY_CLASSES_ROOT/Drive/shell/bashHere/command]
@="E://Cygwin//rxvt-here.bat /"%1/""
[HKEY_CLASSES_ROOT/Directory/shell/bash/Here]
@="Shell: Cygwin shell here"
[HKEY_CLASSES_ROOT/Directory/shell/bash/Here/command]
@="E://Cygwin//rxvt-here.bat /"%1/""
-------------------------------- >8 -------
(注: 上述斜线均应该为反斜线，这里的blog不支持反斜线，只好这样了)
--- e:/cygwin/rxvt-here.bat ---- 8< -----
@echo off
E:
chdir /cygwin/bin
echo.exe -n "cd " > cygwin/tmp/cygwin_here.rc
cygpath -u %1 >> cygwin/tmp/cygwin_here.rc
start rxvt -bg black -fg white -sr -sl 3000 -fn Courier-12 -geometry 100x400 -e /bin/bash -login
-------------------------------- >8 -------
(注: 上述斜线除最后的/bin/bash外均应该为反斜线，这里的blog不支持反斜线，只好这样了)
--- ~/.bash_profile ------- 8< -----
...[snip]
[ -r /tmp/cygwin_here.rc ] && . /tmp/cygwin_here.rc && rm -f /tmp/cygwin_here.rc
--------------------------- >8 -----------
2005年5月28日星期六
My Cygwin Repository近期更新
我的Cygwin Repository有些日子没有更新了（除了上个月应一些朋友的要求提供了xfce-4.2.1.1），总算更新了一把:
- sylpheed-claws更新到了1.0.4a(gtk1)和1.9.9(gtk2)
- 新提供了scite-1.62, 包括gtk1和gtk2版本
- 新提供了gtk-theme-switch-2.0.3, gtk-chtheme-0.3.1
- 新提供了bluefish-1.0
- 上月更新: gqview-2.1.0, gtkpod-0.88.2, leafpad-0.7.9
gtk1的东西还是基于cygnome的， 毕竟cygwin官方包里的gtk缺乏支撑包，而cygnome又比较稳定。(原来在release/目录下提供过一个用cygwin net release的gtk-1.2的包编译的sylpheed-claws，现在已经删除了。)近期如果有空的话，还打算针对cygnome做一次更新，主 要解决python-gnome-1.x的问题。
gtk2的东西倒是都基于cygwin提供的gtk2了。目前还在折腾的是notecase, 而rox, bmp, gwhere等上游也都有新版本等待更新(gaim是不打算维护了，反正它自己也有win32版本，倒是有可能继续搞搞openq的win32版本)。
2005年4月4日星期一
Cygwin port of sylpheed-claws-gtk2-1.9.6cvs1
Here come the cygwin port sylpheed-claws-gtk2-1.9.6cvs1.
Only source patch available. Due to bandwidth limit, I can't upload the binary to my repository
now (Due to this reason I haven't updated it for serveral months :-(.
Now I have a lot of pending packages: xfce-4.2.0, rox-2.2, etc).
This patch was based on the source package provided by debian (experimental) , for its convenience, as it was preprocessed with autoconf/automake.
Usage:
$ tar zxvf sylpheed-claws-gtk2_1.0.1cvs1_orig.tar.gz $ patch -p1 -b < sylpheed-claws-gtk2-1.0.1cvs1-1.diff $ ./sylpheed-claws-gtk2-1.0.1cvs1-1.sh mkdirs patch config make install package
And I also uploaded the source patch for gtk1 version of 1.0.1.
Only source patch available. Due to bandwidth limit, I can't upload the binary to my repository
now (Due to this reason I haven't updated it for serveral months :-(.
Now I have a lot of pending packages: xfce-4.2.0, rox-2.2, etc).
This patch was based on the source package provided by debian (experimental) , for its convenience, as it was preprocessed with autoconf/automake.
Usage:
$ tar zxvf sylpheed-claws-gtk2_1.0.1cvs1_orig.tar.gz $ patch -p1 -b < sylpheed-claws-gtk2-1.0.1cvs1-1.diff $ ./sylpheed-claws-gtk2-1.0.1cvs1-1.sh mkdirs patch config make install package
And I also uploaded the source patch for gtk1 version of 1.0.1.
2005年4月1日星期五
cygwin port of xffm-4.2 almost done
Today:
- Removed the stupid cygwin handling in fstab_module.c. Now you can also visit your DOS drives in the Fstab branch.
- Fixed the window title when goto a network share folder (in cygwin, //machine/service always works even without smb module)
- Now all fixes could be done via automake
- Now xffm seems to be much more stable
Some problems:
- When traversing on the main menu, gtk always complains "assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed"
- I can't bookmark a directory in network share folder (dnd.c? or is it also a problem in the upstream?)
About xffm itself:
- The usability is much better than 4.0
- Some UI parts are not instinctive. For example, the sidebars, I lost it by accident. But if I didn't check the manual, I couldn't know how to get it back.
Source patches are here(xffm-4.2.1-cygwin-patch.tar.gz).
Usage:
xffm-4.2.1-cygwin-automake.patch is for those who have automake installed.
$ tar zxf xffm-4.2.1.tar.gz # unpack source
$ cd xffm-4.2.1
$ patch -p1 -b <>
$ CFLAGS=-O2 ./configure --prefix=/opt/xfce4
$ /usr/autotool/devel/bin/automake-1.9
$ make
$ make install
xffm-4.2.1-cygwin.patch is for those who don't have automake.
$ tar zxf xffm-4.2.1.tar.gz # unpack source
$ cd xffm-4.2.1
$ patch -p1 -b <>
$ CFLAGS=-O2 ./configure --prefix=/opt/xfce4
$ make
$ make install
The -automake patch is smaller, which makes the patch maintainable.
Note:
If you want to build in a directory other than the source directory (e.g. xffm-4.2.1/.build, ) via "./configure --srcdir=/path/to/source/dir", remember to copy the faked src/libxffm.la to $(top_builddir)/src/.
- Removed the stupid cygwin handling in fstab_module.c. Now you can also visit your DOS drives in the Fstab branch.
- Fixed the window title when goto a network share folder (in cygwin, //machine/service always works even without smb module)
- Now all fixes could be done via automake
- Now xffm seems to be much more stable
Some problems:
- When traversing on the main menu, gtk always complains "assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed"
- I can't bookmark a directory in network share folder (dnd.c? or is it also a problem in the upstream?)
About xffm itself:
- The usability is much better than 4.0
- Some UI parts are not instinctive. For example, the sidebars, I lost it by accident. But if I didn't check the manual, I couldn't know how to get it back.
Source patches are here(xffm-4.2.1-cygwin-patch.tar.gz).
Usage:
xffm-4.2.1-cygwin-automake.patch is for those who have automake installed.
$ tar zxf xffm-4.2.1.tar.gz # unpack source
$ cd xffm-4.2.1
$ patch -p1 -b <>
$ CFLAGS=-O2 ./configure --prefix=/opt/xfce4
$ /usr/autotool/devel/bin/automake-1.9
$ make
$ make install
xffm-4.2.1-cygwin.patch is for those who don't have automake.
$ tar zxf xffm-4.2.1.tar.gz # unpack source
$ cd xffm-4.2.1
$ patch -p1 -b <>
$ CFLAGS=-O2 ./configure --prefix=/opt/xfce4
$ make
$ make install
The -automake patch is smaller, which makes the patch maintainable.
Note:
If you want to build in a directory other than the source directory (e.g. xffm-4.2.1/.build, ) via "./configure --srcdir=/path/to/source/dir", remember to copy the faked src/libxffm.la to $(top_builddir)/src/.
2005年3月31日星期四
新闻: Slackware删除GNOME
经过数月的争议后，Patrick终于还是决定将GNOME从Slackware中删除，原因是"GNOME takes a lot of time to package, so this move should allow more time to be spent on the rest of Slackware".
虽然Dropline GNOME等的存在也是一个诱因，虽然我喜欢GNOME界面的简洁，但GNOME安装之麻烦似乎也是不争的事实:
我当初搞CyGNOME-2的
时候也是被六、七十个包搞得晕头，后来部分包被Gerrit P. Haase和Yaakov Selkowitz加入了cygwin正式版本,
而桌面部分又不搞，而且对于他们不肯采用独立的prefix我觉得很不爽，因为这样的话非“官方”包不好维护了，索性不搞了。
不过从讨论中来看XFCE倒是获得了众口一致的好评。嗯，看来有必要更新cygwin port了。
Patrick在ChangeLog里面详细解释了原因:
gnome/*:
Removed from -current, and turned over to community support and distribution. I'm not going to rehash all the reasons behind this, but it's been under consideration for more than four years. There are already good projects in place to provide Slackware GNOME for those who want it, and these are more complete than what Slackware has shipped in the past. So, if you're looking for GNOME for Slackware -current, I would recommend looking at these two projects for well-built packages that follow a policy of minimal interference with the base Slackware system:
http://gsb.sf.net
http://gware.sf.net
There is also Dropline, of course, which is quite popular. However, due to their policy of adding PAM and replacing large system packages (like the entire X11 system) with their own versions, I can't give quite the same sort of nod to Dropline. Nevertheless, it remains another choice, and it's _your_ system, so I will also mention their project:
http://www.dropline.net/gnome/
Please do not incorrectly interpret any of this as a slight against GNOME itself, which (although it does usually need to be fixed and polished beyond the way it ships from upstream more so than, say, KDE or XFce) is a decent desktop choice. So are a lot of others, but Slackware does not need to ship every choice. GNOME is and always has been a moving target (even the "stable" releases usually aren't quite ready yet) that really does demand a team to keep up on all the changes (many of which are not always well documented). I fully expect that this move will improve the quality of both Slackware itself, and the quality (and quantity) of the GNOME options available for it.
Folks, this is how open source is supposed to work. Enjoy. :-)
虽然Dropline GNOME等的存在也是一个诱因，虽然我喜欢GNOME界面的简洁，但GNOME安装之麻烦似乎也是不争的事实:
"How ironic, seeing that Gnome tries to be the simplest and easiest to
use full-featured desktop on Linux. I guess easy to use doesn't mean
easy to package."
"At one point, I had a printout of all the deps for Gnome. It was a huge
spiderweb of tangles that had to be decoded and followed exactly to get
Gnome to build."
"Have you ever tried to build GNOME?! Just take a look at the build scripts [uky.edu] for the two in Slackware. KDE has a unified build script. GNOME is a dependency nightmare."
use full-featured desktop on Linux. I guess easy to use doesn't mean
easy to package."
"At one point, I had a printout of all the deps for Gnome. It was a huge
spiderweb of tangles that had to be decoded and followed exactly to get
Gnome to build."
"Have you ever tried to build GNOME?! Just take a look at the build scripts [uky.edu] for the two in Slackware. KDE has a unified build script. GNOME is a dependency nightmare."
我当初搞CyGNOME-2的
时候也是被六、七十个包搞得晕头，后来部分包被Gerrit P. Haase和Yaakov Selkowitz加入了cygwin正式版本,
而桌面部分又不搞，而且对于他们不肯采用独立的prefix我觉得很不爽，因为这样的话非“官方”包不好维护了，索性不搞了。
不过从讨论中来看XFCE倒是获得了众口一致的好评。嗯，看来有必要更新cygwin port了。
Patrick在ChangeLog里面详细解释了原因:
gnome/*:
Removed from -current, and turned over to community support and distribution. I'm not going to rehash all the reasons behind this, but it's been under consideration for more than four years. There are already good projects in place to provide Slackware GNOME for those who want it, and these are more complete than what Slackware has shipped in the past. So, if you're looking for GNOME for Slackware -current, I would recommend looking at these two projects for well-built packages that follow a policy of minimal interference with the base Slackware system:
http://gsb.sf.net
http://gware.sf.net
There is also Dropline, of course, which is quite popular. However, due to their policy of adding PAM and replacing large system packages (like the entire X11 system) with their own versions, I can't give quite the same sort of nod to Dropline. Nevertheless, it remains another choice, and it's _your_ system, so I will also mention their project:
http://www.dropline.net/gnome/
Please do not incorrectly interpret any of this as a slight against GNOME itself, which (although it does usually need to be fixed and polished beyond the way it ships from upstream more so than, say, KDE or XFce) is a decent desktop choice. So are a lot of others, but Slackware does not need to ship every choice. GNOME is and always has been a moving target (even the "stable" releases usually aren't quite ready yet) that really does demand a team to keep up on all the changes (many of which are not always well documented). I fully expect that this move will improve the quality of both Slackware itself, and the quality (and quantity) of the GNOME options available for it.
Folks, this is how open source is supposed to work. Enjoy. :-)
2005年3月15日星期二
xffm back to cygwin!
从cygwin/windows的角度来看，xffm(这里指4.2版本)的代码模块化方面可谓混乱之极, xffm可执行文件和一堆共享库相互依赖，这在Windows下是不允许的。这就使得xffm-4.2非常难以移植到cygwin上来。
但今天终于再此搞定了，虽然费了整整一天。(但我还是更喜欢用rox)
大致的方法如下:
- 将smb模块和将libs目录下的库编译为静态库
- 将xffm与上述模块进行链接，得到xffm.exe, 用dlltool 输出(export)xffm.exe的全部public符号
- modules下的模块全部依赖于xffm.exe
依赖于libs目录下的一堆库，这些库当中又有引用xffm中的符号的情况；smb模块似乎是可以不编译的，但
libs目录下面的那些库偏偏又用到了smb可加载情况下才有的一些功能；另外modules目录学唉还有一堆插件，实现书签、回收站等虚拟文件系统；
xfdiff4这个小功能也需要libs目录下的libxffm_secondary里面的一些函数。
因为windows下不允许一个可执行文件或者动态库中包含未定义的符号, 所以需要仔细界定一个函数或者变量是在哪里实现，所以从4.1.90版本开始一直搞不定这个东西的移植，每次开始折腾一会儿就晕了。
仔细琢磨了一下代码结构，发掘其实也蛮简单，将原来libs下面的共享库变成静态库不就行了?
但这样的大调整，仅仅靠修改Makefile.in不禁会繁死，而且还很难成功，因为有些东西(比如将编译动态库改为编译静态库，因为用了libtool这些东西)靠修改Makefile.in不知道怎么下手。
于是我从Makefile.am下手，运气好的是，用automake重新生成Makefile.in很顺利，并没有用到什么目前cygwin下面没有的宏。
源代码补丁正在整理中，过两天就可以上载到主页上去了。
The xffm executable used some symbols defined in the libraries in
directory `libs', but these libs also reference some symbols defined
in the xffm executable; the smb module seems to be loadable, for
supporting some systems that don't have smb support , but the libraries
in `libs' insist to call some functions implmented in smb module.
As Windows doesn't allow undefined symbols in the executable and shared
libraries, thus we should know exactly where a symbols is implemented.
Starting from version 4.1.90 of xffm, I neven succeed in porting xffm
to cygwin. Every time I started to work on it, I would be confused and
disoriented just in a few minutes.
I
walked through the code structure, suddenly the God shed some lights on
me: why not just build those libraries into static ones and link xffm
to them?
Then I tried, works! (This change requires me to hacked the Makefile.ams. I'm not familar with
automake/autoconf. But fortunately enough, I got no any error when
running automake.)
Now I'm examining the modification to got a source patch. Maybe you can see it on my repository in a few days.
但今天终于再此搞定了，虽然费了整整一天。(但我还是更喜欢用rox)
大致的方法如下:
- 将smb模块和将libs目录下的库编译为静态库
- 将xffm与上述模块进行链接，得到xffm.exe, 用dlltool 输出(export)xffm.exe的全部public符号
- modules下的模块全部依赖于xffm.exe
From the viewpoint of cygwin/windows, the module structure of xffm-4.2 is a whole mass. The xffm executable and a pack of shared libraries used each other's symbols, which is not allowed on
cygwin/windows. This made it very hard to port xffm-4.2 to cygwin.
But now xffm (4.2) is back to cygwin! I spent a whole day on this. (Nevertheless I'd prefer rox to xffm).
- Turn the libraries in directory `libs' into static libraries
- Link xffm against the libraries above and then we have xffm.exe. Use dlltool to export all the public symbols of xffm.exe.
- Link the modules in directory `modules' against xffm.exe.
依赖于libs目录下的一堆库，这些库当中又有引用xffm中的符号的情况；smb模块似乎是可以不编译的，但
libs目录下面的那些库偏偏又用到了smb可加载情况下才有的一些功能；另外modules目录学唉还有一堆插件，实现书签、回收站等虚拟文件系统；
xfdiff4这个小功能也需要libs目录下的libxffm_secondary里面的一些函数。
因为windows下不允许一个可执行文件或者动态库中包含未定义的符号, 所以需要仔细界定一个函数或者变量是在哪里实现，所以从4.1.90版本开始一直搞不定这个东西的移植，每次开始折腾一会儿就晕了。
仔细琢磨了一下代码结构，发掘其实也蛮简单，将原来libs下面的共享库变成静态库不就行了?
但这样的大调整，仅仅靠修改Makefile.in不禁会繁死，而且还很难成功，因为有些东西(比如将编译动态库改为编译静态库，因为用了libtool这些东西)靠修改Makefile.in不知道怎么下手。
于是我从Makefile.am下手，运气好的是，用automake重新生成Makefile.in很顺利，并没有用到什么目前cygwin下面没有的宏。
源代码补丁正在整理中，过两天就可以上载到主页上去了。
The xffm executable used some symbols defined in the libraries in
directory `libs', but these libs also reference some symbols defined
in the xffm executable; the smb module seems to be loadable, for
supporting some systems that don't have smb support , but the libraries
in `libs' insist to call some functions implmented in smb module.
As Windows doesn't allow undefined symbols in the executable and shared
libraries, thus we should know exactly where a symbols is implemented.
Starting from version 4.1.90 of xffm, I neven succeed in porting xffm
to cygwin. Every time I started to work on it, I would be confused and
disoriented just in a few minutes.
I
walked through the code structure, suddenly the God shed some lights on
me: why not just build those libraries into static ones and link xffm
to them?
Then I tried, works! (This change requires me to hacked the Makefile.ams. I'm not familar with
automake/autoconf. But fortunately enough, I got no any error when
running automake.)
Now I'm examining the modification to got a source patch. Maybe you can see it on my repository in a few days.
2005年3月1日星期二
source patches for xfce4-4.2.1.1 cygwin port
I've uploaded the source patches to my cygwin repository. (directly download, detail info)
- Patch for Terminal-0.2.4 (and dbus, exo)
also included (note: vte required).
- I improved the autobuild script a lot. Each package could be configurable in autobuild.conf.
Still no binary packages, due to bandwidth
limit. I'm tring to find a wide band to upload them in this week.
- Patch for Terminal-0.2.4 (and dbus, exo)
also included (note: vte required).
- I improved the autobuild script a lot. Each package could be configurable in autobuild.conf.
Still no binary packages, due to bandwidth
limit. I'm tring to find a wide band to upload them in this week.
2004年12月22日星期三
考虑是否要结束cygnome2项目
今日给cygnome2的群组发了个邮件，说我正在考虑是否要宣判cygnome-2的死刑。
因
为我一直没有时间来更新它；而同时因为gnome2包在cygwin官方版本的引入，原来的包又不能成功地运行，老有人报告这样那样的问题。所以现在的是
等整个gnome2桌面在cygwin官方版本中出现，但问题是进度似乎太慢了一点，最近一个月已经几乎停滞了——难道他们不打算引入桌面部分的包?
Hi, all
key point (if you're not patient enough):
- The co-existence of the some packages (such as gtk, ORBit) in this project and in cygwin net release could cause a lot of compatibility problems
- There's no need any longer to keep this project
- I'm considering freezing this project.
Recently, I got some issue report such as
"Can't find gdk_threads_lock in cyggdk DLL"
"cyggdk_pixbuf-2.0-0.dll error"
"Gnome2 cyglinc-1.dll missing"
etc.
Most of these problems are caused by the fact that you installed some base Gnome2 packages from cygwin net release and other stuff from our project.
Our packages are based on Gnome 2.4, and because of short of hands, we couldn't keep these packages up-to-date. And with Gerrit P. Haase's and Yaakov Selkowitz's efforts, Gnome2 packages are getting into cygwin net release. Surely, their work are based on the recent releases, i.e. starting from Gnome 2.6, and some of they have been updated to Gnome 2.8.
For example, in Gnome 2.4, linc is a standalone package, thus we have cyglinc-1.dll in our project, and it is used by some other packages. But in Gnome 2.6, the source code of linc is included in ORBit, and linc is no longer a standalone library. Now cygwin net release got latest release of ORBit included (with cygwin's setup.exe, you'll upgrade to that version automatically). If now you want to use our gnome-session, you know, you're doomed to encounter the problem such as "cyglinc-1.dll missing".
And there're a lot problems like this.
But I think putting Gnome2 packages into cygwin net release is in right direction, as it would attact more people to get into this porting work, which would improve the patches. And when these patches getting into upstream release, perhaps cygwin would become an official platform that Gnome would support, just like that kde would do.
Thus I think there is no need to maintain this project (If there's some, that must be that s the progress that Gnome2 packages getting into cygwin net release is too slow, that some of you are not patient enough to wait, thus you want to use our gnome-desktop on new glib/gtk/ORBit packages from cygwin net release, which is not easy:-(
screen.width/2)this.width=screen.width/2
}" vspace="2" border="0" />
Another reason is that, even some of you think there's worthiness for this project, I don't have enough time to do maintain about 60 packages. The patches done on Gnome 2.4 are far from stable (GConf would cause application hangs, the UI would hang there even if the application quitted, and so on, and so on)
OK, now I would freeze this project. The setup.ini would be removed.ini, i.e. it won't be available for cygwin setup.exe any longer. But you can download binary packages manually.
Sorry for the inconvenience brought to you.
CyGNOME-2 project administrator
Yang Guilong
因
为我一直没有时间来更新它；而同时因为gnome2包在cygwin官方版本的引入，原来的包又不能成功地运行，老有人报告这样那样的问题。所以现在的是
等整个gnome2桌面在cygwin官方版本中出现，但问题是进度似乎太慢了一点，最近一个月已经几乎停滞了——难道他们不打算引入桌面部分的包?
Hi, all
key point (if you're not patient enough):
- The co-existence of the some packages (such as gtk, ORBit) in this project and in cygwin net release could cause a lot of compatibility problems
- There's no need any longer to keep this project
- I'm considering freezing this project.
Recently, I got some issue report such as
"Can't find gdk_threads_lock in cyggdk DLL"
"cyggdk_pixbuf-2.0-0.dll error"
"Gnome2 cyglinc-1.dll missing"
etc.
Most of these problems are caused by the fact that you installed some base Gnome2 packages from cygwin net release and other stuff from our project.
Our packages are based on Gnome 2.4, and because of short of hands, we couldn't keep these packages up-to-date. And with Gerrit P. Haase's and Yaakov Selkowitz's efforts, Gnome2 packages are getting into cygwin net release. Surely, their work are based on the recent releases, i.e. starting from Gnome 2.6, and some of they have been updated to Gnome 2.8.
For example, in Gnome 2.4, linc is a standalone package, thus we have cyglinc-1.dll in our project, and it is used by some other packages. But in Gnome 2.6, the source code of linc is included in ORBit, and linc is no longer a standalone library. Now cygwin net release got latest release of ORBit included (with cygwin's setup.exe, you'll upgrade to that version automatically). If now you want to use our gnome-session, you know, you're doomed to encounter the problem such as "cyglinc-1.dll missing".
And there're a lot problems like this.
But I think putting Gnome2 packages into cygwin net release is in right direction, as it would attact more people to get into this porting work, which would improve the patches. And when these patches getting into upstream release, perhaps cygwin would become an official platform that Gnome would support, just like that kde would do.
Thus I think there is no need to maintain this project (If there's some, that must be that s the progress that Gnome2 packages getting into cygwin net release is too slow, that some of you are not patient enough to wait, thus you want to use our gnome-desktop on new glib/gtk/ORBit packages from cygwin net release, which is not easy:-(
screen.width/2)this.width=screen.width/2}" vspace="2" border="0" />
Another reason is that, even some of you think there's worthiness for this project, I don't have enough time to do maintain about 60 packages. The patches done on Gnome 2.4 are far from stable (GConf would cause application hangs, the UI would hang there even if the application quitted, and so on, and so on)
OK, now I would freeze this project. The setup.ini would be removed.ini, i.e. it won't be available for cygwin setup.exe any longer. But you can download binary packages manually.
Sorry for the inconvenience brought to you.
CyGNOME-2 project administrator
Yang Guilong
Powered by ScribeFire.
订阅：
博文 (Atom)