Menu
▾
▴
Re: [Oreka-devel] status of the 0.6 release
|
From: cppjavaperl <cpp...@ya...> - 2006-12-14 00:21:26
|
--- Henri Herscher <he...@or...> wrote: > Cppjavaperl, > > This is good to hear, we might have new projects files checked in in > pretty > soon ! > However, we are using the same version of ACE between 0.5 and 0.6. > > I suspect it's got to do with MSVC not being able to properly link > libraries > that have been compiled with different versions of the platform. I > would > suggest you try to compile ACE on your platform and attempt to link > orkaudio > again. > > Please let us know how you manage. > > Henri OK, well I seem to have the latest repos code working now. I had to basically recompile all of the dependencies with Visual C++ 2005 Express. This was rather time consuming (lots of project file revisions, missing library dependencies, having to upgrade to xerces-c version 2.7.0, etc). The only thing that is different now is that the audio recordings are not being saved as .WAV files (like they were with the binary version of oreka I downloaded before). I am using the same config file. I've edited the config file to store the files as .WAV, but they all show up as .MCF. If I run "OrkAudio.exe debug" and watch the messages, it even shows a filename with a .WAV extension, but the .MCF file is the only one that ever shows up. Any ideas on what could cause this? cppjavaperl > > -----Original Message----- > From: cppjavaperl [mailto:cpp...@ya...] > Sent: 12 December 2006 15:00 > To: Ore...@li... > Subject: RE: [Oreka-devel] status of the 0.6 release > > > --- Henri Herscher <he...@or...> wrote: > > > Hi, > > > > Yes, we should have a 0.6 release probably early in january. I > would > > be interested in knowing why the projects would not convert to > MSVC++ > > 2003 or > > 2005. Did you get any specific error ? It would actually be good to > > > have project files for those. > > I tried it again with VC++ 2005 (the express edition--the free > version). > When trying to load the OrkAudio.dsw file, it asked me if I want to > convert > Generator.dsp, I said yes, and then it said "cannot load the project > due to > a corrupt project file". When I continued, it pretty much said that > all of > the .dsp files were corrupt. > > So now I did some more Google searches and I discovered what was > causing > that problem. I downloaded the latest trunk source from the > Suberversion > repository (OK, the first time I used CVS, but that is of no > consequence > now) in a cygwin bash session. That left my *.dsw and *.dsp files > with > unix-style line endings (no carriage return characters). Microsoft > Visual > C++ doesn't like that, and thinks the file is corrupt (yea Microsoft > -- > that's some robust software you have there!). Anyway, I ran unix2dos > on all > those files, and then the project files converted fine. > > However, I suspect that the oreka-0.5-313-cxx-win32-dependencies.zip > file is not up-to-date enough for the latest trunk version of the > code. > I am able to get the OrkBase project files to compile, but when it > links I > get the following unresolved external error messages: > > OrkBase error LNK2019: unresolved external symbol > "__declspec(dllimport) public: virtual __thiscall ACE_Task<class > ACE_NULL_SYNCH>::~ACE_Task<class ACE_NULL_SYNCH>(void)" > (__imp_??1?$ACE_Task@VACE_NULL_SYNCH@@@@UAE@XZ) referenced in > function > $L119194 > OrkBase error LNK2019: unresolved external symbol > "__declspec(dllimport) public: __thiscall ACE_Task<class > ACE_NULL_SYNCH>::ACE_Task<class ACE_NULL_SYNCH>(class > ACE_Thread_Manager > *,class ACE_Message_Queue<class ACE_NULL_SYNCH> *)" > (__imp_??0?$ACE_Task@VACE_NULL_SYNCH@@@@QAE@PAVACE_Thread_Manager@@PAV?$ACE_ > Message_Queue@VACE_NULL_SYNCH@@@@@Z) > referenced in function "public: __thiscall ACE_Svc_Handler<class > ACE_SOCK_Stream,class ACE_NULL_SYNCH>::ACE_Svc_Handler<class > ACE_SOCK_Stream,class ACE_NULL_SYNCH>(class ACE_Thread_Manager > *,class > ACE_Message_Queue<class ACE_NULL_SYNCH> *,class ACE_Reactor *)" > (??0?$ACE_Svc_Handler@VACE_SOCK_Stream@@VACE_NULL_SYNCH@@@@QAE@PAVACE_Thread > _Manager@@PAV?$ACE_Message_Queue@VACE_NULL_SYNCH@@@@PAVACE_Reactor@@@Z) > > C:\devext\ace_wrappers\lib *is* in the projects additional libraries > settings, and I did extract the dependencies to c:\devext, so that > isn't the > problem. I suspect that you have updated ACE since the > 0.5-313 release. Is that suspicion correct, or am I missing > something else. > > cppjavaperl > > > > > Cheers > > Henri > > > > -----Original Message----- > > From: ore...@li... > > [mailto:ore...@li...] On Behalf Of > > cppjavaperl > > Sent: 12 December 2006 01:33 > > To: ore...@li... > > Subject: [Oreka-devel] status of the 0.6 release > > > > I was just wondering if there might be a 0.6 release in the near > > future. I am interested in trying out the GSM RTP payload type > > support on Windows, but I don't have a copy of Visual C++ 6.0 to > > compile the source from CVS. > > I > > tried converting the project files from both VC++ > > 2003 and VC++ 2005, but I couldn't get them to convert. > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT Join > > SourceForge.net's Techsay panel and you'll get the chance to share > > your opinions on IT & business topics through brief surveys - and > earn > > cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Oreka-devel mailing list > > Ore...@li... > > https://lists.sourceforge.net/lists/listinfo/oreka-devel > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com |