dumplib | Import library generator for x86 PE files

 by   Mattiwatti C++ Version: 1.0.0 License: GPL-3.0

kandi X-RAY | dumplib Summary

kandi X-RAY | dumplib Summary

dumplib is a C++ library. dumplib has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Dumplib is a helper tool to create import libraries (.lib files) with correct extern "C" name decorations for x86 PE files compiled by MSVC. (This means not x64 because x64 files do not have decorated export names; for x64, see Remarks below.) Its main use is to allow creating import libraries for DLLs for which no import library is available, and to customize existing import libraries, e.g. to remove unwanted exports that cause linker collisions.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              dumplib has a low active ecosystem.
              It has 42 star(s) with 11 fork(s). There are 5 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              dumplib has no issues reported. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of dumplib is 1.0.0

            kandi-Quality Quality

              dumplib has 0 bugs and 0 code smells.

            kandi-Security Security

              dumplib has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              dumplib code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              dumplib is licensed under the GPL-3.0 License. This license is Strong Copyleft.
              Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

            kandi-Reuse Reuse

              dumplib releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of dumplib
            Get all kandi verified functions for this library.

            dumplib Key Features

            No Key Features are available at this moment for dumplib.

            dumplib Examples and Code Snippets

            No Code Snippets are available at this moment for dumplib.

            Community Discussions

            QUESTION

            Unresolved external symbol even if everything seems OK
            Asked 2021-Dec-28 at 13:37

            I'm not used to coding on Windows, and I am puzzled with this error on VS.

            I am developping a static library libA, another one libB calling some methods in libA, and a program prog calling some methods in libB.

            libA compiles without any problems.

            Same for libB. The include and lib folders about libA are given to VS, as well as libA.lib as an additional dependency.

            For prog, I give the include and lib folders concerning both libA and libB. The two libaries themselves are given as additional dependencies. It compiles, but while linking, I got a couple of errors LNK2001 of the type:

            unresolved external symbol "public virtual void __thiscall libA::classA1::methodA1(void)" (?methodA1@classA1@libA@@UEAXXZ) in File libB.lib(classB1.obj)

            I did a dumpbin of libB and the symbol ?methodA1@classA1@libA@@UEAXXZ appears many times in the dump file.

            ...

            ANSWER

            Answered 2021-Dec-28 at 13:37

            Finally, I found the problem.

            libA and libB were correctly working on Linux, so I didn't understand why I got this problem on Windows.

            Turns out that, I don't really know why, but the VS solution file generated by CMake allowed to compile libA with an x86 target architecture, but together with the additional option "/machine x64" in the command line section (Project Properties > Linker (or Librarian for a static library) > Command Line).

            I removed this "/machine x64" option, recompiled libA, and now the whole thing compiles and links.

            Source https://stackoverflow.com/questions/70491922

            Community Discussions, Code Snippets contain sources that include Stack Exchange Network

            Vulnerabilities

            No vulnerabilities reported

            Install dumplib

            You can download it from GitHub.

            Support

            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/Mattiwatti/dumplib.git

          • CLI

            gh repo clone Mattiwatti/dumplib

          • sshUrl

            git@github.com:Mattiwatti/dumplib.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link