So, I downloaded boost_1_53_0, and ran bjam. After linking the "libraries" and the "includes" as per the preamble, I ran my Visual C++ solution and i get the following error
LINK : fatal error LNK1104: cannot open file 'boost_python-vc100-mt-gd-1_53.lib'
I read some solutions about executing bjam --build-type=complete --toolset=gcc stage, but it seems my command prompt cannot recognize bjam, even though I added the PATH to the system variables as,
Variable name: bjam
Variable Value: D:\boost_1_53_0\
But I still cannot get bjam running in command prompt! Thanks
Related
I have followed esp-idf guideline to install and test to build the hello world and blink sample code but both the code met this problem.
Visual studio try to build hello world
> Executing task: ninja <
ninja: error: loading 'build.ninja': The system cannot find the file specified.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command ninja " terminated with exit code: 1.
I have tested all the ways I can find to fix it but I'm not sure anything I missed or not.
This is one of the way that I test but also met some problem.
cmd try to run the command below
C:\Espressif\frameworks\esp-idf-v4.4>python -m pip install --user -r %IDF_PATH%/requirements.txt
ERROR: Can not perform a '--user' install. User site-packages are not visible in this virtualenv.
This possible problem is the python environment is exist so I cannot do this command, but I try many ways to disabled or deactivated it still cannot.
python path
system environment
After trying to debug this for a long time, I made a backup copy of the entire project folder, then just went hog-wild deleting files. I deleted almost every file I didn't author. Only left the main/CMakeLists.txt, main/component.mk, main/main.c, main/main.h, .gitignore, CMakeLists.txt, and Makefile. Then I ran idf.py set-target esp32 and idf.py -p /dev/ttyACM0 flash monitor and it worked fine again.
VS Code & ESP-IDF on Ubuntu 20.04.05 LTS
Check if the compiler is properly selected. If you don't select a proper c/c++ compiler, then you might get this error. I had mingw in my system, but vs code did not auto detect the compiler. Then I manually added mingw and selected it for compilation after which this issue was resolved.
What worked for me after updating to the new stable release (v5.0) was
Go to the folder S:\esp\esp-idf\esp-idf-v5.0
Run command prompt at this directory and execute install.bat and later export.bat
After trying to build the program in VSCode the error "ninja: error: loading 'build.ninja'" shows up.
Update the path in the ESP-IDF extension in VSCode using ESP-IDF:Configure Paths
locate your project folder e.g. "V:\simpleTest_using_EspIDF_v5_0"
Open command prompt and execute: idf.py build
Now it builds also in VSCode using the Espressif IDF extension.
You not have a build.ninja file. Find this file on proje
The error
(Qt6Widgets.dll: cannot open shared object file: No such file or directory)
seems to appear when I manually try to compile the .exe in the cmakebuild directory.
When I try to compile in Clion I get this error:
Process finished with exit code -1073741515
(0xC0000135)
I check the installation folder for Qt and the Qt6Widgets.dll exists.
I also try to compile in another computer and it works, I also install all the applications that i needed Qt and Clion and that doesn't change anything. (I'm on Windows 10)
I just entirely reload the project and copy paste everything in the new project and it worked.
I had to choose the Console compilation when creating the project, i don't know if there were other options.
Having built GammaRay from source code on Windows 10, I'm receiving these system errors while trying to run the gammaray.exe binary at C:\Program Files (x86)\GammaRay\bin:
gammaray.exe - System Error: The code execution cannot proceed because Qt5Widgetsd.dll was not found. Reinstalling the program my fix this problem
The error is also thrown for Qt5Cored.dll and Qt5Guid.dll.
Using Visual Studio 2017 Developer Command Prompt, inspired by repository Install.txt, I ran these commands inside the downloaded repository directory:
mkdir build
cd build
set Qt5Core_DIR=C:\Qt\Qt5.12.6\5.12.6\msvc2017_64\lib\cmake\Qt5Core
echo %Qt5Core_DIR%
set Qt5_DIR=C:\Qt\Qt5.12.6\5.12.6\msvc2017_64\lib\cmake\Qt5
echo %Qt5_DIR%
cmake -G "NMake Makefiles" ..
dir
nmake
nmake install
The last nmake install command needs administrative privileges.
Side Notes
I ran into such an issue while building, which is resolved by moving the repository directory to a shorter path like C:\GammaRay\ and building from there.
I have to set Qt5Core_DIR and Qt5_DIR variables due to some CMake complaints similar to this one.
By #Tsyvarev help, the error got resolved by adding C:\Qt\Qt5.12.6\5.12.6\msvc2017_64\bin to path environment variable:
I am trying to compile the Boost library for Windows (as a prerequisite for building the Bitcoin client), using the MinGW compiler toolchain to do so (rather than Visual Studio) and running into errors.
Following various guides online, I have a working bjam application, and the boost_1_55_0 source files. I have tried in the windows shell doing:
path/to/bjam.exe toolset=gcc --build-type=complete stage (the instructions that Bitcoin provides), but get mingw.jam: No such file or directory errors
bootstrap mingw from a standard DOS shell runs successfully, but the .\b2 after emits a bunch of 'cl' is not recognized as an internal or external command, operable program or batch file errors, implying it's not really set up to use gcc/mingw, since it's calling for the Microsoft compiler.
bootstrap.sh --with-toolset=mingw from the MSYS prompt (as suggested here, which creates a log file that doesn't have as many errors, but running ./b2 after leads to a mingw.jam no such file error, and mingw.init unknown error.
Downloading the compiled binaries from http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0/ (boost_1_55_0-msvc-12.0-64.exe). After extracting and referring to the lib and header files, compiling the final executable throws a whole bunch of undefined reference to 'boost::system::generic_category()' for various boost features, implying to me the library files aren't actually containing the proper definitions? Is that because they're Visual Studio libraries?
Downloading the archives from http://www.boost.org/users/history/version_1_55_0.html (boost_1_55_0.7z), which the documentation implies comes with a pre-compiled lib dir, but does not in fact.
So, I'm banging my head on several walls at once. Can anyone help me get past any of these roadblocks?
I used the following steps to successfully build boost version 1.54 in a MinGW/MSYS environment:
Build bjam.exe and b2.exe:
boost_1_54_0\tools\build\v2\engine>build.bat mingw
Copy build tools to the root-directory:
cp boost_1_54_0\tools\build\v2\engine\bin.ntx86\*.exe boost_1_54_0
Run bjam.exe:
bjam --toolset=gcc --build -type=complete install > boost_build.log
I used this process with slight variations for various boost versions, so its a good guess it will work for 1.55 too
I got windows 7 x64, was dl'ing the windows 7 .net 4 sdk when I figured out how to build the bjam.exe file after failing to fulfill these instructions
http://wiki.codeblocks.org/index.php?title=BoostWindowsQuickRef#Set_up_a_Code::Blocks_global_variable_for_Boost
but when I run bjam, I still get a failure.
these are the steps I did
had to add
f:\codeblocks\mingw\bin
to path
THEN open command prompt as administrator (not before path)
then run from boost_1_51_0\tools\build\v2\engine\build.bat
then I could do
bjam --toolset=gcc "--prefix=<installpath>" install
but I get this message when I do
F:\libraries\boost_1_51_0>bjam --toolset=gcc "--prefix=f:\codeblocks" install --
build-type=complete
warning: mismatched versions of Boost.Build engine and core
warning: Boost.Build engine (bjam) is 03.1.18
warning: Boost.Build core (at F:/libraries/boost_1_51_0/tools/build/v2) is 2011.
12-svn
F:/libraries/boost_1_51_0/tools/build/v2/util\path.jam:476: in path.makedirs
rule MAKEDIR unknown in module path.
F:/libraries/boost_1_51_0/tools/build/v2/build\configure.jam:190: in configure.s
et-log-file
F:/libraries/boost_1_51_0/tools/build/v2\build-system.jam:725: in load
F:\libraries\boost_1_51_0\tools\build\v2/kernel\modules.jam:283: in import
F:\libraries\boost_1_51_0\tools\build\v2\kernel\bootstrap.jam:142: in boost-buil
d
F:\libraries\boost_1_51_0\boost-build.jam:17: in module scope
almost looks like linux path's are getting scrambled into the mix
I figured it out.
I redownloaded the bjam that was in the instructions, dumped it to the f:\libraries\bjam folder I had initially setup.
set path=f:\libraries\bjam yadad;%PATH$ whatever command
cd to boost_1_51_0 dir
reran build command
to actually get something to build
I had to add this to other linker options
or , you have to add "$(#boost.lib)\libboost_system-mgw44.lib" into "Other linker options".
source
http://forums.codeblocks.org/index.php?topic=11908.5;wap2