Hi guys, I've now got to the point where I'm comfortable that a Windows binary might actually work (beta), and I'm going to make one available after I've got round to packaging an installer.
Last night, I found and hacked some of the ice-9/boot-9.scm which was causing a path bug when opening certain pieces of the gEDA suite, so we can now specify GEDADATA with C:\.. style absolute paths to relocate the suite without breaking things. The question now, is how to version, or identify a release: ----------------------------------------------------------- 1. Don't bother - don't make it widely available, and hope the fact it announces 1.5.0 as a version (for my git HEAD + ... + cairo_experiment branch code) won't cause too much grief with a restricted distribution. 2. Leave the version string as is (I'm not sure if we have infrastructure to add a git SHA1 to the version?), and patch the code which prints in the log, and the about box, to make clear what the release really is. 3. Try to add something to the version string: 1.5.0.20080706~79384bb59399cb084c6d6ccebe9725080d363c99 (Perhaps truncating the SHA1 at some point) or: 1.5.0.20080706~pcjc2.cairo_experiment.release1 Before anyone gets too excited, we move onto known bugs: -------------------------------------------------------- 1. Printing - forget it for now (and the foreseeable future). Write ".ps" to file, and use some conversion utility to make into pdf. 2. Saves preferences in the equivalent of %HOMEDRIVE%%HOMEPATH%\.gEDA, rather than the proper "%HOMEDRIVE%%HOMEPATH%\Application Data\gEDA" folder. I'll probably move it to in the future, so beta users ought to expect this old folder gets left around. 3. Some bugs (complete failure) have been noticed when the suite, and the schematics being edited are on different drive letters, e.g.: C:\geda\bin\gschem.exe and D:\work\schematic.sch 4. Relocation will be done by the installer setting some system-wide (or per-user?) environment variables, GEDADATA and GUILE_LOAD_PATH. That is another possible place some setting might need manual clean-up if you wanted to remove the suite entirely. (No other system locations are touched though). 5. Applications icons show the GTK logo, not gEDA icons. Probably fixable, but I may not get around to it. (Minor nit) 6. No start menu entries yet. Might be able to fix that though. 7. Any bugs associated with the cairo branch: - A few nits with non solid line-styles not drawing quite right (or at all) - GDK drawing still used for rubberbanding things - slower than cairo on Win32? - Font sizes are too small wrt. the old gEDA font, and are subject to change - Font selection is done by hitting the lines in the old primitive object based font, so sometimes text is hard to select. - Rubber-banding still uses the old GDK drawing of the old primitive object font I'm happy to provide this binary / installer suite to anyone who asks. (And the various patches to GTK and GUILE I've got to make it work). I'm _not_ looking to make this a general release available from some publicly linked page, supported or otherwise. If you're on geda-dev, or have managed to find this announcement, then I'm quite happy that you get and try this suite (when its packaged). I'm interested in bug reports, but on the basis that this is an experiment, based on non-mainline code. I'm offering no guarantees that this code will be usable, or that I'll ever get round to making it so. Best regards, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list geda-dev@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
