Win32 status
Tim Lesher <[email protected]>
| Newsgroups | gmane.comp.audio.zinf.devel |
|---|---|
| Message-ID | <[email protected]> |
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? 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. 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? -- Tim Lesher <[email protected]> http://www.lesher.ws ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en