update

[Ivan R. Judson]

One clarificatin question:

Does this mean someone can attempt to check out winglobus from cvs and build
a working GT2.0 windows globus?

Does it include the accessory python that we've been packaging with
winglobus?

If not, where is that python living?

--Ivan

> -----Original Message-----
> From: Ivan R. Judson [mailto:judson at mcs.anl.gov] 
> Sent: Wednesday, March 12, 2003 10:38 AM
> To: 'Ti Leggett'; 'AG Dev'
> Subject: RE: update
> 
> 
> 
> Ti,
> 
> Good work. I wouldn't worry too much about the one click to 
> build the installer problem.  We'll get there. For now 
> manually building them is fine, as long as it's clear enough 
> for someone to get through it.
> 
> We can poke at the big green build button later :-)
> 
> --Ivan
> 
> > -----Original Message-----
> > From: owner-ag-dev at mcs.anl.gov
> > [mailto:owner-ag-dev at mcs.anl.gov] On Behalf Of Ti Leggett
> > Sent: Wednesday, March 12, 2003 10:22 AM
> > To: AG Dev
> > Subject: Re: update
> > 
> > 
> > Alrighty,
> > 
> > - I fixed the wgpi bailing problem. It was a matter of cvs
> > mangling binary files. I've since added *.exe and *.dll to 
> > the list of files to be added as binary to the cvswrappers 
> > file in CVSROOT.
> > - The installer now creates a registry key that points to a 
> > file and not a directory
> > - The installer postinstall script checks for above file and 
> > creates one if it doesn't exist. This is so the 
> > globus_setup.py doesn't appear to be broken when someone goes 
> > to run it the first time.
> > - Commited my vic project file fixes so that should build fine
> > 
> > TODO
> > I'm trying to come up with an installer prebuild script for
> > both ag and globus that will build all the necessary VC 
> > components so that people shouldn't have to worry too much 
> > about what and in what order things need to be compiled.
> > 
> > I need to work on some other things the rest of the day, but
> > I should be able to jump back on this tomorrow or later on tonight.
> > 
> > On Tue, 2003-03-11 at 21:40, Ti Leggett wrote:
> > > Here's what I got accomplished tonight:
> > > 
> > > WinGlobus is now in cvs. Module name: WinGlobus
> > > It should have all the WinGlobus stuff cleaned and ready to
> > build as
> > > well as the globus setup py files and the iss files. To build
> > > WinGlobus you have to first clean both the threaded and non 
> > threaded
> > > lib solutions, delete all the globus*.lib in /lib. Then you
> > build the
> > > non threaded solution, then you rebuild gssapi. Then you build the
> > > threaded solution.
> > > 
> > > In order to make a windows installer you'll need pyglobus 
> and pydns.
> > > 
> > > NOTE: after rebuilding wgpi now dies horribly so there 
> will be more
> > > debugging tomorrow.
> > > 
> > > I also fixed the generate a certificate certreq.cmd and 
> ssleay.conf
> > > files so they actually work.
> > > 
> > > I also changed everything to use AppDate\globus instead of .globus
> > > 
> > > I also cleaned up the Prebuild.cmd script so it's a bit easier to
> > > change to build installers on others machines.
> > > 
> > > I also added version numbers to the installer exectuable.
> > > 
> > > On the AG side of things.
> > > - I cleaned up and fixed the makeServiceZips.py file
> > > - Cleaned up the Prebuild.cmd and iss files
> > > - Rebuilt ag-rat with VS.NET thanks to Ivan's fixes
> > > - Rebuilt ag-vic with VS.NET thanks to Ivan's fixes and also fixed
> > > some project depenedencies which I haven't commited yet. 
> ag-vic was 
> > > also built without the intel jpeg library though to really 
> > fix we need
> > > to remove some files out of CVS.
> > > - Made it so py files are copied to pyw files and pointed 
> the icons
> > > and shortcuts at those instead
> > > 
> > > I probably did a few other things but can't remember right now.
> > > 
> > > I'm going home.
> > > 
> > 
>