> Who currently builds the Windows stuff? I have built the Windows package for the last little while, though it has been Dirk who has kindly built them before then.
> Robert are you saying that your > Inno Setup for Plucker Desktop does everything you outlined? Yes. It is an installer for all the Windows components of the windows Package. The script is in CVS under the plucker_desktop/installer/msw but it is in fact an installer for everything, since easier to find and install things together. The .spec file in plucker_desktop/installer/linux is just for Plucker Desktop, since Linux has proper package management. Both Dirk and I agreed to put all the components into one installer for the Windows platform, since that is the par for that OS. > Are we saying that the Windows Plucker Desktop installer is using Dirk's > last build? It is using the tools to provide a separate commandline stub, as well as the toolchain for whatever batchfile/automatic execution are already in use. I see the following programs from Dirk: > DBTool.exe - probably not needed since Plucker Desktop takes care of > channels now Yes, cut. > EditStub.exe - no idea what this does Yes, cut. I think it just opened up Notepad.exe with a file. > Plucker.dll - no idea what this does > Plucker.exe - not sure if this is used Don't recall. Not needed though. > plucker-build.exe - this is what Plucker Desktop calls Dirk's commandline shell for plucker-build. It is in the start menu listed as "Commandline Plucker (plucker-build.exe)". It started without arguments it flies up a box to enter some arguments, otherwise it executes python spider with the arguemtns. Left in for people who are using it in the batch files. The Desktop bypasses it and just calls the python script directly, since the Windows API is [still] deficient in regards to killing a process. The Microsoft API only allows proper killing of a process by sending a close event to a window, and a windowless application obviously has no windows. Terminating a windowless application (plucker-build.exe) that spawned another windowless application (python.exe) couldn't be done with such a poor API. Using python.exe directly made it possible to terminate python.exe. In Plucker Desktop, there is a hack added for NT/Me/XP versions that allows a "killing from within" that will overcome the deficient API. > RunSync.exe - used to run the parser from the short cut - probably not > needed anymore There is a RunSync.exe and a /Conduit/Conduit.exe. These are used by the older system to put it in the install directory for a Palm. Also kept in case people have it set up in their batch files or custom setups. There is also a /Bmp2TBmp/Bmp2TBmp.exe that is used for the older windowspil parser, in case people want to use that parser (though pil2 gives better results without requiring it). Best wishes, Robert _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
