Thank you Phil for the suggestion, but unfortunately it didn't work. The
wixproj files are identical except for guids and descriptions. The OutputName
elements contain just the application names. There was a difference in
ItemGroup order which I changed to make the ordering identical, closed,
reloaded, exited, rebuilt - still "Any CPU" for the TEST installer output .exe.
The text "Any CPU" doesn't appear anywhere in either of the wixproj files.
This element is identical in both:
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x86' ">
<OutputPath>bin\$(Configuration)\</OutputPath>
<IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath>
<CompilerAdditionalOptions>-arch x86</CompilerAdditionalOptions>
</PropertyGroup>
- Robert
-----Original Message-----
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Thursday, 7 November 2013 1:02 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] platform x86 vs AnyCPU problems
If I understand the issue, I would go to each of the two project files
(Prod.*proj and TEST.*proj), right click on each file and select 'Unload', then
right click and select Edit Prod.wixproj (or TEST.wixproj). Then compare the
working to the non-working file. It sounds like your OutputName element in the
'global' (top most) PropertyGroup has been overwritten to 'Any CPU' (which is a
possible value VS might pass into $(Platform) MSBuild property).
I was working on a similar issue in my build process recently, because I have a
mixture of wix, C#, and C++ projects which require different platform
specifications. In the course of doing that I came across the chm (and Candle
/? output) which indicates that Package/@Platform (and -d:Platform) is
discouraged (or deprecated) and that -arch is prefered. So I added the
InstallerPlatform element to my project files and set it to x64 in the
situation where I needed the -arch=x64.
When you finish editing a .*proj file you need to close it and then right click
and 'reload' it. I have also found that if you change any .target or .prop
file that is imported by the project, you really need to close the solution and
re-open the solution (so I often do that anyway just to make sure that I know
that my new changes have been loaded prior to testing them). If you do not
close and reopen the solution, imported targets stay in memory and do not
reflect changes made after they were first loaded (at least that is the
behavior of VS2010).
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/platform-x86-vs-AnyCPU-problems-tp7590303p7590322.html
Sent from the wix-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers Accelerate application
performance with scalable programming models. Explore techniques for threading,
error checking, porting, and tuning. Get the most from the latest Intel
processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
