| How to deploy files at a remote debug launch? [message #1567536] |
Fri, 16 January 2015 12:16  |
 Yuri Rumega
Messages: 1
Registered: January 2015
Location: Rostov-on-Don, Russia |
Junior Member |
|
|
Please give me advice how to setup a debug environment with Eclipse CDT/ RSE / DSF or whatever else is available.
I have an enterprise application, which consists of an executable and a lot (30+) of shared library modules. The application is targeted for an embedded non-x86 platform, with POSIX-compatible operating system (QNX or GNU/Linux, depending on the selected toolchain). Because of that, debugging has to be done remotely.
I installed cdt.launch remote ("C/C++ remote launch") and RSE ("Remote System Explorer End User Runtime", "Remote System Explorer User Actions"). Now my Eclipse can launch a program remotely (over ssh) and debug it with gdbserver. But only the main executable can be configured for upload... I found no option for uploading shared libraries.
I wonder what is an appropriate way to deploy files for a debug launch via Eclipse?
My current choices are:
- Using Remote System Explorer perspective, "import" some remote folder as a "Remote project" in the workspace. Set Makefile to copy .so files to the mapped folder after build. After build, manually refresh the "remote project". Then, changed files will be uploaded to remote system at launch.
- Using Remote System Explorer perspective, "export" binaries located in workspace to remote file system, so that files would be uploaded at remote launch. This method also require me to "refresh" all the projects before starting a debug session, or changes wouldn't be noticied.
- Don't use Eclipse for file uploading at all, and deploy them manually or by means of the build script.
- Take the hard way and contribute some code to Eclipse СDT.
Is there a better solution??
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02562 seconds
] 
Search
Help
Register
Login
Home
). The order of the entries made in "C/C++ General>Paths and Symbols" gets intermixed accidentially when switching between Release and Debug configurations. As a result, the project won't compile. It is some kind of a self destruction mechanism. The workaround is to ignore those settings and add the static libraries under "C/C++ Build>Settings>Cross ARM C++ Linker>Miscellaneous>Other objects".