I recommend keeping the tools under source control, so you always know
where they are and what they are.
If you don't want to do that, the simplest thing is probably just to
normalize the WIX variable in the script you use to launch build.
Something like
for %%X in ("%WIX%") do set WIX=%%~fsX
should set it to its short-name form (and clean out any \..\ if there
were any).
> From: Bruce Cran [mailto:br...@cran.org.uk]
> Sent: Friday, January 15, 2010 1:06 PM
>
> I'm using the WDK to build a C++ custom action DLL that gets
> included in my MSI that I create using WiX 3.5. The problem
> I've come across is that the WiX headers are located in
> C:\Program Files (x86)\Windows Installer XML v3.5\SDK\inc, and
> the WDK doesn't appear to recognise long filenames.
>
> I've tried adding $(WIX)SDK\inc both with and without
> quotes to the 'sources' file, but the only thing that works is
> using C:\PROGRA~2\WINDOWS~1.5\SDK\doc. I'd rather not use that
> because it'll be wrong on 32-bit Windows.
>
> Does anyone know a way around this to avoid hard-coding paths that
> other developers are going to have to change for their machines?
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
