kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #11313
Re: Failed to build boost, any changes recently?
Succumbing to top posting:
I just checked in a fix to the Linux scripting builds (i.e. DSO form) with GITHUB_PLUGIN
enabled. (So you should soon update to avoid merge conflicts.)
I enhanced IO_MGR::GuessPluginTypeFromLibPath() to support GITHUB_PLUGIN. You can also
use it from python.
This means you could use lib_convert.py to download and install locally any github based
footprint library in about 3 seconds, just by making that the lib_source argument.
Why you'd want to do that is if you were on a boat without internet access.
Had to add -fPIC to boost compile, so I could link those static boost libraries into the
DSO. (Starting to appreciate header only libraries now.)
Added the github_plugin "cmake library target" to the python DSO. This target is magic in
that it brings in all dependent libraries with the one target name, see line 62 of
github/CMakeLists.txt. This is the way to do it for Windows please, consolidate everthing
under that one target name please.
I am moving on now, the linux support for GITHUB_PLUGIN seems solid, although my testing
of only a quantity 2 footprint library does not mean it is yet. It certainly looks
outstanding though.
Dick
On 09/23/2013 08:34 AM, Miguel Angel wrote:
> Thanks a lot Dick,
>
> I didn't have time this morning to check what was the problem.
>
> But , with the information you shared I can go straight away and fix it.
>
> If there are no more accidental issues, we must get it fixed for OSX this night.
>
> Miguel Angel Ajo Pelayo
> http://www.nbee.es
> +34 636 52 25 69
> skype: ajoajoajo
>
>
> 2013/9/23 Dick Hollenbeck <dick@xxxxxxxxxxx <mailto:dick@xxxxxxxxxxx>>
>
> On 09/23/2013 08:12 AM, Dick Hollenbeck wrote:
> > of course in response to your title, yes something has changed. In order to use SSL
> (i.e.
> > https://github.com/.... ) we use a software stack consisting of boost::asio and avhttp.
> >
> > Underneath these are some *compiled* portions of boost. (Until now, we did not have to
> > compile boost. Enabling BUILD_GIHUB_PLUGIN in cmake, changes the way boost is
> installed.)
> >
> > Here are some tips on compiling boost for OSX,
>
>
> OOPS,
>
> http://stackoverflow.com/questions/4755712/how-to-build-boost-1-45-universal-binaries
>
>
>
> but realize that compiling a subset of
> > boost is smarter and faster. That is the path I chose, so sub-setting the libraries
> that
> > are compiled is a worthwhile effort. Once the compile is done, you should not have to
> > recompile again for any additional out of tree build dirs. That is, so long as you
> > continue to keep BUILD_GITHUB_PLUGIN enabled. If you turn it off for another build
> > directory, then the process gets reset. This resetting is temporary I think.
> Eventually
> > I would hope that everyone can simply use the GITHUB_PLUBIN builds.
> >
> >
> > Dick
> >
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
>
Follow ups
References
-
Failed to build boost, any changes recently?
From: Miguel Angel, 2013-09-22
-
Re: Failed to build boost, any changes recently?
From: Miguel Angel, 2013-09-22
-
Re: Failed to build boost, any changes recently?
From: Dick Hollenbeck, 2013-09-23
-
Re: Failed to build boost, any changes recently?
From: Dick Hollenbeck, 2013-09-23
-
Re: Failed to build boost, any changes recently?
From: Miguel Angel, 2013-09-23