Hello,
I am trying to debug a program using the new IDE eclipse tools
My program includes many static libraries
All source codes are compiled with -g option
And I am using standard C++ make file (not QNX recursive make file).
All librairies are located in a separate and independant folder
My problem is that I cannot debug inside code included in my program and
belonging to a library , the C++ source code does not appears.
The assembler code does not appear also.
So, a a result, I cannot use the new IDE.
Someone said to me that if I use the QNX recursive make file
I will be able to do debug (single step) inside the source code of my
librairies.
It is a big work, and I am sure this is true because inside the code
produced by the GNU linker there is no reference of the path of source
code (only the name is indicated).
Is there anybody with experience with this situation, and reassure me about
the feasibility.
Thanks,
AR
Hello,
I am trying to debug a program using the new IDE eclipse tools
My program includes many static libraries
All source codes are compiled with -g option
And I am using standard C++ make file (not QNX recursive make file).
All librairies are located in a separate and independant folder
My problem is that I cannot debug inside code included in my program and
belonging to a library , the C++ source code does not appears.
The assembler code does not appear also.
So, a a result, I cannot use the new IDE.
Someone said to me that if I use the QNX recursive make file
I will be able to do debug (single step) inside the source code of my
librairies.
It is a big work, and I am sure this is true because inside the code
produced by the GNU linker there is no reference of the path of source
code (only the name is indicated).
Is there anybody with experience with this situation, and reassure me about
the feasibility.
Thanks,
AR
Hello,
I am trying to debug a program using the new IDE eclipse tools
My program includes many static libraries
All source codes are compiled with -g option
And I am using standard C++ make file (not QNX recursive make file).
All librairies are located in a separate and independant folder
My problem is that I cannot debug inside code included in my program and
belonging to a library , the C++ source code does not appears.
The assembler code does not appear also.
So, a a result, I cannot use the new IDE.
Someone said to me that if I use the QNX recursive make file
I will be able to do debug (single step) inside the source code of my
librairies.
It is a big work, and I am sure this is true because inside the code
produced by the GNU linker there is no reference of the path of source
code (only the name is indicated).
Is there anybody with experience with this situation, and reassure me
about
the feasibility.
Thanks,
AR
Hi David
What was the suggestion?
I can’t find the other post you refer to…
Hello,
I am trying to debug a program using the new IDE eclipse tools
My program includes many static libraries
All source codes are compiled with -g option
And I am using standard C++ make file (not QNX recursive make file).
All librairies are located in a separate and independant folder
My problem is that I cannot debug inside code included in my program and
belonging to a library , the C++ source code does not appears.
The assembler code does not appear also.
So, a a result, I cannot use the new IDE.
Someone said to me that if I use the QNX recursive make file
I will be able to do debug (single step) inside the source code of my
librairies.
It is a big work, and I am sure this is true because inside the code
produced by the GNU linker there is no reference of the path of source
code (only the name is indicated).
Is there anybody with experience with this situation, and reassure me
about
the feasibility.
Thanks,
AR
Hi David
What was the suggestion?
I can’t find the other post you refer to…
I’m not actually sure. This doesn’t look like something I
responded too. Maybe I thought I was following up something else.
But, one of the problems I found with the released version is that
it doesn’t seem to find source code that is more than a level or
two down in a multi-level directory structure inside a project.
This seems to be improved for the next generation.
On 3 Jan 2003 17:40:57 GMT, David Gibbs <dagibbs@qnx.com> wrote:
…
I’m not actually sure. This doesn’t look like something I
responded too. Maybe I thought I was following up something else. >
But, one of the problems I found with the released version is that
it doesn’t seem to find source code that is more than a level or
two down in a multi-level directory structure inside a project.
This seems to be improved for the next generation.
After some lateral searching, I found the problem to
be related to upper/lowercase of filenames on the
Windows host. These were files that were ported
from a DOS application (dragged & dropped from
the relevant directory), and although the application
builds ok, the files aren’t found at debug time.
I found the problem by creating a new file with the
same name inside of the IDE, in stead of dragging
a new file.
Seems the IDE will have to be more strict with
the case of filenames.
