Boost Serialization and MFC: “cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib' ”How can I decode the boost library naming?Boost linker errorBoost::Serialization and MFC Doc/View architecturehow to use Boost Asio in MFC Dialog based application?linker errors with boost::archive and serializationboost serialization for socketsFatal error LNK1104: cannot open file 'libboost_log-vc141-mt-gd-1_64.lib'c++ Boost-asio static libraries to release static compilationBoost.Python not the .libLinking boost library in node native module, object file requiring alternative library versionHow to use boost serialization?

Why does it seem the best way to make a living is to invest in real estate?

Why do popular TCP-using services have UDP as well as TCP entries in /etc/services?

Re-entering the UK after overstaying in 2008

Where does the image of a data connector as a sharp metal spike originate from?

Why has Speaker Pelosi been so hesitant to impeach President Trump?

Airport Security - advanced check, 4th amendment breach

How to identify whether a publisher is genuine or not?

How dangerous is a very out-of-true disc brake wheel?

Why do personal finance apps focus on outgoings rather than income

How to prove that the quadratic equation has exactly two real solutions

How to find places to store/land a private airplane?

Why do Russians sometimes spell "жирный" (fatty) as "жырный"?

Drawing Maps; flat distortion

Principled construction of the quaternions

Booting Ubuntu from USB drive on MSI motherboard -- EVERYTHING fails

IEEE 754 square root with Newton-Raphson

Duck, duck, gone!

French license plates

Why does `FindFit` fail so badly in this simple case?

Did the Soviet army intentionally send troops (e.g. penal battalions) running over minefields?

Why such a singular place for bird watching?

What action is recommended if your accommodation refuses to let you leave without paying additional fees?

Are there types of animals that can't make the trip to space? (physiologically)

Decision Variable Value from a Set (Gurobi)



Boost Serialization and MFC: “cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib' ”


How can I decode the boost library naming?Boost linker errorBoost::Serialization and MFC Doc/View architecturehow to use Boost Asio in MFC Dialog based application?linker errors with boost::archive and serializationboost serialization for socketsFatal error LNK1104: cannot open file 'libboost_log-vc141-mt-gd-1_64.lib'c++ Boost-asio static libraries to release static compilationBoost.Python not the .libLinking boost library in node native module, object file requiring alternative library versionHow to use boost serialization?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









1















I'm currently trying to use boost for serialization in my project. I started by following this demo and making sure I could get boost working on Visual Studio:



https://www.boost.org/doc/libs/1_69_0/libs/serialization/example/demo.cpp



After following this demo, I added boost onto my project where I ran into some issues. When I change "Use Standard Windows Libraries" to "Use MFC in a Static Library" I get the error:



cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib'


More specifically this happens for the following includes.



#include <boost/archive/text_iarchive.hpp>
#include <boost/archive/text_oarchive.hpp>
#include <boost/serialization/list.hpp>


I'm new to boost, so what I'm wondering is why this would be occurring and how necessary these are for data storage. If fundamental, how would I go about fixing it?










