-
Notifications
You must be signed in to change notification settings - Fork 719
Description
Hello,
I am missing a libabc-dev like package which will contain libabc.so, libabc-pic.a, headers, pkg-config, cmake find file.
So I have written a config for cpack which builds such a package.
Is it desired to have such configs in this repo (and I should send pull request) or is the distribution handled differently (perhaps you are using dh_make or similar)?
Why it is necessary to have main things defined in Makefile, from my point of view it only complicates things?
=================================================================
cmake.zip
The zip in attachments contains:
- build_debs.sh contains commands to build the deb package
- abc_cpack.cmake extract variables required for cpack and pkg-config
The build works https://app.circleci.com/pipelines/github/Nic30/hwtHls/709/workflows/382d466e-cd08-484b-a307-4299a287ed42/jobs/629
In my project, if I build library as meson subproject everything works, but if I use this generated deb instead I am geting:
berkeley-abc/src/base/abc/abcAig.c:1134: Abc_AigUpdateLevelR_int: Assertion `Abc_ObjIsNode(pNode)' failed.
I am not certain if the bug is in linking or in my lib, but certainly something is broken.
It would help me if we can remove make part so there are less places for bugs to hide in.
I need deb package to have cachable dependency for CI to reduce compilation time of my lib to fit in limits of free plan.
It would be best if it was directly repo of linux distribution, but for start lets have at least local deb build.