Hi, I've started making an Ogg Vorbis SDK, as per IRC topic instructions :) Some questions: Its just targetting MSVC right? Not borland/whatever? Should it install the headers/libraries in the msvc dir (c:\Program Files\Microsoft Visual Studio\VC98\(Include|Lib)), or should it put them in the same directory as the document (c:\Program Files\Ogg Vorbis SDK\(Include|Lib)), and have the sample projects add thoses dirs to the search path? Initally I put them in the msvc dir as this seems more convenient for the programmer (less configuring). But adiabatic reckons I shouldn't, because then the user would need higher privilages to install it. What do you think? <p>Secondly, is CVS meant to build? I got the nightly tarball, and I get these unresolved symbols when building libvorbisfile dynamically: vorbisfile.obj : error LNK2001: unresolved external symbol _vorbis_synthesis_halfrate vorbisfile.obj : error LNK2001: unresolved external symbol _vorbis_synthesis_halfrate_p Should I make this SDK from the last stable release rather than CVS? Thirdly, Where should the DLLs go? %WINDOWS%\system32 ? And finally, if anyone has msvc 7, can you check what the registry key is that says where it is installed, and where the header/libs go relative to that. <p>Thanks. Tim. Argh! 4am - Must sleep before light. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
I can't address the other question, but...> Secondly, is CVS meant to build?Generally speaking, yes. CVS is supposed to be considered "stable" and is actually preferred over the released version in general. If CVS is broken at the moment, though, then it's most likely due to a flurry of commits in preparation for 1.0.1, coming soon. -- Graham Mitchell - computer science teacher, Leander High School "I guess I kinda lost control, because in the middle of the play I ran up and lit the evil puppet villain on fire. No, I didn't. Just kidding. I just said that to help illustrate one of the human emotions, which is freaking out. Another emotion is greed, as when you kill someone for money, or something like that. Another emotion is generosity, as when you pay someone double what he paid for his stupid puppet." -- Deep Thoughts, by Jack Handey --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Personally, I would set up a dir tree with, say, OggVorbis at the top, then ogg, vorbis, vorbis-tools and win32-tools beneath that. Don't place the libs, headers, etc in the MSVC dir. You should use the latest CVS, that is the preferred state of the libs. If the dynamic build fails in that way, you probably only need to add the appropriate function to the '.def' file. These don't always seem to get updated at the same time!! You can place the compiled dlls either in the dir of the app that uses them, or anywhere in the path. The dir structure described above works fine with both VC6 and VC7. John ----- Original Message ----- From: <tim.hutt@btinternet.com> To: <vorbis-dev@xiph.org> Sent: Friday, August 22, 2003 4:05 AM Subject: [vorbis-dev] Ogg Vorbis SDK. <p>> Hi, I've started making an Ogg Vorbis SDK, as per IRC topic instructions :)> > Some questions: > > Its just targetting MSVC right? Not borland/whatever? > > Should it install the headers/libraries in the msvc dir (c:\ProgramFiles\Microsoft Visual Studio\VC98\(Include|Lib)), or should it put them in the same directory as the document (c:\Program Files\Ogg Vorbis SDK\(Include|Lib)), and have the sample projects add thoses dirs to the search path?> > Initally I put them in the msvc dir as this seems more convenient for theprogrammer (less configuring). But adiabatic reckons I shouldn't, because then the user would need higher privilages to install it.> > What do you think? > > > Secondly, is CVS meant to build? I got the nightly tarball, and I getthese unresolved symbols when building libvorbisfile dynamically:> vorbisfile.obj : error LNK2001: unresolved external symbol_vorbis_synthesis_halfrate> vorbisfile.obj : error LNK2001: unresolved external symbol_vorbis_synthesis_halfrate_p> > Should I make this SDK from the last stable release rather than CVS? > > Thirdly, Where should the DLLs go? %WINDOWS%\system32 ? > > And finally, if anyone has msvc 7, can you check what the registry key isthat says where it is installed, and where the header/libs go relative to that.> > > Thanks. > > Tim. > > Argh! 4am - Must sleep before light. > > --- >8 ---- > List archives: http://www.xiph.org/archives/ > Ogg project homepage: http://www.xiph.org/ogg/ > To unsubscribe from this list, send a message to'vorbis-dev-request@xiph.org'> containing only the word 'unsubscribe' in the body. No subject is needed. > Unsubscribe messages sent to the list will be ignored/filtered. ><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Friday 22 August 2003 13:05, tim.hutt@btinternet.com wrote:> Hi, I've started making an Ogg Vorbis SDK, as per IRC topic instructions :) > > Some questions: > > Its just targetting MSVC right? Not borland/whatever?Right. The code is meant to compile under other windows compilers, but we don't have the resources to give full support for all of them, so we chose to support the main/most popular one.> > Should it install the headers/libraries in the msvc dir (c:\Program > Files\Microsoft Visual Studio\VC98\(Include|Lib)), or should it put them in > the same directory as the document (c:\Program Files\Ogg Vorbis > SDK\(Include|Lib)), and have the sample projects add thoses dirs to the > search path?Should definately be in the SDK directory.> > Secondly, is CVS meant to build? I got the nightly tarball, and I get these > unresolved symbols when building libvorbisfile dynamically: vorbisfile.obj > : error LNK2001: unresolved external symbol _vorbis_synthesis_halfrate > vorbisfile.obj : error LNK2001: unresolved external symbol > _vorbis_synthesis_halfrate_pThis is probably a missing export from the vorbis.def file - that file has to list all the symbols that are exported from the library. Changes will probably also be needed to vorbisfile.def and maybe ogg.def. This sort of thing is precisely why we need someone with the tools and some knowledge of windows programming to do the SDK stuff - all of this sort of thing is win32-specific.> > Should I make this SDK from the last stable release rather than CVS?No. The whole point of this is to update the SDK ready for the next release.> > Thirdly, Where should the DLLs go? %WINDOWS%\system32 ?They shouldn't get automatically installed anywhere outside the SDK directory. <p>Mike --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.