Personally I hate it when there is no option to *not* create Start
Menu/Quick Start/Desktop shortcuts. For each of those steps it
would be nice to have a check box or some other item that allows me to
say "Do Not Create Shortcut." Just my preference, really.<br>
<br>
--Greg<br><br><div><span class="gmail_quote">On 2/4/06, <b class="gmail_sendername">DM Smith</b> <<a href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Troy,<br> Lynn and I have been working on this. Our approach has been a little<br>different. My goal is to get a basic installer for just BibleCS and his<br>has been to create a family of installers for all derivative Sword API
<br>Windows applications. These are not at odds with each other and I think<br>we are nearly there with at least a first pass.<br><br>To finish the first pass, we need a couple of things:<br>1) All the compile artifacts of the build (
e.g. dlls, exes, ...) as I<br>don't have a C++ compile environment. Preferably, these should be what<br>will be used by the installer. Also, if you could give me the paths for<br>these using the checkout scheme below that would be great. Currently, I
<br>am stubbing this with 1.5.6.<br>2) What are the other files that must be included? And for dlls, what<br>versions?<br>(For 1 and 2, if you could create an directory layout of what the final<br>install should be like that might be easier. Essentially, this would be
<br>a zip of what the installation directory would contain right after<br>installation when no modules are installed.)<br>3) What is the minimum set of files to provide the Sword API for other<br>applications? (I want to create a SwordAPI installer that will install
<br>the absolute minimum that a derivative application must have present.<br>This will then be called by those applications installers, if the<br>SwordAPI has not been installed.) Does it need icudt34.dll? Does it need<br>
the install manager? How about all the subdirectories in biblecs/.../stage/?<br>4) In an earlier note, Lynn gave a path to a patch to allow for the<br>modules to be located elsewhere. Is this something that can be included
<br>in 1.5.8 or should it wait for a later release.<br>5) NSIS needs (un)installer icons that work. I am terrible at artwork,<br>so I am not the one to do it. NSIS requires that the size of the<br>installer and uninstaller icons be the same.
<br><br>Can you give me check in privs for the installer directory? Then I can<br>work in there. I think that the following addition to the svn<br>authorization file, would work:<br>[biblecs:/trunk/installer]<br>dmsmith=rw
<br><br>Right now this is where the installer is at:<br>1) Offers the user a choice as to where to install the program and what<br>Start Menu Group to create.<br> It defaults to the same default locations that 1.5.6 uses.
<br>2) The installation<br> a) Installs the files<br> b) creates the registry entries<br> i) The uninstaller is listed in Add/Remove Programs<br> ii) Keys and values are created so that other programs can
<br>discover where Sword is installed.<br> c) creates a desktop shortcut<br> Does not offer the user a choice about this one.<br> Should also probably install to the Quick Start task bar. And it<br>should be a choice, too.
<br> d) creates shortcuts in the Start Menu for<br> i) the Sword program<br> ii) the Sword Install Manager<br> iii) the website<br> iv) the uninstaller<br> It probably should also create a shortcut to help.
<br> e) It adds/changes SWORD_HOME environment variable to point to the<br>installation directory.<br> The installer assumes that prior versions have been deleted. This<br>may be bad.<br> Are there any files that *must* be removed for the install to the
<br>same directory to be successful?<br> For example, is it bad to have icudtXX.dll and icudtYY.dll in the<br>same directory?<br>3) It creates an uninstaller that<br> a) runs InstallManager -uninstall<br> currently, this is broken
<br> b) Removes all files that the installer installed. Leaving all files<br>that the program or user created.<br> c) Removes all shortcuts (that have not been moved)<br> c) Removes empty folders<br> d) Removes registry entries.
<br> The uninstaller does not determine whether there are any dependent,<br>derivative applications and act appropriately.<br> These will have a registry key located under HKLM\software\CrossWire.<br> It should be the responsibility of the last removed derivative
<br>application to remove the SwordAPI.<br><br>Is there anything missing from the above? Must haves? Should haves? Nice<br>to have?<br><br>The last thing needed before the installer(s) is(are) released is robust<br>testing. I know there are somethings that don't work yet and some of the
<br>paths are wrong. And there may be some things, I won't find because I<br>always test the same small set of paths! So after I get the bugs out<br>that I know, testing help would be appreciated.<br><br>In His Service,<br>
DM<br><br>Troy A. Griffitts wrote:<br>> Hey guys,<br>> I spend today trying to build a new installer for the upcoming<br>> release of BibleCS. I'm abandoning the commercial InstallShield<br>> installer we currently use and am trying to make everything work using
<br>> the free NullSoft installer. I gave up after trying to learn the<br>> scripting language and downloaded Eclipse and the NullSoft Installer<br>> plugin for Eclipse. I used a wizard and got it pretty far. Had to
<br>> hand edit the generated script to get it to compile.<br>><br>> There are a few things missing:<br>> Launch Readme.txt and wait for close BEFORE launching<br>> InstallManager.exe<br>> Registry keys correct so Windows Module self-installers (website,
<br>> module download, windows) know where to unzip themselves.<br>> Uninstaller successfully launching "$INSTDIR/InstallManager.exe<br>> -uninstall" to uninstall all modules<br>><br>> I've checked everything in:
<br>> <a href="https://crosswire.org/svn/biblecs/trunk/installer">https://crosswire.org/svn/biblecs/trunk/installer</a> so if you'd like<br>> to give it a shot, please help yourself! It expects the normal:<br>> sword, icu-sword, biblecs directories all checked out at the same level.
<br>><br>> svn co <a href="https://crosswire.org/svn/sword/trunk">https://crosswire.org/svn/sword/trunk</a> sword<br>> svn co <a href="https://crosswire.org/svn/icu-sword/trunk">https://crosswire.org/svn/icu-sword/trunk
</a> icu-sword<br>> svn co <a href="https://crosswire.org/svn/biblecs/trunk">https://crosswire.org/svn/biblecs/trunk</a> biblecs<br>><br>> I'd really welcome the help with this.<br>><br>> -Troy.<br>
<br>_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">
http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page<br></blockquote></div><br>