Hi Kyle,

What about using the XSLT to change the duplicate <Directory/> elements to
<DirectoryRef/> elements, and define the directory structure once, in
another file?

I do something like this when I first create a setup project--I do not use
HEAT dynamically at build time. I like to have the directory structure laid
out in one place where it's easier to visualize how it will look on the
target system.

-Zach

On Fri, Jan 8, 2010 at 7:08 AM, Kyle Huey <ksh...@ufl.edu> wrote:

> Hello all,
>
> I am using heat to generate the source for two .wixlibs which are lighted
> together with some other pieces to form my final MSI.  Heat is used on two
> different directories at build time.  One of these directories holds all of
> my language specific files "/localized/" and the other holds all of my
> language neutral files "/neutral/".  Creating a setup this way allows me to
> generate the language neutral .wixlib just once for every locale I support.
> The problem is that the directory structure within those directories has
> some (but not complete) overlap.  e.g.
>
> localized
>  foo
>    greeneggs
>  bar
>
> neutral
>  foo
>    ham
>
> becomes on the user's computer
> installdir
>  foo
>    greeneggs
>    ham
>  bar
>
> This gives me a duplicate symbol error at foo when I try to link the two
> wixlibs together.  I can't just throw away the directory fragments from one
> heat run because neither structure is a subset of the other.  I also don't
> want to tell light to suppress the duplicate symbols error (and I don't
> know
> that that will produce a working MSI).  Really the only solution I've come
> up with is to use XSLT to eliminate all of the directory elements from the
> first two runs and then run heat again against the combined result and use
> XSLT on that third run to eliminate all of the non-directory elements.
>
> That seems suboptimal at best.  Anyone have any better ideas?
>
> Thanks,
>
> - Kyle
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to