share|improve this question






























    1















    I'm currently trying to use boost for serialization in my project. I started by following this demo and making sure I could get boost working on Visual Studio:



    https://www.boost.org/doc/libs/1_69_0/libs/serialization/example/demo.cpp



    After following this demo, I added boost onto my project where I ran into some issues. When I change "Use Standard Windows Libraries" to "Use MFC in a Static Library" I get the error:



    cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib'


    More specifically this happens for the following includes.



    #include <boost/archive/text_iarchive.hpp>
    #include <boost/archive/text_oarchive.hpp>
    #include <boost/serialization/list.hpp>


    I'm new to boost, so what I'm wondering is why this would be occurring and how necessary these are for data storage. If fundamental, how would I go about fixing it?










    share|improve this question


























      1












      1








      1








      I'm currently trying to use boost for serialization in my project. I started by following this demo and making sure I could get boost working on Visual Studio:



      https://www.boost.org/doc/libs/1_69_0/libs/serialization/example/demo.cpp



      After following this demo, I added boost onto my project where I ran into some issues. When I change "Use Standard Windows Libraries" to "Use MFC in a Static Library" I get the error:



      cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib'


      More specifically this happens for the following includes.



      #include <boost/archive/text_iarchive.hpp>
      #include <boost/archive/text_oarchive.hpp>
      #include <boost/serialization/list.hpp>


      I'm new to boost, so what I'm wondering is why this would be occurring and how necessary these are for data storage. If fundamental, how would I go about fixing it?










      share|improve this question














      I'm currently trying to use boost for serialization in my project. I started by following this demo and making sure I could get boost working on Visual Studio:



      https://www.boost.org/doc/libs/1_69_0/libs/serialization/example/demo.cpp



      After following this demo, I added boost onto my project where I ran into some issues. When I change "Use Standard Windows Libraries" to "Use MFC in a Static Library" I get the error:



      cannot open file 'libboost_serialization-vc141-mt-s-x32-1_69.lib'


      More specifically this happens for the following includes.



      #include <boost/archive/text_iarchive.hpp>
      #include <boost/archive/text_oarchive.hpp>
      #include <boost/serialization/list.hpp>


      I'm new to boost, so what I'm wondering is why this would be occurring and how necessary these are for data storage. If fundamental, how would I go about fixing it?







      c++ boost mfc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 28 at 19:09









      TarfaceTarface

      114 bronze badges




      114 bronze badges

























          1 Answer
          1






          active

          oldest

          votes


















          0
















          The 'x32' in the error message filename indicates that "Use MFC in a Static Library" is trying to link with a 32 bit boost library and the s in the filename indicates that it requires a static library, see: how can I decode boost library namimg.



          Your boost libraries are most likely built in 64 bit mode and may not be static. You can tell from the library filenames: 64 bit libraries have 'x64' in their filename, e.g.: libboost_serialization-vc141-mt-x64-1_69.lib is a 64 bit library that is not built for static linking to the C++ standard library and compiler runtime support libraries, because it does not have -s in the filename.



          In which case, the solution is to build the boost serialization library in 32 bit mode, with runtime-link=static, see boost getting stared on windows.






          share|improve this answer

























          • Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

            – zett42
            Mar 28 at 21:46













          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );














          draft saved

          draft discarded
















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55405204%2fboost-serialization-and-mfc-cannot-open-file-libboost-serialization-vc141-mt%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0
















          The 'x32' in the error message filename indicates that "Use MFC in a Static Library" is trying to link with a 32 bit boost library and the s in the filename indicates that it requires a static library, see: how can I decode boost library namimg.



          Your boost libraries are most likely built in 64 bit mode and may not be static. You can tell from the library filenames: 64 bit libraries have 'x64' in their filename, e.g.: libboost_serialization-vc141-mt-x64-1_69.lib is a 64 bit library that is not built for static linking to the C++ standard library and compiler runtime support libraries, because it does not have -s in the filename.



          In which case, the solution is to build the boost serialization library in 32 bit mode, with runtime-link=static, see boost getting stared on windows.






          share|improve this answer

























          • Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

            – zett42
            Mar 28 at 21:46
















          0
















          The 'x32' in the error message filename indicates that "Use MFC in a Static Library" is trying to link with a 32 bit boost library and the s in the filename indicates that it requires a static library, see: how can I decode boost library namimg.



          Your boost libraries are most likely built in 64 bit mode and may not be static. You can tell from the library filenames: 64 bit libraries have 'x64' in their filename, e.g.: libboost_serialization-vc141-mt-x64-1_69.lib is a 64 bit library that is not built for static linking to the C++ standard library and compiler runtime support libraries, because it does not have -s in the filename.



          In which case, the solution is to build the boost serialization library in 32 bit mode, with runtime-link=static, see boost getting stared on windows.






          share|improve this answer

























          • Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

            – zett42
            Mar 28 at 21:46














          0














          0










          0









          The 'x32' in the error message filename indicates that "Use MFC in a Static Library" is trying to link with a 32 bit boost library and the s in the filename indicates that it requires a static library, see: how can I decode boost library namimg.



          Your boost libraries are most likely built in 64 bit mode and may not be static. You can tell from the library filenames: 64 bit libraries have 'x64' in their filename, e.g.: libboost_serialization-vc141-mt-x64-1_69.lib is a 64 bit library that is not built for static linking to the C++ standard library and compiler runtime support libraries, because it does not have -s in the filename.



          In which case, the solution is to build the boost serialization library in 32 bit mode, with runtime-link=static, see boost getting stared on windows.






          share|improve this answer













          The 'x32' in the error message filename indicates that "Use MFC in a Static Library" is trying to link with a 32 bit boost library and the s in the filename indicates that it requires a static library, see: how can I decode boost library namimg.



          Your boost libraries are most likely built in 64 bit mode and may not be static. You can tell from the library filenames: 64 bit libraries have 'x64' in their filename, e.g.: libboost_serialization-vc141-mt-x64-1_69.lib is a 64 bit library that is not built for static linking to the C++ standard library and compiler runtime support libraries, because it does not have -s in the filename.



          In which case, the solution is to build the boost serialization library in 32 bit mode, with runtime-link=static, see boost getting stared on windows.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 28 at 20:52









          kenbakenba

          2,6091 gold badge11 silver badges30 bronze badges




          2,6091 gold badge11 silver badges30 bronze badges















          • Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

            – zett42
            Mar 28 at 21:46


















          • Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

            – zett42
            Mar 28 at 21:46

















          Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

          – zett42
          Mar 28 at 21:46






          Building boost yourself can be somewhat tricky for a beginner. There are myriades of build options. For beginners I recommend to download prebuilt binaries. Also it can be helpful to add "/VERBOSE:LIB" to the linker command-line arguments to see where the linker is searching for the libs.

          – zett42
          Mar 28 at 21:46





















          draft saved

          draft discarded















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55405204%2fboost-serialization-and-mfc-cannot-open-file-libboost-serialization-vc141-mt%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

          Swift 4 - func physicsWorld not invoked on collision? The Next CEO of Stack OverflowHow to call Objective-C code from Swift#ifdef replacement in the Swift language@selector() in Swift?#pragma mark in Swift?Swift for loop: for index, element in array?dispatch_after - GCD in Swift?Swift Beta performance: sorting arraysSplit a String into an array in Swift?The use of Swift 3 @objc inference in Swift 4 mode is deprecated?How to optimize UITableViewCell, because my UITableView lags

          Access current req object everywhere in Node.js ExpressWhy are global variables considered bad practice? (node.js)Using req & res across functionsHow do I get the path to the current script with Node.js?What is Node.js' Connect, Express and “middleware”?Node.js w/ express error handling in callbackHow to access the GET parameters after “?” in Express?Modify Node.js req object parametersAccess “app” variable inside of ExpressJS/ConnectJS middleware?Node.js Express app - request objectAngular Http Module considered middleware?Session variables in ExpressJSAdd properties to the req object in expressjs with Typescript