[Paraview] Plugins in Windows 3.6.2 binary

Dave Partyka dave.partyka at kitware.com
Thu Jan 7 10:44:38 EST 2010


Hi all, disabling the manifest for the plugins worked! Thanks all for
pointing this out to me! Now the plugins use the runtime that we bundle with
ParaView and you will not need to install the redist package. I will update
the binaries and source downloads asap.

Thanks again!

On Wed, Jan 6, 2010 at 9:07 PM, Marcus D. Hanwell <
marcus.hanwell at kitware.com> wrote:

> Hit send a second too soon, it should be,
>
> if (MSVC)
>   # Do not generate manifests for the plugins - caused issues loading
> plugins
>   set(CMAKE_MODULE_LINKER_FLAGS "${CMAKE_MODULE_LINKER_FLAGS}
> /MANIFEST:NO")
> endif(MSVC)
>
> In order to append to the module linker flags.
>
> On Wed, Jan 6, 2010 at 9:05 PM, Marcus D. Hanwell <
> marcus.hanwell at kitware.com> wrote:
>
>> Something like,
>>
>> if (MSVC)
>>   # Do not generate manifests for the plugins - caused issues loading
>> plugins
>>   set(CMAKE_MODULE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} /MANIFEST:NO")
>> endif(MSVC)
>>
>> That was enough to fix the majority of the problems we saw with Qt plugins
>> on Windows.
>>
>> Marcus
>>
>> On Wed, Jan 6, 2010 at 9:00 PM, Mike Jackson <mike.jackson at bluequartz.net
>> > wrote:
>>
>>> For those of us following along at home. just what would that line in
>>> the CMake file be?
>>> _________________________________________________________
>>> Mike Jackson                  mike.jackson at bluequartz.net
>>>
>>> On Wed, Jan 6, 2010 at 6:16 PM, Marcus D. Hanwell
>>> <marcus.hanwell at kitware.com> wrote:
>>> > I did this in the past and it seemed to work well. You can add a line
>>> to the
>>> > CMakeLists file to instruct CMake not to do this.
>>> >
>>> > On Wednesday 06 January 2010 18:06:01 Dave Partyka wrote:
>>> >> So you're saying that if I don't embed any manifest (which the IDE
>>> does by
>>> >> default) into the plugins it should just work?
>>> >>
>>> >> On Wed, Jan 6, 2010 at 6:02 PM, Clinton Stimpson
>>> > <clinton at elemtech.com>wrote:
>>> >> > Can you fix that issue some people might have by not embedding the
>>> >> > manifests
>>> >> > into the plugin dlls, where embedding them is the default behavior?
>>> >> >
>>> >> > Clint
>>> >> >
>>> >> > On Wednesday 06 January 2010 03:58:54 pm Dave Partyka wrote:
>>> >> > > Hi All,
>>> >> > >
>>> >> > > I have tracked down the issue. That being an inconspicuous Visual
>>> >> > > Studio Security update
>>> >> > > (KB971092<
>>> >> >
>>> >> > http://www.microsoft.com/downloads/info.aspx?na=49&p=1&SrcDisplay
>>> >> >
>>> >> >
>>> >Lang=en&SrcCategoryId=&SrcFamilyId=294de390-3c94-49fb-a014-9a38580e64cb&
>>> >> > >u=ht tp%3a%2f%2fsupport.microsoft.com%2f%3fkbid%3d971092> ) that
>>> was
>>> >> > > installed sometime after I did the 3.6.1 release. Binaries built
>>> with
>>> >> > > that patch applied appear to not run on older revisions of XP
>>> (SP2).
>>> >> > > Thus, I have uninstalled the update, rebuilt ParaView 3.6.2 and
>>> >> > > uploaded the
>>> >> >
>>> >> > regenerated
>>> >> >
>>> >> > > binary to the download server. I have verified that it does work
>>> on a
>>> >> >
>>> >> > clean
>>> >> >
>>> >> > > SP2 machine BUT you must either install the Visual Studio runtime
>>> >> > > redistributable (simple)
>>> >> >
>>> >> >
>>> http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4A
>>> >> >B7
>>> >> >
>>> >> > >-A40D-3802B2AF5FC2&displaylang=en
>>> >> > >
>>> >> > > OR copy the runtime dlls (Microsoft.VC90.CRT.manifest, msvcm90.dll
>>> >> > > msvcp90.dll msvcr90.dll) distributed with ParaView into each
>>> plugin's
>>> >> > > folder (ugly) in order to get plugins to work.
>>> >> > >
>>> >> > > Any one using an up-to-date Windows XP or newer (Vista,7) should
>>> be
>>> >> > > able to disregard these directions.
>>> >> > >
>>> >> > >
>>> >> > > Please report and further issues relating to this and thank you
>>> for the
>>> >> > > feedback!
>>> >> > >
>>> >> > > On Wed, Jan 6, 2010 at 9:31 AM, Robert Maynard
>>> >> >
>>> >> > <robertjmaynard at gmail.com>wrote:
>>> >> > > >  When you profile ParaView does the main executable and plugins
>>> load
>>> >> >
>>> >> > the
>>> >> >
>>> >> > > > same MSVC dlls. ( F9 shows full paths of loaded dlls ).
>>> >> > > >
>>> >> > > > If they don't load the same dlls, comparing the manifest files
>>> will
>>> >> > > > determine if the problem is two different versions of the MSVC
>>> are
>>> >> >
>>> >> > being
>>> >> >
>>> >> > > > used.
>>> >> > > >
>>> >> > > >
>>> >> > > > Moreland, Kenneth wrote:
>>> >> > > >
>>> >> > > > Um, sure.  What specifically would you like me to report?
>>> >> > > >
>>> >> > > > -Ken
>>> >> > > >
>>> >> > > >
>>> >> > > > On 1/5/10 4:46 PM, "Robert Maynard" <RobertJMaynard at gmail.com>
>>> wrote:
>>> >> > > >
>>> >> > > >  Would you be able to run dependency walker, and report back the
>>> >> >
>>> >> > results?
>>> >> >
>>> >> > > > On Tue, Jan 5, 2010 at 6:06 PM, Moreland, Kenneth <
>>> kmorel at sandia.gov>
>>> >> > > > wrote:
>>> >> > > >
>>> >> > > > I tried adding the runtime redistributable.  The plugins now
>>> load
>>> >> >
>>> >> > without
>>> >> >
>>> >> > > > complaint, but they do not work.  The SLAC tools plugin does not
>>> >> > > > create
>>> >> >
>>> >> > a
>>> >> >
>>> >> > > > toolbar like it is supposed to.  The point sprite plugin does
>>> not
>>> >> >
>>> >> > create
>>> >> >
>>> >> > > > the “Point Sprite” representation to the representation combo
>>> box.
>>> >> > > > The VisIt reader plugin allows you to open .silo files, but they
>>> >> > > > always end up with empty data.
>>> >> > > >
>>> >> > > > Does anyone have an idea why that is?  Could it be using two
>>> >> > > > different sets of MSVC libraries?
>>> >> > > >
>>> >> > > > -Ken
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > > On 1/5/10 3:11 PM, "Dave Partyka" <dave.partyka at kitware.com <
>>> >> > > > http://dave.partyka@kitware.com> > wrote:
>>> >> > > >
>>> >> > > >  The best you can probably do if you're stuck at SP2 is install
>>> the
>>> >> > > > runtime redistributable.
>>> >> >
>>> >> >
>>> http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4A
>>> >> >
>>> >> > > >B7-A40D-3802B2AF5FC2&displaylang=en
>>> >> > > >
>>> >> > > > On Tue, Jan 5, 2010 at 5:08 PM, Moreland, Kenneth <
>>> kmorel at sandia.gov
>>> >> > > > < http://kmorel@sandia.gov> > wrote:
>>> >> > > >
>>> >> > > > Given that, is there some advice you can give for installing the
>>> MSVC
>>> >> > > > classes on Windows XP stuck at SP 2?  How do you do that
>>> (without
>>> >> > > > installing the entire compiler)?
>>> >> > > >
>>> >> > > > -Ken
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > > On 1/5/10 1:45 PM, "Utkarsh Ayachit" <
>>> utkarsh.ayachit at kitware.com <
>>> >> > > > http://utkarsh.ayachit@kitware.com>  <http://utkarsh.ayachit@
>>> >> >
>>> >> > kitware.com>
>>> >> >
>>> >> > > > > wrote:
>>> >> > > >  > Another option would
>>> >> > > > >
>>> >> > > > > be for ParaView to do a silent install of the MSVC redist
>>> package
>>> >> > > > > instead
>>> >> > > >
>>> >> > > > of
>>> >> > > >
>>> >> > > > > dumping the dll's/
>>> >> > > >
>>> >> > > > Actually that might not be a bad idea. We can even make it a
>>> option
>>> >> > > > that the user can uncheck, if he wants. Maybe we should look
>>> into
>>> >> > > > that for 3.8.
>>> >> > > >
>>> >> > > > Utkarsh
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >    ****      Kenneth Moreland
>>> >> > > >     ***      Sandia National Laboratories
>>> >> > > > ***********
>>> >> > > > *** *** ***  email: kmorel at sandia.gov <http://kmorel@sandia.gov>
>>>  <
>>> >> > > > http://kmorel@sandia.gov>
>>> >> > > > **  ***  **  phone: (505) 844-8919
>>> >> > > >     ***      web:
>>> >> > > > http://www.cs.unm.edu/~kmorel<http://www.cs.unm.edu/%7Ekmorel><
>>> >> > > > http://www.cs.unm.edu/%7Ekmorel>
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >    ****      Kenneth Moreland
>>> >> > > >     ***      Sandia National Laboratories
>>> >> > > > ***********
>>> >> > > > *** *** ***  email: kmorel at sandia.gov <http://kmorel@sandia.gov
>>> >
>>> >> > > > **  ***  **  phone: (505) 844-8919
>>> >> > > >     ***      web:
>>> >> > > > http://www.cs.unm.edu/~kmorel<http://www.cs.unm.edu/%7Ekmorel><
>>> >> > > > http://www.cs.unm.edu/%7Ekmorel>
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >
>>> >> > > >    ****      Kenneth Moreland
>>> >> > > >     ***      Sandia National Laboratories
>>> >> > > > ***********
>>> >> > > > *** *** ***  email: kmorel at sandia.gov
>>> >> > > > **  ***  **  phone: (505) 844-8919
>>> >> > > >     ***      web:
>>> >> > > > http://www.cs.unm.edu/~kmorel<http://www.cs.unm.edu/%7Ekmorel>
>>> >> > > >
>>> >> > > >
>>> >> > > > _______________________________________________
>>> >> > > > Powered by www.kitware.com
>>> >> > > >
>>> >> > > > Visit other Kitware open-source projects at
>>> >> > > > http://www.kitware.com/opensource/opensource.html
>>> >> > > >
>>> >> > > > Please keep messages on-topic and check the ParaView Wiki at:
>>> >> > > > http://paraview.org/Wiki/ParaView
>>> >> > > >
>>> >> > > > Follow this link to subscribe/unsubscribe:
>>> >> > > > http://www.paraview.org/mailman/listinfo/paraview
>>> >>
>>> >
>>> > --
>>> > Marcus D. Hanwell, Ph.D.
>>> > R&D Engineer, Kitware Inc.
>>> > (518) 881-4937
>>> > _______________________________________________
>>> > Powered by www.kitware.com
>>> >
>>> > Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>> >
>>> > Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>> >
>>> > Follow this link to subscribe/unsubscribe:
>>> > http://www.paraview.org/mailman/listinfo/paraview
>>> >
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>
>>
>>
>> --
>> Marcus D. Hanwell, Ph.D.
>> R&D Engineer, Kitware Inc.
>> (518) 881-4937
>>
>
>
>
> --
> Marcus D. Hanwell, Ph.D.
> R&D Engineer, Kitware Inc.
> (518) 881-4937
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100107/00116954/attachment-0001.htm>


More information about the ParaView mailing list