|Just another Perl shrine|
Re^3: Config sets optimisation compilation flags (-O/-g)!by BrowserUk (Patriarch)
|on Jan 28, 2019 at 19:53 UTC||Need Help??|
Config simply supplies the same options as was used to build the build of perl you are using; full stop.
If you want to override those options you must do so manually; and you must also consider the implications of your code having been built with different options to the build of perl with which it will be interacting at the binary level.
Eg. If you want to be able to debug your C code extensions, and turn off optimisations so that the binary code generated matches the source code, then when you run that code under the debugger, your extension's code will match up to its sources; but if you trace the code into the perl binary, its code will not match up to its sources, because it will have been optimised.
Whilst it will be possible to debug the extension that way, it would almost certainly be better to build a debug version (ie.no optimisations) of the perl binary, and use that to build and debug your extensions. In that case, your extension will inherit those debug build options by default and you won't need to modify them manually.
Once you extension is fully debugged, you can go back to the optimised build of perl, and your extension will be optimised also.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". The enemy of (IT) success is complexity.
In the absence of evidence, opinion is indistinguishable from prejudice. Suck that fhit