The preprocessor is single pass today so this does not work.
On Wed, Oct 10, 2012 at 2:27 AM, wrote:
> How can I resolve $(var.Feature) as "ProjectName" part of
> $(var..TargetPath) in the following example?
>
> VS error:
> Error 157Ill-formed preprocessor function
> '$var.($(var.Feature))M
How can I resolve $(var.Feature) as "ProjectName" part of
$(var..TargetPath) in the following example?
VS error:
Error 157Ill-formed preprocessor function
'$var.($(var.Feature))Module.TargetPath'. Functions must have a prefix (like
'fun.'), a name at least 1 character long, and matching o
Hi List
I need to include some extra files in a project but only when i build it for
the "de-de"
locale. So is it possible to do something like this:
Yours
Rune Henssel
--
Live Security Virtual Confe
I have opened an issue here:
https://sourceforge.net/tracker/?func=detail&aid=3374854&group_id=105970&atid=642714
On 21/07/2011 17:16, Rob Mensching wrote:
> Sounds like a bug.
>
> On Thu, Jul 21, 2011 at 2:22 AM, Stefan Pavlik wrote:
>
>> Hi All
>>
>> I need to include some part code depending
Sounds like a bug.
On Thu, Jul 21, 2011 at 2:22 AM, Stefan Pavlik wrote:
> Hi All
>
> I need to include some part code depending on existence of several
> macros. I would write something like this:
>
>
>
>
>
> Problem is that candle will generate error CNDL0150 (Undefined
> preprocessor variab
On 21/07/2011 11:42, Peter Shirtcliffe wrote:
> Rather than depending on the existence of the variables, could you give them
> an arbitrary null/empty/false value as a default and test for them being not
> null/empty/false ? Would that work ?
Hm... It is problem because the macros are created dyn
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Preprocessor
On 21/07/2011 11:30, Peter Shirtcliffe wrote:
> This works for us
>
>
>
>
This works also for me, but it is not possible (AFAIK) to use 'OR',
'AND' operators in , expression
On Thu, Jul 21, 2011 at 11:30 AM, Peter Shirtcliffe wrote:
> This works for us
>
>
>
>
>
>
This will simplify a bit the code but still it is not very pretty:
--
Stefan Pavlik | stefan.pav...@gmail.com
Lietavska 14 | 851 06 Bratislava | Slovak Republic
On 21/07/2011 11:30, Peter Shirtcliffe wrote:
> This works for us
>
>
>
>
This works also for me, but it is not possible (AFAIK) to use 'OR',
'AND' operators in , expressions.
--
Stefan Pavlik | stefan.pav...@gmail.com
Lietavska 14 | 851 06 Bratislava | Slovak Republic
--
My own reply:
On Thu, Jul 21, 2011 at 11:22 AM, Stefan Pavlik wrote:
>
>
>
>
Of course I can use following code but it is a bit unhandy (to check for
aprox. 20 possible macros)
--
Stefan Pavlik | stefan.pav...@gmail.com
Lietavska 14 | 851 06 Bratis
This works for us
-Original Message-
From: Stefan Pavlik [mailto:stefan.pav...@gmail.com]
Sent: 21 July 2011 10:22
To: WiX-users
Subject: [WiX-users] Preprocessor
Hi All
I need to include some part code depending on existence of several
macros. I would write something like this
Hi All
I need to include some part code depending on existence of several
macros. I would write something like this:
Problem is that candle will generate error CNDL0150 (Undefined
preprocessor variable) if any of the variables is not defined.
According to http://wix.sourceforge.net/manual-wi
Has anyone created a preprocessor extension for generating an informational
message (that they can share)? Along the lines of the built-in error and
warning message functionality, but with a type of 'Information'. I am
currently using warning messages, but these are polluting the build logs.
T
Steve [mailto:b...@nbsin.com]
Sent: Thursday, 19 May 2011 5:26 a.m.
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Preprocessor variable question
I am relatively new to WiX, so please excuse me if my question seems
juvenile. Come to think of it, maybe you'd app
I am relatively new to WiX, so please excuse me if my question seems juvenile.
Come to think of it, maybe you'd appreciate an easy question for once!
I am using VS2010 and using a build server, so no local builds. In my WiX
setup, I have my preprocessor variable defined as 'BinariesRoot=$(OutD
On 31-Aug-10 13:41, Maillet, Ed wrote:
> The Preprocessor.GetSourceLineNumbers doesn't work because the preprocessor
> extension doesn't get the XmlNode. (Or it's hiding somewhere I haven't seen).
Please enter a bug to have it exposed.
--
sig://boB
http://joyofsetup.com/
---
mewhere I haven't seen).
Date: Tue, 31 Aug 2010 05:13:13 -0700 (PDT)
From: Nick Ramirez
Subject: Re: [WiX-users] Preprocessor Extension question
To: wix-users@lists.sourceforge.net
Message-ID: <1283256793610-5482348.p...@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii
Ther
There's a static method called Preprocessor.GetSourceLineNumbers that accepts
an XmlNode object. It's used by WiX as Candle is looking through your
markup. I'm not sure that you'll be able to use it very easily. If you don't
mind my asking, what is it you're trying to achieve? Preprocessor extensi
When writing a preprocessor extension, how can you get
SourceLineNumberCollection inside the extension? It isn't in the base class or
Core that I can find.
- Ed
--
This SF.net Dev2Dev email is sponsored by:
Show
That's what I ended up doing. Just thought it odd that I couldn't ifdef an
environment variable and that I could define a wix variable named the same
as wix pre-processor syntax...
Cheers...
--
View this message in context:
http://n2.nabble.com/Preprocessor-ifdef-environment-variables-tp455599
Could you try a custom preprocessor extension?
- Original Message -
From: "John Nannenga"
To: "General discussion for Windows Installer XML toolset."
Sent: Friday, February 12, 2010 4:10 AM
Subject: [WiX-users] Preprocessor I think
I think this is kind of odd:
Which compiles just fine.
What I want to be able to do is have the preprocessor condition logic based on
whether or not an environment variable is set.
Forexample:
But I cannot use because in the case when
the environ
aillet, Ed [mailto:email...@unum.com]
Sent: Monday, August 31, 2009 9:59 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Preprocessor and Component Guids
Here's the real use case.
I need to create what I'll call an 'Infrastructure Package',
specifically for a web serv
") and use them as your keypaths. If they are all "buried" in the
same key it won't look so "heavy" in RegEdit.
-Original Message-
From: Maillet, Ed [mailto:email...@unum.com]
Sent: Monday, August 31, 2009 8:53 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX
Message: 7
Date: Mon, 31 Aug 2009 16:25:46 +
From: Svet Bonev
Subject: Re: [WiX-users] Preprocessor and Component Guids
No, there is no built-in functionality to accomplish that.
But the bigger question is why you want to create such components.
Ideally, you would have file KeyPaths. Ran
about the use case would help us identify a solution.
-Original Message-
From: Maillet, Ed [mailto:email...@unum.com]
Sent: Monday, August 31, 2009 8:53 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Preprocessor and Component Guids
Hey all,
I hope I'm missing some
Hey all,
I hope I'm missing something obvious. Is there a way for the
preprocessor to generate a guid value for a variable? (without making my
own custom extension).
Something like
I'm trying to create multiple conditional components like:
martin lavelle wrote:
> I can't think why they would object to using Linker variables this way?
>
Who said we would? It's supported and useful, especially in localization.
--
sig://boB
http://joyofsetup.com/
--
Ope
Christopher Painter wrote:
> 1) Incorrect file paths will manifest themselves too late in the process.
>
> 2) When using a different variable like $(env.INSTALLFILES) if the
> directory path is different for different builds the wixlib is already
> formatted and the files won't line up.
>
U
Hi Chris,
You could use Linker Variables in your source paths ( !(wix.Var) Variables )
I've used them this way in the past without problems. The linker still tells
you if it can't find a file, etc. The Compiler (Candle.exe) won't allow linker
variables everywhere, but they did/do work ok in S
I've noticed a couple things I wonder about:
Let say I use:
Source="$(env.WINDIR)\notepad.exe
The wixlib gets formatted as C:\WINDOWS\NOTEPAD.EXE.
If I type the file name wrong, it still compiles with no errors. It's not
until I consume the library in a merge module that it reports a failu
That variable comes from the project system. If you look at the
command-line to candle.exe during the build, you'll see it (and may
other things) passed in as the -D switch.
You've asked a couple basic questions about the preprocessor. Have you
read the WiX.chm documentation?
Hu, Pan wrote:
>
I have the following component in my Product.wxs file for my WiX
project:
My question is, I want to use a preprocessor variable, i.e.
$(var.MyApp.TargetFilePath) for the 'Source' attribute of the 'File'
element above. In Votive 3.0, is var..TargetFilePath a built-
n WiX v2 won't change.
2. The behavior in WiX v3 is more what you would expect... (I think).
-Original Message-
From: Mark Modrall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2008 08:11
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
Sorry, I should have included that in the first place... V2.0.5325.0...
Thanks
Mark
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] preprocessor
Sorry... Should have included that to begin with - v2.0.5325.0
Thanks
Mark
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 6:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] preprocessor and
What version of the WiX toolset are you using?
-Original Message-
From: Mark Modrall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2008 14:38
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] preprocessor and environment variables?
Hi...
I recently ran into a number
Hi...
I recently ran into a number of problems trying to change wix project
behavior based on environment variable settings. A number of the things that
sounded intuitive to me didn't work.
For example
didn't work because ifdef returns false for all environment variables always
w
ehalf Of Scott Palmer
Sent: Friday, June 27, 2008 13:56
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Preprocessor ifdef did odd thing
Attempts to reproduce the problem failed, the problem changed to simply not
recompiling the source file in the new project.. I
d and hit a bug then
> you can get trapped in a difficult position.
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Behalf Of Scott Palmer
> Sent: Wednesday, June 25, 2008 06:21
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-
too far behind and hit a bug then you
can get trapped in a difficult position.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Wednesday, June 25, 2008 06:21
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Preprocessor ifde
I have a product that can be built two ways. I have two WiX installer
projects in visual studio, sharing many of the same wxs files. One project
defines a variable in the project settings to cause some of the .wxs files
to compile differently, like this:
...
AM
To: Quattro IV
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Preprocessor Directives
Where can I find the current list of preprocessor directives? I'm using the
list from this article,
http://msdn2.microsoft.com/en-us/library/aa302186.aspx#wixsetup_topic6 But I'm
gett
Where can I find the current list of preprocessor directives?
I'm using the list from this article,
http://msdn2.microsoft.com/en-us/library/aa302186.aspx#wixsetup_topic6
But I'm getting compilation errors in VS when using the
ProjectAggregator2-3.0.2925.0.msi. Thanks
Where can I find the current list of preprocessor directives? I'm using the
list from this article,
http://msdn2.microsoft.com/en-us/library/aa302186.aspx#wixsetup_topic6 But
I'm getting compilation errors in VS when using the
ProjectAggregator2-3.0.2925.0.msi. Thanks
Example error: Error 1 Unde
Tuesday, November 07, 2006 6:58 AM
To: 'Bob Arnson'; Friedrich, Oliver
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: RE: [WiX-users] preprocessor variable $(var.Build)
The variable $(Configuration) is set by most MSBuild scripts
automatically (C#, VB, VJ#, WiX, etc.). Als
iable.
Hopefully this offers at least some additional information
which may help you determine where you need to look.
Regards,
Richard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich,
OliverSent: Tuesday, November 07, 2006 03:37To:
wix-users@lists.sourceforge.netSubj
then you also get
$(Configuration) defined for you. I’m not sure if $(ConfigurationName) is
defined. If not, it’s a bug.
Justin
From:
Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, November 06, 2006
7:28 PMTo: Friedrich, OliverCc:
wix-users@lists.sourceforge.net; [EMAIL PROT
.
Justin
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 7:28 PM
To: Friedrich, Oliver
Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED]
Subject: Re: [WiX-users] preprocessor variable $(var.Build)
Friedrich, Oliver wrote:
Alright, just found out, where
Friedrich, Oliver wrote:
Alright, just found out, where this variable was set. It is set on the commandline while calling the batch-file to start the compilation of the setup.
The batch-file is called as "Pre-build
event command line" in VS2005. The variable "var.Build" is set
script and passed when compiling the
wxs files to wixobj.
morten
Message: 6
Date: Mon, 6 Nov 2006 14:20:58 +0100
From: "Friedrich, Oliver" <[EMAIL PROTECTED]>
Subject: Re: [WiX-users] preprocessor variable $(var.Build)
To:
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/pl
: wix-users@lists.sourceforge.netSubject: Re:
[WiX-users] preprocessor variable $(var.Build)
Friedrich, Oliver wrote:
No, we did not use Votive V2, just plain wxs-files
that we added to a simple solution, we did not use Votive
V2.Sorry, I'm not understanding. Are you
Friedrich, Oliver wrote:
No, we did not use Votive
V2, just plain wxs-files that we added to a simple solution, we did not
use Votive V2.
Sorry, I'm not understanding. Are you asking how to set the Build
variable using Votive?
--
sig://boB
http://bobs.org
-users] preprocessor variable $(var.Build)
Friedrich, Oliver wrote:
That`s the point, this variable is defined nowhere in the
source.
We
used WiXV2 manually written files added to a blank solution
in vs2005, compiled via batch
on post-build-action
Friedrich, Oliver wrote:
That`s the point, this variable is defined
nowhere in the source.
We used WiXV2 manually written files added to a
blank solution in vs2005, compiled via batch on post-build-action.
The error that raises at compile-time is that
the preprocessor
alk
to my *shiver* Outlook as soon as I get some spare
time...
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 31, 2006 1:52 AMTo: Friedrich,
OliverCc: wix-users@lists.sourceforge.netSubject: Re:
[WiX-users] preprocessor variable $(var.Build)
Friedrich, Ol
Friedrich, Oliver wrote:
One of my
problems now is, that we used the pre-processor
variable “var.Build” in our setup for finding the final sourcepath
of our apps. But votive won`t compile with it used like that:
We need more detail to help. What happens? Do you get an
Again its me,
currently I`m trying to convert our V2 setup to V3
using a votive-project in our solution.
One of my problems now is, that we used the pre-processor
variable “var.Build” in our setup for finding the final sourcepath
of our apps. But votive won`t compile with it used li
58 matches
Mail list logo
