From: Kirk J. <kir...@gm...> - 2013-06-22 20:20:03
|
> As Eli says, if you switch to MSVC++ you have to rebuild boost with that > compiler. More specifically, with the MSVC++ version you would be using. > Same for major GCC releases (i.e. 4.7/4.8 etc) or even for the same GCC > release configured with incompatible options (DW2/sjlj exception model, > etc.) Thanks for this information. I got the idea of trying to make shared resources from this HOWTO on the MinGW website http://www.mingw.org/wiki/IncludePathHOWTO Near the bottom there is a list of three ways you might try to deal with external resources. I went with #3 because it appealed to my tastes. You are basically saying that #3 doesn't actually work. > The specs file is not a configuration file for the final user to tinker > on. It is mostly for platform-specific configuration, the sort of work > the MinGW folks do for you. > What you want must be achieved the same way other users do: either by > installing the headers and libraries on a path that the toolset already > knows about or by explicitly telling the build process of your project > where to find the required libraries. Ok, I'm very glad you're telling me this because this HOWTO http://www.mingw.org/wiki/SpecsFileHOWTO really makes it seem like editing specs is kosher. > Editing the specs file is the most complicated and error prone method of > achieving what you want. This needs to be indicated in the documentation. As it stands that specs HOWTO makes it sound like editing specs is a perfectly fine idea. > Forget it. Make yourself familiar with the standard methods for building > projects and that will do, as it does for 99.99% of the people out > there. Tinkering with the specs file is like opening a can of worms. I'm really surprised by this given the existence of official documentation on editing specs. I'll go with your solution for now until someone else pipes in. Thanks. |