Feature #3035 2007-01-11 07:31
mareq
Shared libraries directories
Ubuntu (6.10) I have read some posts regarding this problem, but nothing helped. I have workspace with multiple projects: shared libraries and executable(s). I have also other third-party shared libraries in a specific folder of my workspace. Example of built and third-party libs locations: /home/user/cbtest/lib1proj/Debug/lib1.so /home/user/cbtest/lib2proj/Debug/lib2.so - these are libraries generated by CB /home/user/cbtest/libs/libthirdparty1.so /home/user/cbtest/libs/libthirdparty2.so - these are third party libraries /home/user/cbtest/executableproj/Debug/executable - this is the executable file generated by CB There was no problem with building these files using CB. I only had to set the libraries and library directories in CB: executableproj -> Project build options -> Tab Linker -> Link libraries would be 1 2 thirdparty1 thirdparty2 executableproj -> Project build options -> Tab Directories -> Tab Linker would be ./../lib1proj/Debug ./../lib2proj/Debug ./../libs But I am not able to launch this project, neither Debug, nor Run. I set up the Environment variables in CB -> Settings -> Environment -> Environment variables: LD_LIBRARY_PATH=/home/user/cbtest/lib1proj/Debug/:/home/user/cbtest/lib2proj/Debug/:/ home/user/cbtest/libs/ but it didn't help. When I run the executable from CB, the xterm writes that it is not able to locate the shared library. When I start debugging, there is no console output and the debugger ends with messages: Program exited with code 0177. Debugger finished with status 0 In case of debugging I am not able to see what is wrong. Please help me, to solve it. 1. How to specify the libraries directories for xterm when running from CB. (IMPORTANT) 2. How to change xterm to other terminal. 3. How to specify the libraries directories for debugger when debugging from CB. (IMPORTANT) 4. How to see the console output of my application (it is a GTK2+ GUI application, but I print trace messages to console). (IMPORTANT) Suggestions: 1. Automatically add the libraries for executable linker options - looking for projects, the executable depends on. 2. Automatically set the library paths when debugging or running the project. (3. Possibility to set target specific library paths of third-party libs when debugging or running.)
- Category
- Build System
- Status
- Open
- Close date
- Assigned to