Some further notes re. using enfold.recipe.innosetup

Tim Knapp <tim-gMu3S4noFYp8UrSeD/[email protected]>
Newsgroups gmane.comp.web.zope.plone.installers
Message-ID <1321515179.3046.8.camel@monty>
Hi,

Just some further notes for posterity (in no particular order):
      * If you rerun "bin\installer.exe" you need to delete the "docs"
        dir in the installation dir otherwise the script will fail.
      * When you install InnoSetup, you need to ensure there's no spaces
        in the directory name that InnoSetup is installed in.
      * I also installed the Windows SDK. I used SDK 6.1 for Windows
        2008 R2 (64-bit edition).
      * Seemed like I also need to ensure the install dir defined in
        installer.cfg was the same 'case' (i.e. lower/upper) as the
        existing installation dir (i.e. if I'd run the installer.exe
        already). This may've just been a symptom of my particular
        install.
      * You need to ensure you update the "path" environment variable to
        include the "bin" directory for your Windows SDK compilers. In
        my case this was: C:\Program Files\Microsoft SDKs\Windows 6.1
        \Bin.
      * The process I followed in creating the custom windows installer
        was to install Plone 4.1.2 into a separate directory and copy in
        my custom buildout.cfg and installer.cfg and then run bin
        \buildout -c installer.cfg and finally bin\installer.exe. This
        would then install into a separate "install directory", which in
        my case was L:\plone41. As this was my existing directory that
        I'd been developing in *and* I'd already done the aforementioned
        steps in that directory too, it seemed like it registered
        pywin32 to that directory location so if I ever renamed L:
        \plone41, I could no longer do: "import win32api". This again
        was probably just strangeness related to my particular setup.
      * I also found "installer.exe" produced a lot of errors, mainly
        related to the Windows SDK compilers but that the windows
        installer still came out alright at the end of the process.
      * And finally, I needed a bulk of disk space (21GB+ to build the
        installer so ensure you've got plenty of disk space to spare).

Thanks,
Tim


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.