On 08/20/2013 11:39 AM, Dick Hollenbeck wrote: > > KiCad Developers: > > Anyway I've looked, building some compiled libraries for boost is required > and I have > augmented CMakeModules/download_boost.cmake to conditionally build some > compiled boost > libraries, although that support is not enabled yet. There is an alternate > execution path > in that module that does what it did before except for a new header file > location. > > > I have the boost build scripts mostly done, but want to take a break so I am > committing > what I have done so far. > > The net effect of this upcoming commit, short term, is that the boost headers > are moved into > > to > <kicad_src>/boost_root/include/boost > > from > <kicad_src>include/boost > > . > > > This immediately paves the way for a sensible <kicad_src>/boost_root/libs/* > as needed and > as used in the alternate execution path in download_boost.cmake. > > It also smoked out some bugs in our build scripts which were using a bogus > Boost_INCLUDE_DIR variable, which was dis-functional, but now is functional. > > If you have any problems with it let me know. > > (Thinking of ramifications across 3 platforms has taken its toll. I can > however see a > clear path forward, and will be back at this within a week or two after I > recharge my > batteries. My current thinking is to try and use boost::async
oops, boost::asio (proof its time for a longer break.) > and forgo use of other > networking libraries on top of that. On windows we will have to pick up > openssl support, > and that may mean insisting on the python install to pull it from python > a-mingw-us. I > build it there, but not in DLL form yet.) > > > Dick > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
