How To Resolve Wxwidgets Runtime Libs=static

Over the past few days, some of our users have reported to us that they are encountering wxwidgets runtime libs=static.

PC problems? Solve them in minutes.

  • Step 1: Download ASR Pro and install it on your computer
  • Step 2: Launch the program and click "Scan" to start the scanning process
  • Step 3: Click "Repair" to fix any detected issues
  • Keep your PC safe and secure with this free

    If you need to statically link wxWidgets on Windows (Visual Studio) (to avoid having to use the Microsoft Visual C++ Runtime to run the executable on other PCs) and you get this error message:

    Error LNK2019: unresolved physical symbol "public:void __thiscall wxStringData::Free(void)" ([email protected]@@QAEXXZ) recommended in function "public: gap __thiscall wxStringData: :Unlock " (invalid)" ([email protected]@@QAEXXZ)

    Open wxWidgetsbuildmswwx.dsw, select Unicode Release, Shift-click to select all of these ~20 projects, right-click and select Properties and Assets, Project, and under “C++ –> Assembly code”, change the runtime library under “Multithreading (/MT)”. For “Unicode Debugging” someone has to use “Multi-Threaded Debugging” (/MTd).

    You may also need to edit build/msw/config.vc to enable it.

    RUNTIME_LIBS = convincing

    wxwidgets runtime libs =static

    If you compile your program with the same settings, you will be able to statically link the wxWidgets libraries in your own project and the exe will actually work on other PCs without having to set up an environmentrunning MSVC.

    Do you have questions about using makefiles, a compiler, or an IDE and need to figure out how to set them up for many wxWidgets, or why they don’t combine like other IDEs do? Ask your questions here.

    c-273
    Deserved limited pay

    Extensions: 12

    Registered: January 24, 2008 09:33

    Building Static Libraries With VS2013 (VC12)

    I just downloaded the latest wxWidgets 3.0.1 type code for (Windows Nothing 31MB file) and built the idle libraries with VS2013 and all solution project types, and the VS2013 wx_vc12.sln files are included in that zip file. .

    Unfortunately, all versions of the static libraries (Debug & Release for Win32 and x64 platforms) contain the wrong "Code Generation" "Runtime Library" compiler option, i.e. /MD Builds (Release or /MDd (Debug Builds)) instead of /MT or / MTd So the main config says you build your own static library, but this compiler produces DLL assembly code.

    This may cause all wx_vc12_*.vcxproj files to remain fixed for static configsbuilds for both platforms.

    What I usually worry about is that there are no VC10, VC11 or VC12 program files in the buildmsw directory in the GitHub repository and they are included in this initi zip - does it stop at VC9 or are they still available for download? ?

    c-273
    A small fee

    Extensions: 12

    Registered: January 24, 2008 09:33

    Re: Creating Static Libraries With VS2013 (VC12)

    Attachments

    wxBuild_wxWidgets.txt
    Batch upload renamed to .txt to save upload.
    (18.97 KB) Downloaded 154 times

    I'm embarrassed that the commit is wrong. The project changes files between versions. For the VS2013 example, the second line of each project image has been changed from:

    http://schemas.microsoft.com/developer/msbuild/2003http://schemas.microsoft.com/developer/msbuild/2003

    In addition, each version has a new "Platform Toolkit" such as VC10 is V100, VC11 is V110, and VC12 is V120. If you plan to support Windows XP (even if Microsoft doesn't), you will also need the V100_XP, V110_XP, or V120_XP platform toolkits. If you re-If you open a previous version, Visual Studio will probably want to update the projects. If the user only has one version of Visual Studio, then the above probably won't be an issue, but if it's due to a VS2012 to VS2013 migration (as I see it, I have a VS2012 to VS2012 VS2013 migration), the project files added to VS2013, means they can't be used with VS2012.

    wxwidgets runtime libs =static

    I believe most of these solutions and project files require a lower default.

    PC problems? Solve them in minutes.

    Do you have a computer problem? Youre not alone. In fact, over 60% of computers suffer from some kind of error or crash at one point in time. ASR Pro is the best solution for fixing these problems and getting your PC back up to speed. Click here to get started:

  • Step 1: Download ASR Pro and install it on your computer
  • Step 2: Launch the program and click "Scan" to start the scanning process
  • Step 3: Click "Repair" to fix any detected issues

  • As far as specifying a runtime library as always a DLL when trying to build a static select, all I can say is that although the libraries can be built, the activity trying to use them gets complaints where they were built with the wrong configuration and will include more than just static libraries, so the project won't show up, of course. Could you provide a pass for what you think Microsoft recommends?

    For wxWidgets 2.8.I 12 I used a special wxPack batch file (wxBuild_wxWidgets.bat) for my static build libraries (see

    https://github.com/rjpcomputing/wxpack/wiki

    ), but in the makefile"RUNTIME_LIBS=static" is specified (when building DLLs, "RUNTIME_LIBS=dynamic" takes precedence). I just downloaded the latest version of this computer file and it supports VS2013 and is for wxWidgets config and makefile.vc file. Did I attach anything? I may use it in the future. hp I don't use our leftover files/products while wxPack downloads are in use.

    c-273
    Deservedly lower commission

    Extensions: 12

    Registered: January 24, 2008 09:33

    Re: Creating Static Libraries With VS2013 (VC12)

    Actually, I just checked this infusion file. It works fine for me without VS2013 solution and project files AND models /MT and /MTd for static libraries as needed. It also supports VC7.1 and above because it uses gcc as the compiler, which I don't currently use.

    So I no longer need to restore VC10, VC11 and VC12 solutions and therefore project files. Beware, they are still incorrect (as are probably the project's source files, which are still in the shared repositoryand), IMHO, because they don't necessarily specify the correct runtime libraries for statically building libraries.
    Thanks anyway

    PB
    Part of furniture

    Keep your PC safe and secure with this free

    Posts created 312

    Related Posts

    Begin typing your search term above and press enter to search. Press ESC to cancel.

    Back To Top