RE: problems building feature release on windows

[Kelly F. Hickel]

> -----Original Message-----
> From: bug-cvs-bounces+kfh=mqsoftware.com@nongnu.org [mailto:bug-cvs-
> bounces+kfh=mqsoftware.com@nongnu.org] On Behalf Of Kelly F. Hickel
> Sent: Tuesday, May 02, 2006 8:39 PM
> To: Jim Hyslop
> Cc: bug-cvs@nongnu.org
> Subject: RE: problems building feature release on windows
> 
> Hi Jim,
> 
> > -----Original Message-----
> > From: Jim Hyslop [mailto:jhyslop@dreampossible.ca]
> > Sent: Tuesday, May 02, 2006 8:31 PM
> > To: Kelly F. Hickel
> > Cc: bug-cvs@nongnu.org
> > Subject: Re: problems building feature release on windows
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Kelly F. Hickel wrote:
> > > Hi,
> > >
> > >             I've been trying for the last day or so to build the
> feature
> > > release on windows (so that I can use Rational purify & quantify
to
> look
> > > at some other issue).  I've had no luck at all.  I've tried
1.12.12,
> > > 1.12.13 and the tip of the trunk.  I've used VS .Net 2003 and VS
> .net
> > > 2005.  I've tried cvsnt.mak and cvsnt.dsp.
> > >
> > >
> > >
> > >
> > >
> > > The .dsp/.dsw files won't load into either version of VS .net that
I
> > > have, it reports that the project files are corrupt.
> > >
> > >
> > >
> > > When I use the .mak files, I can get it to build if I add code for
> some
> > > of the wide character stuff (btowc, mbrtowc and wctype) which
don't
> seem
> > > to be supplied.  When I do that the resulting .exe seems to work
but
> > > doesn't actually do anything with any of the files in the
> directories of
> > > the repo.  So, if I do a co, I get all the directories and CVS
> > > directories, but no files.
> > >
> > >
> > >
> > > This stuff must build, right? I can download binaries that work
> fine, so
> > > someone must have built it......
> >
> > That'd be me. I used Visual Studio 6.0 (yes, I know it's old :=)
> >
> > I just refreshed the tip of the trunk, and it builds cleanly with VS
> > 6.0. I don't believe 6.0 is supported by MS any more. It used to
ship
> > with the MSDN (I haven't used MSDN in a year, so I couldn't tell you
> if
> > it's still there - probably not).
> >
> > I don't have a recent version of Visual Studio .NET to test this on.
I
> > have the discs, I just haven't installed it.
> >
> > WRT the corruption reported by visual studio, check the
line-endings.
> I
> > suspect the .dsp and .dsw files may have plain LF endings, rather
than
> > CRLF. I could be wrong, though.
> 
>  [Kelly F. Hickel] That's a good idea to check, I have gotten past
this
> however, at the moment I'm using a .sln file that I made myself.  The
> bigger question for me is how do you get btowc, mbrtowc etc to
resolve?


 [Kelly F. Hickel] Wait a sec, you said the tip of the trunk?  That's
awfully hard to believe. I checked out the tip of the trunk into a clean
workspace and went to the top of the tree and did "nmake /f cvsnt.mak".
There were tons of errors due to code that needed "#ifdef
SERVER_SUPPORT" around it.

Maybe you build some other way????

> 
> 
> 
> >
> > - --
> > Jim Hyslop
> > Dreampossible: Better software. Simply.
> http://www.dreampossible.ca
> >                  Consulting * Mentoring * Training in
> >     C/C++ * OOD * SW Development & Practices * Version Management
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2 (MingW32)
> > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> >
> > iD8DBQFEWAfLLdDyDwyJw+MRAh2mAJ9ZMb29G7r/UvUWfo0+CkiCknbaUwCcCvS2
> > O4BQBZrYS/S/SsleCMW1Cso=
> > =APRW
> > -----END PGP SIGNATURE-----
> 
> [Kelly F. Hickel]
> --Kelly
> 
> 
> _______________________________________________
> Bug-cvs mailing list
> Bug-cvs@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/bug-cvs