The .dsp and .dsw files included I obtained as a part of the vorbis source, via CVS, are not recognized by Visual Studio as valid workspace/project files. Should I be getting these files from another place or can someone clue me in on how else to build vorbis on a windows platform? Scott Danahy Programmer VedaLabs - www.vedalabs.com --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
There shouldn't be any .dsw files in the vorbis cvs tree, only .dsp's. They are valid project files, as chad, michael and myself all use them/it. Make sure you're checking it out in binary mode. Also, what version of visual studio do you have? jack. On Tue, 22 Aug 2000, Scott Danahy wrote:> The .dsp and .dsw files included I obtained as a part of the vorbis source, > via CVS, are not recognized by Visual Studio as valid workspace/project > files. Should I be getting these files from another place or can someone > clue me in on how else to build vorbis on a windows platform? > > Scott Danahy > Programmer > VedaLabs - www.vedalabs.com >--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2000-08-22 at 11:53 Scott Danahy wrote:>The .dsp and .dsw files included I obtained as a part of the vorbis >source, via CVS, are not recognized by Visual Studio as valid >workspace/project files. Should I be getting these files from >another place or can someone clue me in on how else to build vorbis >on a windows platform?This is probably caused by bad CR/LF translation of your CVS client. Microsoft VC++ workspace files need to have DOS/Windows line endings, ie { 0x0d, 0x0a } sequences. If any of the files get transferred in "binary mode", it will probably end up with Unix line endings, ie only 0x0d characters, and that will cause MSVC to complain. Try using another CVS client, like WinCVS (which should do the right translation automatically), or manually converting the files to DOS/Windows format (for example, by loading them into EDIT.COM and saving them). Cheers, - -- Dimitry Andric <dimitry@andric.com> PGP key: http://andric.com/dim.asc KeyID: 4096/1024-0x2E2096A3 Fingerprint: 7AB4 62D2 CE35 FC6D 4239 4FCD B05E A30A 2E20 96A3 -----BEGIN PGP SIGNATURE----- Version: Encrypted with PGP Plugin for Calypso Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBOaKktrBeowouIJajEQLDEACcD8We4XsUre+5/clPwPljuUb5U1kAoJdS Ca1BEk/IkD8ZId1eRQh3/WcH =RW9P -----END PGP SIGNATURE----- --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
"Doh". That was it exactly. Thanks so much. Scott Danahy Programmer VedaLabs - www.vedalabs.com -----Original Message----- From: Dimitry Andric [mailto:dimitry@andric.com] Sent: Tuesday, August 22, 2000 12:06 PM To: Scott Danahy Cc: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] Vorbis Beta 2 MSVC Files -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2000-08-22 at 11:53 Scott Danahy wrote:>The .dsp and .dsw files included I obtained as a part of the vorbis >source, via CVS, are not recognized by Visual Studio as valid >workspace/project files. Should I be getting these files from >another place or can someone clue me in on how else to build vorbis >on a windows platform?This is probably caused by bad CR/LF translation of your CVS client. Microsoft VC++ workspace files need to have DOS/Windows line endings, ie { 0x0d, 0x0a } sequences. If any of the files get transferred in "binary mode", it will probably end up with Unix line endings, ie only 0x0d characters, and that will cause MSVC to complain. Try using another CVS client, like WinCVS (which should do the right translation automatically), or manually converting the files to DOS/Windows format (for example, by loading them into EDIT.COM and saving them). Cheers, - -- Dimitry Andric <dimitry@andric.com> PGP key: http://andric.com/dim.asc KeyID: 4096/1024-0x2E2096A3 Fingerprint: 7AB4 62D2 CE35 FC6D 4239 4FCD B05E A30A 2E20 96A3 -----BEGIN PGP SIGNATURE----- Version: Encrypted with PGP Plugin for Calypso Comment: http://www.gn.apc.org/duncan/stoa_cover.htm iQA/AwUBOaKktrBeowouIJajEQLDEACcD8We4XsUre+5/clPwPljuUb5U1kAoJdS Ca1BEk/IkD8ZId1eRQh3/WcH =RW9P -----END PGP SIGNATURE----- --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/
There is indeed a .dsw file in the cvs tree under vorbis/vorbis_vc6/. Scott Danahy Programmer VedaLabs - www.vedalabs.com -----Original Message----- From: Jack Moffitt [mailto:jack@icecast.org] Sent: Tuesday, August 22, 2000 11:58 AM To: 'vorbis-dev@xiph.org' Subject: Re: [vorbis-dev] Vorbis Beta 2 MSVC Files There shouldn't be any .dsw files in the vorbis cvs tree, only .dsp's. They are valid project files, as chad, michael and myself all use them/it. Make sure you're checking it out in binary mode. Also, what version of visual studio do you have? jack. On Tue, 22 Aug 2000, Scott Danahy wrote:> The .dsp and .dsw files included I obtained as a part of the vorbissource,> via CVS, are not recognized by Visual Studio as valid workspace/project > files. Should I be getting these files from another place or can someone > clue me in on how else to build vorbis on a windows platform? > > Scott Danahy > Programmer > VedaLabs - www.vedalabs.com >--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/