I have already installed Boost.Python. There were no erros during instalation, but I have a problem. When I try to build my project ererything is OK, but when I run my wrapped project there is an error:
import wrraped_project
ImportError: libboost_python.so.1.41.0: cannot open shared object file: No such file or directory
I tried to copy the project to libboost_python.so.1.41.0 also the lib to the project etc. But every time I have the sme error.
Check if the boost library files are in LD_LIBRARY_PATH.
If that doesn't help, check if the filename is correct, and create a symlink if different.
Can you give us the relevant content of your /usr/lib directory? I'm assuming you're on Linux, right? And did you install Boost.Python with a package manager?
Related
I need to change some configuration information to use SpringToolSuite4. But when I downloaded SpringToolSuite4 4.1.2 and unziped, there isn't SpringToolSuite4.ini file. So I created one, but SpringToolSuite4 didn't reference to SpringToolSuite4.ini file when starting.
I solved the problem with these steps:
Open the commad terminal;
go to the location where you put the jar file;
Run "java -jar [****.jar]";
PS: Make sure you have java runtime installed in you machine and you have the correct environment settings.
Hope this could help you.
I guess this is an admin rights problem:
I have downloaded the self extracting .jar file:
spring-tool-suite-4-4.8.1.RELEASE-e4.17.0-win32.win32.x86_64.self-extracting.jar
I saved it in c:\Program Files (needs admin rights).
Double-clicked it (not as admin) -> Same error (cannot find the SpringToolSuite4.ini file).
I have started TotalCommander (you may use a differnt explorer) with admin rights -> Problem fixed.
Open jar with winrar. Open the "contents.zip". Move to "sts-4.8.0.RELEASE" folder in documents. After, we run the program.
jar:spring-tool-suite-4-4.8.0.RELEASE-e4.17.0-win32.win32.x86_64.self-extracting
You can solve the problem like this.
When I downloaded it for the second time. I also got this error(SpringToolSuite4.ini). That's how I passed. instead of downloading it again. Downloading it again didn't work.
right click on the sts icon inside the extracted sts-bundle package and select show content.
I've downloaded the sources for kdesvn from the github repo as I'm thinking to look into working on an addition to the project. Now turns out, I'm not even able to properly compile the downloaded sources: I've created a directory kdesvn-build changed into it and launched cmake ../ (as described on https://github.com/KDE/kdesvn/blob/master/INSTALL-cmake) which does some stuff but then stops saying:
CMake Error: The following variables are used in this project, but
they are set to NOTFOUND. Please set them or make sure they are set
and tested correctly in the CMake files: SUBVERSION_INCLUDE_DIR
Now, I don't know what SUBVERSION_INCLUDE_DIR should be set to nor could I find it searching around the web. Anyone?
It is a directory containing svn_*.h files. If you are on Linux, you'd need to install something like subversion-dev package. On FreeBSD headers are installed with main package, and the directory is /usr/local/include/subversion-1/.
I'm experiencing this issue on a brand new Sierra setup, with Xcode 8.1.
I have a framework target for iOS, the target builds fine, but when I try to build for test the build fails with this error:
Opening import file for module 'XCTest': Not a directory
I looked at these questions already, but their suggestions are not useful for us:
Opening import file for module 'Swift': Not a directory
<unknown>:0: error: Opening import file for module 'Swift': Not a directory
All the settings in the project are pretty standard.
The cause of this issue was quite bizarre.
It was happening in a CI box on which I had installed Xcode 8.1 via the MAS. In our company we provision CI boxes using xcode-install, but for some reason that I don't remember I wasn't able to do so on this one.
To mimic xcode-install's behaviour I renamed Xcode.app into Xcode-8.1.app, and created an alias of it called Xcode.app.
This is where the issue was. The alias I created wasn't a proper symbolic link. Xcode.app wasn't actually a folder.
I realised this when trying to perform a command line build that referenced some system framework other than Foundation/UIKit... It failed saying that it couldn't find the framework inside Xcode.app/....
Once I made Xcode.app into a proper symlink everything worked.
I am working with veins. I needed to change the default behavior of BaseWaveApplLayer. Rather doing in file changes, I created a second application file with the name MyApp. I added MyApp.cc, MyApp.h, MyApp.ned files. Then I duplicated TraCIDemoRSU11p, and added files for TraCIDemoRSU11pEnhanced. Now in .ini file when I changed *.rsu[*].applType to point to "TraCIDemoRSU11pEnhanced". It compiles fine, but when I try to run it, generates the following error:
Submodule appl: no module type named `TraCIDemo11pEnhanced' found that implements module interface org.car2x.veins.base.modules.IBaseApplLayer (not in the loaded NED files?).
In MyApp.ned file it is declared to be of type IBaseApplLayer. I tried setting ned-path parameter in ini file, didn't resolve the problem. In veins project properties, NED source folder is checked. Do I have to add the ned path for the newly created application file, somewhere?
Try using the cookiecutter package (https://veins.car2x.org/tutorial/#newprojects) to create new applications that use veins instead of copying and pasting files:
Use pip to install the package (https://github.com/cookiecutter/cookiecutter)
Then follow the steps in (https://github.com/veins/cookiecutter-veins-project/blob/master/README.md) to create the new project; following the prompts that appear.
This will create a new project that uses Veins and has the application layer-related files for you to update according to your application with no errors.
I have three files ImgProc.h, ImgProc.lib, and ImgProc.dll created by Matlab. I imported them to my VSC++ 2012 MFC project, but when I ran it, the error occurred. I did add the ImgProc.lib into the linker-> input->additional dependencies, Copied 3 files into project directory.
I could not add references. Because when I tried, it was empty like:
that
I really appreciate if someone could help me.
ImgProc.dll must be available at runtime in your application's directory. You need to manually copy this file to your output directories for both Debug and Release builds. Alternatively you can create a post-build step that does the copying. Having ImgProc.dll in your project directory is not enough - your project directory is not part of the Dynamic-Link Library Search Order.