Hi Hagen,
I headed that OpenSuse has such a compile farm, as otherwise *nobody* would build packages for suse.
Lets make Slackware tgz packages :-)
Cheers
Ludwig
On Sunday, February 3, 2019, Hagen SANKOWSKI <hsank@posteo.de> wrote:
> Hello Ludwig.
>
> At least David is a OpenSuse Tumbleweed user.
> And he already showed me the possibility to build/compile Debian
> Packages on OpenSuse Server farm.
>
> So, if your machine is probably to week, OpenSuse's build service is an
> option.
>
> Regards,
> Hagen.
>
> On 2/3/19 9:48 AM, ludwig jaffe wrote:
>>
>>
>> ---------- Forwarded message ----------
>> From: ludwig jaffe <ludwig.jaffe@gmail.com <mailto:ludwig.jaffe@gmail.com>>
>> Date: Saturday, February 2, 2019
>> Subject: Tools for VLSI Design - LibreSilicon flavored Live-DVD
>> To: Staf Verhaegen <staf@fibraservi.eu <mailto:staf@fibraservi.eu>>
>>
>>
>> Debian based is enough imho.
>> Also openSuSE is not so much used for development.
>> Fedora and especially centos/rhel has a much smaller package wealth
>> compared to debian
>> or ubuntu which is based on debian.
>> People with rpm distros could try to use the alien tool. But I will
>> support debian and ubuntu as these are preffered by me.
>>
>> Cheers
>>
>> Ludwig
>>
>> On Saturday, February 2, 2019, Staf Verhaegen <staf@fibraservi.eu
>> <mailto:staf@fibraservi.eu>> wrote:
>>> ludwig jaffe schreef op za 02-02-2019 om 18:40 [+0100]:
>>>
>>> Toolchain:
>>> Hi I could maintain a repository to be added to /etc/apt/sources.list
>>> /etc/apt/sources.list.d/libresilicon
>>>
>>> Alternatively maybe repos can be maintained for a few selected OSes on
>> openSUSE build Service. I do think for example some academic
>> environments are still based on Centos or derivatives like Scientific Linux.
>>> greets,
>>> Staf.
>>>
>>> so apt will find the packages
>>> this should work for debian and ubuntu and one could try to statically
>> link the tools if they need old stuff like motif or even older stuff
>> that could create dependency problems as every distro is a bit different.
>>> But the first step is to maintain a dynamically linked version of the
>> tools for debian stable and ubuntu lts.
>>> This should be not too much work.
>>> No need fir a life cd.
>>> Just a howto for adding our repo to the distribution.
>>>
>>> Regarding electric: how to host a 600M tarball of html code docunentation.
>>> Github accepts only 100M blobs. So splitting up the docu part of
>> electric did not help much.
>>> If you want to code with electric git clone levush/electric
>>> read the readme on compiling and have gixygen and graphviz installed
>> to make the docu.
>>> There is still a path problem in the Doxyfile as relative paths
>> sonehow are not working correctly.
>>> If someone knows better please look at the different Versions of
>> Doxyfile in the project and improve it.
>>> The code base is quite huge so one would need to surf the code to
>> understand it. Doxygen is a cool tool for analysis of code written by
>> others.
>>>
>>> If we want to develop with electric we need to find what should be
>> improved and try to understand the code to the extend needed fir this task.
>>> Otherwhise electric sits there beeing rescued from beeing depublished
>> in favor of the shity java version but thats it.
>>>
>>>
>>> Cheers
>>>
>>> Ludwig
>>>
>>>
>>>
>>>
>>> On Saturday, February 2, 2019, Hagen SANKOWSKI <hsank@po
>>>
>>> steo.de <http://steo.de>> wrote:
>>>> Hello Ludwig, Hello List.
>>>>
>>>> Thanks Ludwig for your Effort to compile some tools!
>>>>
>>>> I came across the fact, that the Debian family of Distributions has
>>>> already compiled packages for qflow, which also includes yosys and
>> magic..
>>>>
>>>> IMHO we should have a working tool flow, which allows us to work on our
>>>> project and others to follow us.
>>>>
>>>> Ludwig, do you like to setup and maintain a (Debian/Mint clone) Live-DVD
>>>> with all tools already installed tools?
>>>>
>>>> I would vote (at least) for
>>>> - qflow
>>>> - yosys
>>>> - magic
>>>> - klayout
>>>> - electric
>>>> - (lua)latex (while with easier UTF-8 usage!)
>>>>
>>>> all in the latest and greatest version. Plus all stuff we are developing
>>>> here, like
>>>> - lsc
>>>> - popcorn
>>>> - melmac
>>>> - ... etc.
>>>>
>>>> Additional (in later versions) I can think about distributing nice
>>>> documentations not only about the process, but also how-to, cookery
>>>> books of how to make chips.
>>>
>>>
>>
>> --
>> Send from mobile phone with autocorrection / autofill. Blame my phone
>> for typos.
>>
>>
>>
>>
>> --
>> Send from mobile phone with autocorrection / autofill. Blame my phone
>> for typos.
>>
>>
>> _______________________________________________
>> Libre-silicon-devel mailing list
>> Libre-silicon-devel@list.libresilicon.com
>> http://list.libresilicon.com/mailman/listinfo/libre-silicon-devel
>>
> _______________________________________________
> Libre-silicon-devel mailing list
> Libre-silicon-devel@list.libresilicon.com
> http://list.libresilicon.com/mailman/listinfo/libre-silicon-devel
>
--
Send from mobile phone with autocorrection / autofill. Blame my phone for typos.