v8_*_cc.pdb files are missing. How do I get them? - windows

(I am working with Windows 10)
I need to update V8 in a project that uses V8 5.8 to V8 7.9.
In the project with the old library I get these files: v8_*.lib, v8_*_cc.pdb, natives_blob.bin and snapshot_blob.bin
I have managed to build V8 7.9, but I do not get the v8_*_cc.pdb files.
How do I create these files? Thanks!
I followed the proceure described here.
This got me the .bin and .lib files. but not the .pdb files.

Related

Is there a pre-built Bolts.framework for Objective-C available?

We have tried to update our Bolts.framework (to remove UIWebView references) from the GitHub sources and failed. And the one provided on back4app.com is out of date.
Does anyone know if there is an already built Bolts.framework ZIP file posted anywhere with the latest updates?
I spend almost whole day to built this lib, so few steps to build Bolts:
Download latest release https://github.com/BoltsFramework/Bolts-ObjC/releases
After that download xtoolchain from https://github.com/parse-community/xctoolchain-archive
Move files and folders from xtoolschain folder to Bolts/Vendor/xtoolchain
So now you can build Bolts running command sh build_all.sh from Bolts/scripts
In Bolts folder you can found build folder and the framework will be here build/Debug-iphonesimulator/Bolts.framework

How to use Tesseract OCR with Cmake on Windows?

I'm tryint to use tesseract in my cmake project on Windows. I installed tesseract 5.0 and tesseract 4.0. They both come with no cmake folder so the line
find_package(Tesseract REQUIRED)
produces
CMake Error at CMakeLists.txt:14 (find_package):
By not providing "FindTesseract.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"Tesseract", but CMake did not find one.
Could not find a package configuration file provided by "Tesseract"
(requested version 4.0) with any of the following names:
TesseractConfig.cmake
tesseract-config.cmake
Add the installation prefix of "Tesseract" to CMAKE_PREFIX_PATH or set
"Tesseract_DIR" to a directory containing one of the above files. If
"Tesseract" provides a separate development package or SDK, be sure it has
been installed.
However, in the installation folder for tesseract 5.0, there's libtesseract-5.dll and many others. Can I link those in my cmake project? If so, how? And why there are no include files in the installation folder? How am I suppose to include the .h files in my project?
UB-Mannheim installer is autotools build and it has only runtime part of tesseract (e.g. executables and linked libraries).
You can not use it for any development because it does not provide needed files (libraries and header files), so missing cmake files are reasonable consequences of this installation.
You can check this information in detail where installer finished.
Have you tried using the MSYS/Mingw build of tesseract: pacman -S mingw-w64-x86_64-tesseract-ocr? Since there is no cmake config file you will have to use pkg_check_modules instead (see also cMakefile for using tesseract and opencv without the opencv bit)

missing payoffs.hpp and other .hpp from version

When building the Windows C++ version of quantlib 1.9.1, I get this error of missing payoffs.hpp. When I browse to the directories, I see payoffs.cpp, but not payoffs.hpp:
Severity Code Description Project File Line Suppression State
Error C1083 Cannot open include file: 'ql/instruments/payoffs.hpp': No such file or directory FittedBondCurve c:\users\administrator\google drive\quantlib-1.9.1\ql\cashflows\conundrumpricer.hpp 27
I also get this for #include <ql/instruments/swap.hpp> [and possibly others]. I am able to build the windows quantlib library ok. Just not the examples.
I just checked the QuantLib 1.9.1 release available from the project downloads (did you get your version from there?) and the files you're looking for are contained in the release zip and tarball. Also, it's pretty weird that you could compile the library without them, so I'd double check if they're there. If they really aren't—well, hard to know how they got displaced; anyway, you can download the release again and replace them. If that doesn't fix the problem (or if they're already there after all), it's possible that you have to fix the include path for the example you're trying to compile. Does it include the QuantLib directory?

The compilation of Miracl for the DSP C6713 of Texas Instruments

I was trying to compile the Miracl library by using Code Composer Studio V3.1. The target DSP is a C6713 made by texas instruments. I also added to the project the files: csl6713.lib, dsk6713bsl.lib,rts6700.lib and c6713dsk.cmd. The file in C is config.c. The project compiles and runs without problem but the obtained file miracl.lst is empty.
The latest version of MIRACL contains a file texasdsp.txt which has specific advice on building the library for the C6713 DSP, using Code Composer Studio V5. Download from www.certivox.com

qmake gives code 3 when attempting to configure qt for static building

I have the latest Qt SDK. I'm trying to configure it for static building with VS2010 (dynamic linking works fine) I have it at this location: C:\QtSDK\Desktop\Qt\4.8.0\msvc2010
When I go there with the VS2010 command prompt and try to run configure -static, or configure -static I get some output but in the end it fails with
Generating Makefiles...
WARNING: c:\QtSDK\Desktop\Qt\4.8.0\msvc2010\projects.pro:44: Unable to find file
for inclusion src\src.pro
WARNING: c:\QtSDK\Desktop\Qt\4.8.0\msvc2010\projects.pro:46: Unable to find file
for inclusion doc\doc.pri
Reading C:/QtSDK/Desktop/Qt/4.8.0/msvc2010/tools
Reading C:/QtSDK/Desktop/Qt/4.8.0/msvc2010/translations/translations.pro
Reading C:/QtSDK/Desktop/Qt/4.8.0/msvc2010/examples
Reading C:/QtSDK/Desktop/Qt/4.8.0/msvc2010/demos
Qmake failed, return code 3
Please help
I downloaded the source zip file instead of trying to work with what came in the SDK and it's working now. Just download the source from here, unzip it, and run the configure.exe in the unzipped folder. My guess (although I have inspected this) is that there's missing source files or other resources in the SDK version.

Resources