Thursday 15 July 2010

visual studio - Wix - relationship between heatdirectory directory and preprocessorvariable -



visual studio - Wix - relationship between heatdirectory directory and preprocessorvariable -

i using heat harvest project confused relationship between defined preprocessor variable in visual studio like: sourcedir=$(solutiondir)myproject, <heatdirectory> directory=var.sourcedir , <heatdirectory> directory=$(solutiondir)myproject

which 1 defining source directory going harvested? me looks preprocessorvariable/defined preprocessor variable in vs overwriting directory 1 in headdirectory.

is correct?

one thing clear up, when phone call heat, directory harvest supplied via command line argument heat. sourcedir placeholder path in you'd find actual files harvested, relative directory chose harvest.

it's defined preprocessor variable or path specify light using -b option.

when phone call heat, can tell variable replace sourcedir , when phone call candle, you'll define it.

an example:

heat dir [options] -var var.myprojectdir <dir harvest>

will produce .wxs file $(var.myprojectdir) in place of sourcedir

when phone call candle:

candle [options] -dmyprojectdir=<my project path> <wxs files>

using -d alternative allow define value of preprocessor variable , reference when compile fragment files.

if don't utilize -var , -d options heat , candle, can utilize -b in light , wix utilize effort resolve files using paths. acts environment path variable, in utilize paths specified find files.

visual-studio wix installation heat

No comments:

Post a Comment