[JIRA] Commented: (SSPCPP-506) Add WiX Builds into VisualStudio/MsBuild

[Rod Widdowson (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14438#comment-14438 ] 

Rod Widdowson commented on SSPCPP-506:
--------------------------------------

Design notes

The end goal here is 

1) To be able to hit "build all" and have all the msi's pop out at the end.  This means:

  a) Adding .wixproj files as appropriate and making any changes needed to the WXS files to ensure things still work when run from the command line and from the IDE
  b) Getting the build ordering correct,
  c) Getting the build dependencies encapsulated.  Thus is shibd1_4.dll is rebuilt then the associated msm must be rebuilt and if the msm is rebuilt then the msi's must be rebuilt.  I think this is done via project references.

a) is under control
b) is just a matter of typing
c) needs further study

2) To make sure that all configuration is in one place.

We want to get rid if versions.wxi.  Further we really want to separate out the things we want to check in to svn (like version numbers and dll names) from local configuration ("dependencies are built _here_, this project is built _there_").

Currently everything goes in to the per system bucket for VC.  This is not available to WixProj's and anyway is too general.  I propose that we introduce two new property sheets.  One is checked into SVN and contains all the versions as well as the guddling that we have to do to paths and so forth.  The other contains just the paths and is not checked in.  All projects (vcc and wix) will include these two files.  In addition the wix projects will have enough clever stuff in their definitions to pass these variables in to the compilation stage.

At this stage other people doing builds just end one two line file with their dependencies.  Every time we change a rev we change the other property sheet and check it in.  I propose that where changing a name requires changing a GUID we move that into the property sheet as well thus leaving the wxs files mostly unchanged from release to release.



> Add WiX Builds into VisualStudio/MsBuild
> ----------------------------------------
>
>                 Key: SSPCPP-506
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-506
>             Project: Shibboleth SP - C++
>          Issue Type: Task
>          Components: Installation / Packaging
>    Affects Versions: 2.5.0
>            Reporter: Rod Widdowson
>            Assignee: Rod Widdowson
>   Original Estimate: 3 days
>  Remaining Estimate: 2 days, 7 hours
>
> We need to take the stuff which is currently scattered inside two batch files and a wix include file and put them into proper projects within the Shibboleth master solution (.sln).  Then we can arrange to collect parameterization from the MSBuild properties file and get the dependencies such that you just say "build" and out pops all the msm and msi files that you need.
> This was not done in the first pass of Wix-isation so as to control risk, but it leaves the Windows build needlessly fragmented, tedious and this risk-prone.
> Wix has support for most of this stuff so it is "just" a matter of swapping in the tech and building the thing.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira