Peter Kümmel wrote:
Abdelrazak Younes wrote:
Abdelrazak Younes wrote:
To run it I had to install two libraries: msvcr80.dll and msvcp80.dll.
But then, lyx still complains about missing Entry point:

---------------------------
lyx.exe - Entry Point Not Found
---------------------------
The procedure entry point _decode_pointer could not be located in the
dynamic link library MSVCR80.dll.

Maybe you have in your search PATH the mingw-qt/bin folder
before the msvc-qt/bin. Then it helps to temporary rename
the qt-mingw folder.

I have done that but the error persist. The following explains that a manifest file is _mandatory_ to any MSVC 2005 generated executable or library:

http://msdn2.microsoft.com/en-us/library/ms235591.aspx

It is recommended that a C/C++ application (or library) have its manifest embedded inside the final binary because this ensures proper runtime behavior in most scenarios. Visual Studio by default tries to embed the manifest when building a project from source files; see Manifest Generation in Visual Studio for more details. However if an application is built using nmake, some changes to the existing makefile are necessary. This section demonstrates how to change existing makefiles to automatically embed the manifest inside the final binary.
Two approaches

There are two ways to embed the manifest inside an application or library.

    *

If you are not doing an incremental build you can directly embed the manifest using a command line similar to the following as a post-build step:

      mt.exe –manifest MyApp.exe.manifest -outputresource:MyApp.exe;1

      or

mt.exe –manifest MyLibrary.dll.manifest -outputresource:MyLibrary.dll;2

      (1 for an EXE, 2 for a DLL.)
    *

If you are doing an increment build, directly editing the resource as shown above will disable incremental building and cause a full rebuild; therefore a different approach should be taken:
          o

            Link the binary to generate the MyApp.exe.manifest file.
          o

            Convert the manifest to a resource file.
          o

Re-link (incrementally) to embed the manifest resource into the binary.

Reply via email to