That sounds like the bug I remember. Maybe it hasn't been fixed yet. I have
not been in to the WiX v3 Binder in a long time... focused on finishing WiX v2.
From: Cullen Waters
Sent: Tuesday, February 13, 2007 10:28 AM
To: Rob Mensching; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] ?Bug? in linker
That's not the behavior I'm seeing. I saved the wixlib files, so you can see
the paths that are in there. The wixlib and the file it references are both
built to the same directory, but the wixlib contains the path from the .wxs
source file to the binary reference. Since we build to a 'Target' directory,
that path is invalid when the wixlib is compiled.
From: Rob Mensching
Sent: Tuesday, February 13, 2007 10:26 AM
To: Cullen Waters; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] ?Bug? in linker
No, .wixlibs are designed to be portable. There was actually a bug a long time
ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were
looking for the server CustomAction files in the location we built them on the
build server. That's obviously bad.
What should actually be happening is that files referenced by the .wixlib
should be relative to the location of the .wixlib (wherever that might be).
That way you can move around the .wixlibs and their referenced files together
(the way we used to move sca.wixlib, scasched.dll and scaexec.dll together).
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters
Sent: Tuesday, February 13, 2007 10:05 AM
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] ?Bug? in linker
In my application, we have several wixlibs that we use to wrap functionality
for Custom Actions. Recently, we changed the way we were building these
slightly, and it broke our build.
Previously, we were relying on a particular environment variable to be set, in
order for the build to work. This environment variable was the full path to
the root of our source control tree, and is different on each machine.
We've been moving to Votive, and in doing so, have been removing the dependency
on environment variables from our wix source (so we can build in VS). I
changed the paths of the files to relative paths. Candle compiled the wixobj
file fine, and lit created the wixlib that I expected.
When I try to link an MSI that uses this wixlib, though, I get an error that a
file with a relative path couldn't be found. I went to the directory where the
wixlib was compiled and linked from, and pasted in the path that couldn't be
found. It was there, just as expected.
Eventually, I realized that light seemed to be resolving the path from the
directory where the MSI was linking from, not the directory where the wxs file
for the wixlib resided. This seemed strange, since light has the directory of
the source file.
I think this is a bug, and I think that Lit should be changed to resolve all
relative paths to absolute paths when it builds the wixlib file. What do
others think?
Cullen Waters
SDET
Office Live
+1 425 706 6809
x 66809
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
