Re: [mpp-devel] Building MPP Installers from Source Code (SVN)

[sod/sgt-d <sg...@so...>]

 

i just tested this on a computer that has never had tortoisesvn, nsis, 7z or
md5...

 

7139.exe - 7.39 MB (7,752,312 bytes)

getmpp.exe - 97.1 KB (99,440 bytes)

mpp-800-full.exe - 13.1 MB (13,762,840 bytes)

mpp-800-lite.exe - 7.77 MB (8,151,968 bytes)

mpp-800-max.exe - 13.1 MB (13,763,480 bytes)

mpp-800-portable.paf.exe - 5.24 MB (5,502,152 bytes)

mpp-800-upgrade.exe - 9.30 MB (9,759,472 bytes)

 

everything worked on the first try.

 

your byte sizes will not match mine, but they should be close.

 

additionally...

 

my official mpp folder size is:  317 MB (332,625,279 bytes)

 

the svn download of mpp for me was:  317 MB (332,699,144 bytes)

 

you should be seeing similar values.

 

/sgt

 

  _____  

From: mpp...@li...
[mailto:mpp...@li...] On Behalf Of sod/sgt-d
Sent: Tuesday, April 10, 2007 1:45 AM
To: mpp-beta
Subject: [mpp-beta] Building MPP Installers from Source Code (SVN)
Importance: High

 

 

Building MPP Installers from Source Code (SVN)

 

This email will attempt to outline what steps are required to build the MPP
Installers from source code.

 

Some of you already know this...  but your software is probably sorely out
of date.  See below.

 

For some of you, this information is all new.  None of this is hard though,
so bear with me.

 

Since I am sending this email though the MPP Mailing List, it will be
publicly available for everyone once it hits the archives.

 

 

First, some quick notes...

 

Currently when I make MPP releases, I end up with 51.5+ megs of installers
that I first have to upload to a remote location, then I have to notify
everyone, then they have to download and install the new exe's.  I might
have only changed two files that were a total of 70kb...  it doesn't matter
how small the change was, I still have to rebuild and then upload over 50mb
of files.  I don't mind doing this from time to time for public betas or for
official releases, but for private betas this is very time consuming.

 

With the new SVN Checkout system things will be much simpler for private
beta testing.  If I change the same two files totaling 70kb, when I commit
(upload) the changes, only two files get uploaded.  The change is available
almost instantly.  I can then send a notice through the MPP Mail List
(SourceForge) so everyone knows that a change was committed.  Beta testers
would then right click on their MPP SVN Repository and select "SVN
Checkout".  Only the two changed files would be downloaded and your
repository would then be current.  At this point you can rebuild your
installer exe's on your local hard drive and then run them.  All of this can
now happen within minutes instead of hours.

 

Note:  The first time you run SVN Checkout it has to download the entire
package.  Every time you run SVN Checkout after that, it only downloads the
changes at the latest revision level.

 

So, basically what I am trying to do is push out small updates and then
everyone can almost instantly build new packages that they can test locally.

 

This might look complicated, but it's really not too bad at all.

 

Here are the steps...

 

 

(1)  Getting "Juiced In" to MPP and SF.net

 

Consider creating an SF.net account:  http://sourceforge.net
<http://sourceforge.net/> 

 

Join the MPP Mailing Lists:  http://sourceforge.net/mail/?group_id=183794

 

Join the MPP Forums:  http://sourceforge.net/forum/?group_id=183794

 

If you really want to stay current, I strongly suggest signing up for all
three of these mailing lists:

 

mpp-devel:  http://lists.sourceforge.net/mailman/listinfo/mpp-devel

 

mpp-beta:   http://lists.sourceforge.net/mailman/listinfo/mpp-beta

 

mpp-user:  http://lists.sourceforge.net/mailman/listinfo/mpp-user

 

 

(2)  Downloading and Installing some Software

 

Download and install TortoiseSVN, NSIS, 7-Zip and MD5

 

Version and builds shown here were updated on 4/10/07.  As a general rule it
is always a good idea to keep up with the current builds of all of these
tools.

 

If you want to know when I have updated my own software, sign up for the
mpp-devel list as well as mpp-beta.

 

TortoiseSVN 1.4.3.8645 (SVN 1.4.3)

 

Website:  http://tortoisesvn.tigris.org/

32 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-win32-
svn-1.4.3.msi?download

64 Bit Download:
http://prdownloads.sourceforge.net/tortoisesvn/TortoiseSVN-1.4.3.8645-x64-sv
n-1.4.3.msi?download

 

Nullsoft Scriptable Install System (NSIS) 2.25

 

Note:  Install NSIS to default folder (C:\Program Files\NSIS) or edit
build.cmd to reflect your NSIS path.

 

Website:  http://nsis.sourceforge.net/

Download:
http://prdownloads.sourceforge.net/nsis/nsis-2.25-setup.exe?download

 

7-Zip

 

Website:  http://www.7-zip.org/

 

I recommend 4.44 Beta, your call...

 

7-Zip 4.44 Beta 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444.exe?download

7-Zip 4.44 Beta 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z444-x64.msi?download

7-Zip 4.42 32 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442.exe?download

7-Zip 4.42 64 Bit:
http://prdownloads.sourceforge.net/sevenzip/7z442-x64.msi?download

 

MD5

 

Put this file in your Windows or Windows\System32 folder:

 

Download:  http://ucheetmfer.com/files/md5.exe

 

 

(3)  Setting up a local SVN Repository and downloading the MPP Source Code

 

Open Windows Explorer and browse to C:

 

Create a new folder:  c:\svn

 

Create a new subfolder:  c:\svn\mIRC Power Pack

 

Right click the new "mIRC Power Pack" folder (c:\svn\mIRC Power Pack) -> SVN
Checkout...

 

URL of the MPP Repository:  https://mpp.svn.sourceforge.net/svnroot/mpp/

 

Uncheck "Only check out top folder" and "Omit externals"

 

Check "Head Revision"

 

Click OK.

 

TortoiseSVN should start downloading files.

 

 

(4)  Building the MPP Installers

 

When SVN Checkout is complete, build the MPP installers.

 

Locate this file:  c:\svn\mIRC Power Pack\install\build\build.cmd

 

If you DO have a code signing certificate you can leave sign=1 but you will
have to modify build.cmd to point to your PFX (certificate) file.  You can
get a free code signing certificate here:
http://www.ascertia.com/OnlineCA/codesign.aspx?linkID=40.  Ascertia free
certificates expire after one year, so you have to keep up with them.

 

If you DO NOT have a code signing digital certificate...

 

Right click build.cmd and select "Edit"

 

change:  set sign=1

 

to:  set sign=0

 

Exit and save.

 

Either way, let's test the build now...

 

Double click build.cmd

 

You might see some minor errors, but when the builds are complete you should
have installers, logs and md5's in the automatically created
"install\release" folder.

 

Note:  After editing build.cmd or any other files, the files and the folders
will change from a green icon to a red icon.  This indicates that your
copies are no longer the same as the SVN tree online.  This is normal any
time files or folders are modified.

 

In other words, if you have to make a change to these files, don't worry
that their icon has changed from green to red - it's totally normal.

 

 

In ALL CASES...  success or failure...  please EMAIL ME ASAP and report your
results!!!

 

 

/sgt