[Paraview] Building on VS 2005

[Mike Jackson]

Sure I can run CPack. I tried running CPack -G ZIP on a windows XP  
machine and I get the error that ZIP cannot be found, which is what I  
thought would happen. I did get the Compressed Tar option to work  
though. My problem now is I am not sure if my customers system will  
have anything that understands the tar.z file. The computer systems  
are locked down extremely tight so I can only count on what comes  
Native with Windows XP SP2. Is there a Zip package that you recommend  
I put on my own system so that I can generate a .zip package?

Thanks for the help.
-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On May 16, 2007, at 8:42 AM, Amy Squillacote wrote:

> Hi Mike,
>
> I don't a whole lot about the install issues with VS2005 either,  
> but I had a conversation with one of my colleagues where I found  
> out that the CMake folks have figured out how to redistribute  
> things built with VS 2005 if it's a release build (and have  
> incorporated this functionality into CPack). For some reason it's  
> different with a debug build, and he's wasn't even sure it was  
> possible. Is it possible for you to use CPack to create an  
> installer executable, and then run the installer on that server?
>
> - Amy
>
> Berk Geveci wrote:
>> Hi Mike,
>>
>> I am not a Windows person but I heard from someone that it is no
>> longer possible to simply distributed the MS runtime libs. It has
>> something to do with manifest files or something.  You have to do
>> something more or install some runtime stuff from Microsoft. I  
>> know my
>> answer is vague :-) I didn't use VS 2005 yet. I am still building  
>> with
>> 2003. You may want to ask it to the cmake mailing list.
>>
>> -berk
>>
>> On 5/14/07, Mike Jackson <imikejackson at gmail.com> wrote:
>>> I recently started using VS 2005 Professional (up from VS 2003 .Net)
>>> and when I compile ParaView (2.4.4) using the "INSTALL" project from
>>> within the VS 2005 solution file everything seems to build and does
>>> get copied to the install location but I noticed that the MS C  
>>> and C++
>>> runtime libs are no longer copied into the intsall location. Is  
>>> this a
>>> bug somewhere? Has anyone else noticed this? I used to be able to
>>> right click on the "INSTALL" project, let it run to completion, then
>>> simply copy the Paraview 2.4.4 folder onto a  server for other  
>>> people
>>> to use. Now I am not sure what else needs to be copied.
>>>
>>> Thanks
>>> -- 
>>> Mike Jackson
>>> imikejackson _at_ gee-mail dot com
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>
>>