The wix39-binaries.zip has an "sdk\inc" folder that should have the published headers. I'm pretty sure the MSI installs the headers as well. If there are headers missing, we should fix that bug.
You shouldn't need to go get the source code of the WiX toolset unless you want to improve the WiX toolset itself (which is what this mailing list is all about and we welcome more people doing it! <smile/>) _______________________________________________________________ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -----Original Message----- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Wednesday, July 16, 2014 3:54 PM To: WiX toolset developer mailing list Subject: Re: [WiX-devs] Wix 3.9.702 Results But my point is that I don't see any headers in the installation directory of any version. I ended up with the idea that I had to download the *source code* of WiX in order to get headers for custom actions or BAs. -- Nicolás 2014-07-16 19:36 GMT-03:00 John Cooper <jocoo...@jackhenry.com>: > If you look at a C++ custom action, you'll note that it links into one or > more libraries in the SDK and has one or more include files. It is a minor, > one-time problem, but after an upgrade to a new version of Wix, these no > longer line up. The issue was actually much bigger with Wix 3.5 to 3.6 as > there were platform folders sprinkled in with the paths that had to be > contended with. Again, it's a one time problem, but it's a (minor) pain. > -- > John Merryweather Cooper > Build & Install Engineer - ESA > Jack Henry & Associates, Inc.® > Shawnee Mission, KS 66227 > Office: 913-341-3434 x791011 > jocoo...@jackhenry.com > www.jackhenry.com > > ________________________________________ > From: Nicolás Alvarez [nicolas.alva...@gmail.com] > Sent: Wednesday, July 16, 2014 10:22 AM > To: WiX toolset developer mailing list > Subject: Re: [WiX-devs] Wix 3.9.702 Results > > 2014-07-11 13:48 GMT-03:00 John Cooper <jocoo...@jackhenry.com>: >> However, I had to uninstall 3.9.702 and reinstall 3.8 as my custom >> action library has a few C++ paths and these don’t migrate well between >> versions. >> What would be nice would be some full on environment variables that >> define the version-specific parts of the paths to Header and Lib >> files, and then modifying the C++ custom action template to match so >> this manual migration would not be necessary in the future. > > What's this about? Last I checked the WiX binaries don't include > headers (which I find annoying). What C++ paths are you referring to? > > -- > Nicolás ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
