I can document it more fully but basically I created new default project files
for wixproj, vcxproj and csproj and then put the files in them. The C++ was the
hardest as I needed to copy across all the build settings. Once you have
standard project files building is easy and the settings can all be overridden
from an external build process rather than in the project file.
Neil
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 18 February 2013 23:09
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Building WiX Code
Okay, that's getting to the crux of the issue. What is missing or what did you
add to make you so much faster outside of the WiX build process that made it
worthwhile to do that work?
From my point of view, you should be able to get the same exact wins inside the
WiX toolset without having to do the work to extract the code out of the WiX
build process and create a new one.
What was different outside of the WiX toolset?
PS: if someone wants to go about getting the extension build to use the built
files they'd be available in the SDK, that seems reasonable to me as long as it
makes it easier to build the extensions, not harder. <smile/>
On Mon, Feb 18, 2013 at 2:40 PM, Neil Sleightholm
<n...@x2systems.com<mailto:n...@x2systems.com>> wrote:
I appreciate this wouldn’t be trivial to arrange but I believe the benefits
would be worth it. I base this on the speed at which I have been able to
develop the extended BA, spending time breaking it out of the WiX build has
made it so much easier to work on.
Neil
From: Bob Arnson [mailto:b...@joyofsetup.com<mailto:b...@joyofsetup.com>]
Sent: 18 February 2013 21:07
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: Re: [WiX-devs] Building WiX Code
On 18-Feb-13 14:22, Neil Sleightholm wrote:
There is an SDK for WiX so I would expect the extensions to use it
I think that's the root disconnect: The extensions that ship with WiX aren't
separate from WiX, so there's been no reason to build them separately. It's not
that I think they shouldn't or that it's a bad idea, just that that's not how
it's been done. So building them separately is reasonable -- but it can't break
the things that need to work for things that ship with WiX, such as versioning
and error numbers.
I'd add that breaking the build into separate partitions like this reduces the
extent to which the build can be parallelized. Minimizing that impact would
also be good.
Making all that work (as well as making the build output match the staging
output) is probably a 2.5 on a difficulty scale of 1 to 10.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net<mailto:WiX-devs@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wix-devs
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
