Publish generated pdb files

amz-shahji commented 5 years ago

When publishing libraries and executables, the process should include generated pdb files, either as part of the same or a new artifact.

Generated pdb files will be published and made available when consuming.

PDB files are ignored.

When compiling under MSVS, the linker throws a warning (LNK4099 specifically) when pdb files are not available.

amz-shahji commented 5 years ago

Related to #610

lacasseio commented 5 years ago

This issue contains three distinct parts of the work: 1) the producer, 2) the consumer and 3) the publishing.

Thinking quickly about this, here is a small outline of the work to be done:

[ ] A new usage, something like native-debugging
[ ] A configuration for consuming (the producer) ending with Elements with the debugging usage. This configuration should have the outgoing artifact set to the debugging file and built by the compile task.
[ ] A configuration for resolution (the consumer) with the debugging usage.
[ ] A new variant on the main publication of a component. It will require a new SoftwareComponent implementation which I would recommend keeping internal. We want to avoid any public configuration of the PDB file at this point.
[ ] Support the absence of PDB files

gradle / gradle-native