Hi all,
due to the size of the html doc I made a new repository which is uploading to github.
It is there
https://github.com/levush/electric-html-doc

The html-doc tarball will be removed from the
https://github.com/levush/electric
as soon as possible in order to allow for checking out the source code quickly.

Cheers,

Ludwig


On Wed, Jan 23, 2019 at 6:30 AM ludwig jaffe <ludwig.jaffe@gmail.com> wrote:
Hi all,

having Kicad to support VLSI design would be great. As the tool is then maintained by the cern. So we can focus
on other stuff. Also cern would have a benefit as they could design their asics using Kicad. The users of KiCad get
to know our project and are able to design chips.
A 3Win situation. Try to promote it from the view of cern benefiting from vlsi design capabilities.

Electric as backup solution:
So I generated doxygen with caller grapghs and so on for electric which takes long having 4 xeon cores and enough ram
in the vm. the documentation is uploading to github, so wait a while and you can git clone and have fun with the project.
Maybe, I should make a different repository for the documentation as it is huge.
https://github.com/levush/electric/tree/master/doc

Cheers,

Ludwig




On Wed, Jan 23, 2019 at 5:49 AM Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:


On Wednesday, January 23, 2019, David Lanzendörfer <david.lanzendoerfer@o2s.ch> wrote:
Their build system sucks and it's virtually impossible to build a distribution
package for it...

It's just cmake. There's nothing special. I got it up and running last year on debian, spoke to jean-paul, and submitted patches, which were accepted.
 
Now, yes, boost is a bitch on steroids, the people who created it should be castrated or something suitably painful as a way to reflect the level of pain that they've inflicted on others through their thoughtless lack of proper strategic planning on API changes.  I believe I have had up to EIGHT f**bbn versions of libboost simultaneously installed at some point. Absolute insanity.

Anyway.

If i recall correctly I set up a debian/stable chroot in order to get out of the hell that is boost.

The normal way that this is dealt with in debian is to use the auto-chroot-build debian developer tools. This guarantees a consistent clean environment. I forget the name of the tool, so did the chroot manually.

The patches that I added were down to strange spurious changes to the linker phase of upstream cmake or dependencies.  Cant recall the details but I had to list all of the libraries manually even those that had aleady been linked in to other shared libraries.

On ubuntu they allow shared libraries to recursively pull in their dependent shared libraries into the executable being linked.

It was a pain in the ass to track down, but should be fine, now.

L.


--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

_______________________________________________
Libre-silicon-devel mailing list
Libre-silicon-devel@list.libresilicon.com
http://list.libresilicon.com/mailman/listinfo/libre-silicon-devel