Make import symbol limit configurable

[fpq473]

Hello, thanks for this useful tool.

I came across a scenario where delvewheel-repair does not include all necessary DLLs. This was caused by pefile returning a truncated list of imports due to a limit on the number of imports parsed. I observe in CadQuery/cadquery#1048 (comment) that increasing pefile.MAX_IMPORT_SYMBOLS at least partially resolves some issues.

My ideas for delvewheel are:

• Allow MAX_IMPORT_SYMBOLS to be specified at the command-line, e.g. delvewheel repair --max_import_symbols=1000000 leads to pefile.MAX_IMPORT_SYMBOLS = 1000000 before parsing;

• Display all pefile warnings to the user. Warning messages are accumulated on the PE object (example) and can be retrieved by PE.get_warnings().

[adang1345]

I have fixed this issue and #29 and in the newly released version 0.0.22.

I added an option to display warnings from pefile.

I fixed the issue of exceeding the number of imported symbols by using the import_dllnames_only parameter at https://github.com/erocarrera/pefile/blob/9addb08b9906266ad8835a5ac80c7ec623cff758/pefile.py#L3513. When this is set to True, we avoid parsing the symbols that are imported from each DLL and thus don't go over the pefile.MAX_IMPORT_SYMBOLS limit.

I ran a quick test against a copy of OCP.cp310-win_amd64.pyd from https://github.com/roipoussiere/OCP/actions/runs/2173754949, and it looks like delvewheel is able to list out all its dependencies now.

[fpq473]

Thank you very much for the exceedingly quick and helpful changes. Using import_dllnames_only brings the loading of data directories from around two minutes to under 10 ms. Also thanks for testing against OCP and making the new release - that will make our builds very convenient.