PDA

View Full Version : Merge Module Question



NewsArchive
09-16-1999, 12:00 AM
Hi David,

> >1) How do I make ISWI look at places other than it's Modules directory
for
> >MSM files?
>
> Currently you can not, though we are looking into changing this for a
future
> release.

Is this likely to make it into a future maintenance release, or am I likely
to have to wait longer?

It is fairly crucial to our build scheme. We need to be able to build with
off the shelf tools, with everything else held in our source control system.
To have to modify an installed product, by copying files in this case, in
order to get our products too build is a real pain.

> >2) How do I tell the difference between MFC42.MSM and MFC42U.MSM in the
> >merge module wizard, when they are both called "MFCDLL Shared Library -
> >Retail"?
>
> Currently you can not.

Can you log this as a feature request, please?

> >3) After inserting both MFC42.MSM and MFC42U.MSM into a feature, I see 2
> >instances of the "Microsoft (R) C Runtime Library". When I build with
> >iscmdbld I see 4 separate lines mentioning this DLL. Can I assume that
only
> >one copy of msvcrt.dll has been added to me install image?
>
> What are the lines tht mention this DLL?

My feature shows the following merge module components:

* ATL Module for Windows
* MFCDLL Shared Library - Retail Version
* Microsoft Stock Property Page
* Microsoft (R) C Runtime Library
* MFCDLL Shared Library - Reailt Version
* Microsoft (R) C Runtime Library

I only added 3 merge modules, ATL, MFC42 and MFC42U.

When I build with iscmdbld I see the following snippet of output:

InstallShield table successfully built
Summary information stream
SummaryStream table successfully built
Merging modules...
ATL Module for Windows:C:\Program
Files\InstallShield\InstallShield for Windows Installer\Modules\i386\ATL.MSM
MFCDLL Shared Library - Retail Version:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MFC42.MSM
Microsoft Stock Property Page:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSSTKPRP.MSM
Microsoft (R) C Runtime Library:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSVCRT.MSM
Microsoft Stock Property Page:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSSTKPRP.MSM
Microsoft (R) C Runtime Library:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSVCRT.MSM
MFCDLL Shared Library - Retail Version:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MFC42U.MSM
Microsoft (R) C Runtime Library:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSVCRT.MSM
Microsoft (R) C Runtime Library:C:\Program
Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\MSVCRT.MSM
Modules merged
English (United States)
Property
English (United States): AdminChangeFolder.

Thanks,

Don

NewsArchive
09-17-1999, 12:00 AM
<<..inline..>>



Don Irvine wrote in message <37e124e1.0@news.installshield.com>...
>Hi David,
>
>> >1) How do I make ISWI look at places other than it's Modules directory
>for
>> >MSM files?
>>
>> Currently you can not, though we are looking into changing this for a
>future
>> release.
>
>Is this likely to make it into a future maintenance release, or am I likely
>to have to wait longer?
>
>It is fairly crucial to our build scheme. We need to be able to build with
>off the shelf tools, with everything else held in our source control
system.
>To have to modify an installed product, by copying files in this case, in
>order to get our products too build is a real pain.

[David] I am not sure what the status of this is. I know that this has
been requested by a couple other customers and I do personally believe that
this will be modified. However, I do not think that this will be an MP
modification, I think this is more of a point release feature.


>> >2) How do I tell the difference between MFC42.MSM and MFC42U.MSM in the
>> >merge module wizard, when they are both called "MFCDLL Shared Library -
>> >Retail"?
>>
>> Currently you can not.
>
>Can you log this as a feature request, please?

[David] This has already been entered.

>> >3) After inserting both MFC42.MSM and MFC42U.MSM into a feature, I see 2
>> >instances of the "Microsoft (R) C Runtime Library". When I build with
>> >iscmdbld I see 4 separate lines mentioning this DLL. Can I assume that
>only
>> >one copy of msvcrt.dll has been added to me install image?
>>
>> What are the lines tht mention this DLL?
>
>My feature shows the following merge module components:
>
> * ATL Module for Windows
> * MFCDLL Shared Library - Retail Version
> * Microsoft Stock Property Page
> * Microsoft (R) C Runtime Library
> * MFCDLL Shared Library - Reailt Version
> * Microsoft (R) C Runtime Library
>
>I only added 3 merge modules, ATL, MFC42 and MFC42U.
>
>When I build with iscmdbld I see the following snippet of output:
>
> InstallShield table successfully built
> Summary information stream
> SummaryStream table successfully built
> Merging modules...
> ATL Module for Windows:C:\Program
>Files\InstallShield\InstallShield for Windows
Installer\Modules\i386\ATL.MSM
> MFCDLL Shared Library - Retail Version:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MFC42.MSM
> Microsoft Stock Property Page:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSSTKPRP.MSM
> Microsoft (R) C Runtime Library:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSVCRT.MSM
> Microsoft Stock Property Page:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSSTKPRP.MSM
> Microsoft (R) C Runtime Library:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSVCRT.MSM
> MFCDLL Shared Library - Retail Version:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MFC42U.MSM
> Microsoft (R) C Runtime Library:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSVCRT.MSM
> Microsoft (R) C Runtime Library:C:\Program
>Files\InstallShield\InstallShield for Windows
>Installer\Modules\i386\MSVCRT.MSM
> Modules merged
> English (United States)
> Property
> English (United States): AdminChangeFolder.

[Dave] I need to look into this a little more, I do not have the VSI Merge
Modules to reproduce this yet. I do think that this will not be a problem.
Merging the same module twice should have no effet on the installer since
the collisions caused on Merge are ignored.


--
David Thornley
Lead Developer Support Engineer
InstallShield Software Corporation
http://www.installshield.com

ruppy88
02-13-2002, 11:43 AM
My company creates dlls with the same name for 2 similar products. I wanted to put each into a merge module, but after creating the first merge module for product A, I can not add the same named files to a different merge module for product B without the merge module for Product A being included. If the files were the same, I could create a third merge module and put that in A and B, but they are not. Does anyone have a suggestion on how to get around this?

Thanks

_doog_
02-13-2002, 12:41 PM
i don't get it, please explain it again :)

why create 2 merge-modules for the same dll?

put each dll in a seperate merge-module and modify the required table so that the required merge modules are automatically included when u check it

other possibility: you have 2 DIFFERENT dlls with the same name... i would suggest you rename them

ruppy88
02-13-2002, 01:32 PM
I have 2 DIFFERENT dlls with the same name. Getting the dlls renamed will be a problem as well.