[amigo421]

seems visualgdb interprets cmake oddly (incorrect?).

cmake_minimum_required (VERSION 3.5)

project(my_project)

…
add_executable(my_project main.cpp src/handler.cpp)

target_link_libraries(my_project pthread boost_system crypto ssl cpprest swe “${LIBRARIES_FROM_REFERENCES}”)

the case above works fine.

however (more correct for cmake , from my perspective) doesn’t work with error from the initial post

cmake_minimum_required (VERSION 3.5)

project(my_project)

…
add_executable(${PROJECT_NAME} main.cpp src/handler.cpp)

target_link_libraries(${PROJECT_NAME} pthread boost_system crypto ssl cpprest swe “${LIBRARIES_FROM_REFERENCES}”)

[amigo421]

you are right, thank you, it really works,

placing .so into source folder does also work , just have needed to replace Debug with Linux-style “.”(current folder,  instead of “”

[amigo421]

thank you, I successfully switched on GNU Make system, with some limits (see my topic about custom build folder)

please comment my question about debugged executeable field.

”

1. please confirm that Debugged Executable is not stored to settings when specified in a Wizard, bug?

”

if this is really a bug, do you have a public tracker for the requests?

“

[amigo421]

confirmed , makefile project created from scratch works fine with auto build on update

however another issues are found , please comment in a topic “custom build folder”

[amigo421]

I suppose that can be happened due the mixed makefile usage, which I decribed in previous topic (about PHP debug)

when I switch from custom to gnu make build system, it really didn’t overwrite my imported from linux make file but does some odd mixture of original and generated from GUI settings.
I’ll try to migrate to GUI based makefile completely and move my actions from original one accurtelly ,

and if the problem will be still there, I’ll ask you for a next steps

 

THank you!

[amigo421]

the topic can be closed,

the steps to solve:

1. after makefile-based project import, build system has been set to Custom, so I’ve changed to GNU Make manually. is it okay? or bug?
2. add some required (from makefile GUI dialog) settings, which were added to my existing makefile, thanks a lot that just added only, not overwritten 🙂

the settings from default Debug GUI dialog were enough for start debug

currently works perfect, thank you!

=========================================================================

so as a summary of the topic:

1. please confirm that Debugged Executable is not stored to settings when specified in a Wizard, bug?
2. IMport makefile based project doesn’t set build system to GNU Make, why

• This reply was modified 7 years, 10 months ago by amigo421.

[amigo421]

do I understand GCC compilation right , for the including debug info, I have to add these flags to Makefile

LD_FLAGS = -Wall -shared -O0 –g -ggdb3  ??

 

and how can I add “set solib-search path command”? and why? all my sources and .so in the same work directory (just for simplifying on this step)

• This reply was modified 7 years, 10 months ago by amigo421.

[amigo421]

didn’t find ” info symbols” output… please assist

 

by the way , a couple more questions:

1. in a wizard “import .so project”, that I’m doing from linux host, the setting: Debugged executable , I’m specifying “php”, however, after the project created, this field is $(TargetPath), and I need to change this again, is it a bug?
2. please clarify, why my makefile from linux host is not imported locally? If I will download this manually and change this locally, will this be uploaded to remote host for a building automatically?

[Author]

Posts