27 Nov
2011
27 Nov
'11
9:40 a.m.
With autotools I use --enable-debug=full.
How is this done with cmake ?
I built with -DCMAKE_BUILD_TYPE=Debug but there is no difference in the final package
sizes.
Is there anything in the build log that lets me know how I built a package?
Darrell
27 Nov
27 Nov
4:55 p.m.
New subject: [trinity-devel] Cmake build with debug support
On Sunday 27 November 2011 04:40:44 Darrell Anderson wrote:
With autotools I use --enable-debug=full.
How is this done with cmake ?
I built with -DCMAKE_BUILD_TYPE=Debug but there is no difference in the
final package sizes.
Is there anything in the build log that lets me know how I built a package?
Try -DCMAKE_CXX_FLAGS="-g"
Darrell
--
Serghei
28 Nov
28 Nov
12:48 a.m.
New subject: [trinity-devel] Cmake build with debug support
With autotools
I use --enable-debug=full.
How is this done with cmake ?
I built with -DCMAKE_BUILD_TYPE=Debug but there is no
difference in the
final package sizes.
Is there anything in the build log that lets me know
how I built a package?
Try -DCMAKE_CXX_FLAGS="-g"
12:54 a.m.
New subject: [trinity-devel] Cmake build with debug support
On Sunday 27 November 2011 19:48:03 Darrell Anderson wrote:
I added that flag. Yet the package sizes are the same.
1. How do I know whether or not a package is built with debug support?
Run make VERBOSE=1 and check if -g parameter is passed to compiler.
With autotools I use --enable-debug=full.
How is this done with cmake ?
I built with -DCMAKE_BUILD_TYPE=Debug but there is no
difference in the
final package sizes.
Is there anything in the build log that lets me know
how I built a package?
Try -DCMAKE_CXX_FLAGS="-g" 2. Does the build log provide a clue?
See previous answer.
3. Should the package size be larger?
Yes, much larger. But ensure that binaries are not stripped at install stage
(you should not see "-s" parameter passed to linker). Use "file" to
check if
the binary is stripped or no.
4. Is there a simple test after installing the package
to test for
debugging support?
Dunno.
Please be verbose. :)
Darrell
--
Serghei
1:17 a.m.
New subject: [trinity-devel] Cmake build with debug support
> > With
autotools I use --enable-debug=full.
> >
> > How is this done with cmake ?
> >
> > I built with -DCMAKE_BUILD_TYPE=Debug but
there is no
>
> difference in the
>
> > final package sizes.
> >
> > Is there anything in the build log that lets
me know
how I built a package?
Try -DCMAKE_CXX_FLAGS="-g"
I added that flag. Yet the package sizes are the
1. How do I know whether or not a package is built
with debug support?
Run make VERBOSE=1 and check if -g parameter is passed to
compiler.
2. Does the build log provide a clue?
See previous answer.
3. Should the package size be larger?
Yes, much larger. But ensure that binaries are not stripped
at install stage
(you should not see "-s" parameter passed to linker). Use
"file" to check if
the binary is stripped or no.
4. Is there a simple test after installing the
package
to test for
debugging support?
Dunno.
1:21 a.m.
New subject: [trinity-devel] Cmake build with debug support
On Sunday 27 November 2011 20:17:04 Darrell Anderson wrote:
[...]
As I mentioned the package sizes are the same and
built times are basically
the same. Everything indicates I am not building with debug support.
What else do I need to do?
Run "file" against a library to check if is stripped. If is stripped, you
should check linker flags.
Darrell
--
Serghei
3:39 a.m.
New subject: [trinity-devel] Cmake build with debug support
As I mentioned
the package sizes are the same and
built times are basically
the same. Everything indicates I am not building
with
debug support.
What else do I need to do?
Run "file" against a library to check if is stripped. If is
stripped, you
should check linker flags.
4814
days inactive
4814
days old
6 comments
2 participants
participants (2)
-
Darrell Anderson -
Serghei Amelian