While its not the stupid error you pointed out, it was the result of
another stupid error... I think. I'm still not good with the VS
environment.
It turns out, for whatever reason, I had been specifying msvcrtd.lib as
an additional dependency. My interpretation is that it made the linker
dynamically link to that instead of the correct static library.
Adjusting my additional dependency list looked promising. It caused my
dll to increase in size (seems good) and caused the Dependency Walker to
show the dependency had gone away (also good.)
However, in a throwback to days I thought I had left in my wake, the
installer now bails when trying to access the dll with the handy failed
to execute error... Dependency Walker isn't throwing up any
(noteworthy) red flags this time around, so I might be stuck
experimenting with build settings some more.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 15, 2007 10:12 AM
To: Rowland, Chris; WiX-users@lists.sourceforge.net
Subject: RE: [WiX-users] CustomAction = .VC Runtime Dependency?
Chris,
Just for stupidity's sake, make sure you have changed that setting for
the correct build. I spent almost an hour one morning wondering why
something wasn't linking the way I expected, only to find that I had
made the change in the release settings and was trying to use the debug
build! :-) Boy did I feel stupid when I found that one! Serves me right
for doing a batch build each time and thinking that if the file modified
time was correct I must be using the right file!
Regards,
Richard
P.S. I just looked at the configuration for the custom action we have.
(Visual Studio 2005 - your mileage may vary.) We are apparently using
the "Use Standard Windows Libraries" option instead of the static /
dynamic MFC choices. Dependency walker shows just three direct
dependencies - MSI.dll, USER32.dll and KERNEL32.dll.
P.P.S. I also thought it is worth mentioning that for the purpose of
this exercise you are probably only interested in direct dependencies.
It is perfectly possible that Microsoft may decide to make some of their
libraries dependent on msvcr80.dll, but if you are not using the runtime
directly its use by other parts of the system should be transparent to
your code.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, May 15, 2007 9:48 AM
To: [EMAIL PROTECTED]; WiX-users@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Subject: Re: [WiX-users] CustomAction = .VC Runtime Dependency?
Thanks for the suggestion. It didn't seem to have any effect though.
The size of the dll (and all the other files in the build directory)
stayed the same, and the msvcr80.dll dependency still exists.
________________________________
* C O N F I D E N T I A L I T Y N O T I C E *
-----------------------------------------------------------
The content of this e-mail is intended solely for the use of the
individual or entity to whom it is addressed. If you have received this
communication in error, be aware that forwarding it, copying it, or in
any way disclosing its content to any other person, is strictly
prohibited. Peek Traffic Corporation is neither liable for the contents,
nor for the proper, complete and timely transmission of (the information
contained in) this communication. If you have received this
communication in error, please notify the author by replying to this
e-mail immediately and delete the material from any computer.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
