Re: [Zinf-devel] Win32 status

[Kristian G. K. <kr...@cs...>]

On Wed, 2003-03-19 at 07:17, Tim Lesher wrote:
> The win32 port (using VC6) is progressing pretty well against CVS
> head.  One issue I'm running into is the inconsistent use of C++
> standard library namespace resolution (using std::vector vs. just
> using vector and hoping that someplace else in the include tree
> there's a "using namespace std;" line).
> 
> So far I've been choosing to add explicit resolution everywhere.  Any
> opinions on which of the two ways we should adopt?

Currently the accepted practice is to use:
1.   full namespace naming in headers.
2.   using namespace is source files.

I prefer the shorter style without the namespace string vs
std::string when writing code.

Whether we have a single using namespace in config.h or put it in
individual source files does not really make much of difference.   
So far none of the c++ libraries have any namespace name conflicts.
It's pretty unlikely too, but I guess it's better to play it safe.


> Also, I'm fine with removing "standard" libs from the zinf source tree
> (like zlib, zip, ogg, and id3).  I'm thinking about creating a top-level
> "win32libs" directory that the win32 build can access to get
> prcompiled versions of these libs.  I don't want to pollute the zinf
> CVS module with these binaries, since there's no reason a Linux
> developer needs to pull them down every time they do a cvs get, so
> either they'll be a separate CVS module or else they'll just be a file
> release a win32 developer can download and install before trying to
> build.

I like the idea of a separate module or even tarball or both.   The
latest win32 libs available as tarball.  The cvs module for history.


> Finally, the issue of windows installers.  The README.win32 says that
> the installer is InstallShield-based, but the install script that's
> actually checked in is for the Wise installer.  Unfortunately, neither
> of these are freely available.  Any objection to moving to either a
> gratis installer like InnoSetup, or a Free installer like NSIS?

How hard is the conversion process?  Do you think we can build these
with mingw32?


-- 
email:kr...@cs... office:(805)893-4276 http://www.cs.ucsb.edu/~kris