Hello Perhaps Michael will answer you because he is a maintainer of the octave by VC++. Octave 3.0.1 was produced VC++ 2005 express edition and microsoft platform SDK to my knowledge. Now Octave 3.0.3 is uploaded which is built by VC++ 2008 Express Edition with Microsoft SDK. Octave 3.0.1 is obsolete now and no longer maintained any more.
So I think that it is better that you will try again what you carried out with octave 3.0.3 and VC++ 2008. Regards Tatsuro --- Thomas M. Ortiz wrote: > > > > > Hello > > > > I tried to integratethe Octave 3.0.1 distribution created using MSVC 2005 > into my own applicationin order to consume Octave functionality using the C++ > API. I found thatI could not run my program in Debug mode because the > following error wasgenerated: > > > > “Thisapplication has failed to start because MSVCR80.dll was not found. > Re-installing the application may fix this problem.” > > > > Afterexhausting all alternatives known to me, I contacted Microsoft, who > found thesolution to the problem (see below). The DLLs in the Octave > Forgedistribution of v. 3.0.1 all had an RT_MANIFEST ID = 1, which signifies > thatthey are executables; DLL files must be given an ID = 2. When I changed > themby hand-editing the resource files, the problem disappeared. > > > > However, itwould be helpful to have both Debug and Release versions of the > Octavedistribution available for download. > > > > Finally, theMicrosoft engineer was able to discern from looking at the > resource files thatsome of the DLLs in the VS 2005 distribution of Octave > 3.0.1 were actuallycreated using VS 2003. This is dangerous because passing > pointers amongDLLs created using different versions of Visual Studio can > result in memoryaccess violations. All of the Octave DLLs should be built > with the sameVS version. > > > > Thanks fortaking the time to have a look at this. > > > > Tom > > > > > > From: Ravi Avanaganti[mailto:[EMAIL PROTECTED] > Sent: Monday, December 08, 2008 5:24 PM > To: Thomas M. Ortiz > Subject: Case SRX081208601113 : Important Links > > > > Hi Tom, > > > > As discussed, I am sending you the links that talk about theresource ID of > the DLL and exe. > > http://blogs.msdn.com/dsvc/archive/2008/08/07/part-1-troubleshooting-vc-side-by-side-problems.aspx > > > > > CREATEPROCESS_MANIFEST_RESOURCE_ID (1): If an executable hasa resource of > type RT_MANIFEST, ID 1, Windows will create a process defaultactivation > context** for the process. The process default activation contextwill be used > by all components running in the process. > > > > ISOLATIONAWARE_MANIFEST_RESOURCE_ID(2): This is usedprimarily for DLLs. It > should be used if the DLL wants private dependenciesother than the process > default. > > > > Following article is also good, that talks about commonsidebyside errors > > http://blogs.msdn.com/dsvc/archive/2008/08/07/part-2-troubleshooting-vc-side-by-side-problems.aspx > > > > > This link talks about the potential errors that occur whenobjects are passed > across DLLs compiled in different versions of Visual Studio > > http://msdn.microsoft.com/en-us/library/ms235460(VS.80).aspx > > > > I will call you again tomorrow to make sure if everything isworking fine and > see if you have any follow-up questions. > > > > Thanks & Regards > > Ravi A > > -------------------------------------- Power up the Internet with Yahoo! Toolbar. http://pr.mail.yahoo.co.jp/toolbar/ ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
