You are not logged in.
Could anyone comment on adding OpenROAD-flow into openroad-git ?
Offline
I have no idea what either of these things are.
What precisely does "add it to the package" mean, how would this be done, and what is wrong with the package as it is today?
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
See the sources links inside openroad-git
this AUR package seems to forget to include one particular extra package which is OpenROAD-flow. What I mean by extra is that without including this extra package will not introduce compilation or installation error, but it is for extra features.
This OpenROAD package is for ASIC synthesis and place-and-route tool purpose.
It seems to me that only installation method option 1 is feasible for PKGBUILD, because the other two installation methods involves dockerfile.
Please correct me if wrong.
Offline
What precisely does "add it to the package" mean,
What I mean by extra is that without including this extra package will not introduce compilation or installation error, but it is for extra features.
This... doesn't really answer my question.
Does it link in new object code? Does it install support files? Does it install something which makes use of openroad?
how would this be done
I have no idea if you tried to answer this, or how. So, moving on.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Setup
The flow has the following dependencies:
OpenROAD
KLayout
TritonRoute
YosysThe dependencies can either be obtained from a pre-compiled build export or built manually. See the KLayout website for installation instructions.
KLayout, Tritonroute, Yosys are NOT required for openroad itself .
https://github.com/The-OpenROAD-Project shows upstream uses separate repos for openroad and openroad-flow .
Both also have their own isue tracker.
IF packaging openroad-flow satisifies the aur submission guidelines, it should get its own package.
Last edited by Lone_Wolf (2020-06-17 10:34:34)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I have the following draft PKGBUILD for openroad-flow
However, how do I deal with this source environment script ?
# Maintainer: promach
pkgname=openroad-flow-git
pkgrel=1
pkgver=r9415.868b6b1b
pkgdesc='A framework for RTL-to-GDSII'
arch=('x86_64' 'i686')
url='https://github.com/The-OpenROAD-Project/OpenROAD-flow'
license=('BSD-3')
provides=("openroad-flow")
#conflicts=()
depends=('yosys' 'klayout' 'openroad' 'TritonRoute')
#optdepends=()
makedepends=('git')
source=('git+https://github.com/The-OpenROAD-Project/OpenROAD-flow.git')
sha512sums=('SKIP')
build(){
cd ${srcdir}/OpenROAD-flow
make PREFIX="/usr"
}
pkgver() {
cd "$srcdir/${pkgname%-git}"
printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
}
package() {
cd ${srcdir}/OpenROAD-flow
make PREFIX="/usr" PYTHON_PREFIX="$pkgdir/usr" DESTDIR="$pkgdir" install
}
Last edited by promach (2020-06-17 23:54:41)
Offline
So basically this just exports the environment variable $OPENROAD during the build process, pointing to the directory with the openroad installation? I guess you could export this as /usr/lib/whatever to have it detect wherever the packaged version of openroad-git is.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
you could export this as /usr/lib/whatever to have it detect wherever the packaged version of openroad-git is.
May I know what is the exact command syntax to do this exact thing ?
Should it be inside build() or package() ?
Offline
I don't know, wherever you would otherwise use this setup_env.sh thing...
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
modroot="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )/tools"
What is the above line of code doing ?
Do I need to modify this particular above line inside PKGBUILD ?
Besides, there is also this following line of code which I think needs to change as well ?
path_string=${modroot}/build/OpenROAD/src:${modroot}/build/TritonRoute:${modroot}/build/yosys/bin
the reason is that OpenROAD , TritonRoute and yosys already had their own PKGBUILDs
Besides, how to handle this cmake build script for OpenROAD-flow ?
Could anyone advise ?
Last edited by promach (2020-06-21 09:09:27)
Offline