using library compiled with -g option

[melalec]

hello all.
I have a simple question: if I have a library (eg libjpeg.a) compiled form source with the debugging option -g, can I use it in order to compile other programs?

Thanks a lot!!!

[i92guboj]

hello all.
I have a simple question: if I have a library (eg libjpeg.a) compiled form source with the debugging option -g, can I use it in order to compile other programs?

Thanks a lot!!!

What's the exact problem?

You should be able to use it as long as you instruct the programs you are compiling to use that version of libjpeg (in case that it's not the one installed on your base system).

If that's not what you needed to know, try to be more specific on what the actual problem is.

[melalec]

What's the exact problem?

You should be able to use it as long as you instruct the programs you are compiling to use that version of libjpeg (in case that it's not the one installed on your base system).

If that's not what you needed to know, try to be more specific on what the actual problem is.

my question arises from my embedded system experience, because if you compile a program for a MCU with the debug option, generally you won't be able to use this program "stand alone" but only within a debugger environment.

[wje_lf]

In the ordinary Linux environment, programs and libraries compiled with the -g option are perfectly usable in a non-debugging environment; the extra debugging information in the compiled code is ignored in that situation.

[i92guboj]

Now I understand your concern.

But, as wje_lf already told you, you don't need to worry about that. In linux you don't have any problem with debug builds. You can use them just like a regular build. The only "problems" are that it will usually be a bit (or a lot) slower and that the output to sdtout/sdterr will be much versobe sometimes.

[wje_lf]

it will usually be a bit (or a lot) slower

I don't understand. The only way it would be made slower is that the object code takes longer to read (or swap) into main memory, because of the extra object file information.

output to sdtout/sdterr will be much versobe sometimes

This is not correct. The only difference is that there is extra debugging information in the object files for use by the debugger. If you're not running a debugger, exactly the same code gets executed with or without the -g option.