[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Location of libtcc1.a referred to in application deb
Re: [Tinycc-devel] Location of libtcc1.a referred to in application deb file
Wed, 11 Oct 2017 22:55:04 +0100
KMail/5.2.3 (Linux/4.13.0-1-amd64; KDE/5.37.0; x86_64; ; )
On mercredi 6 septembre 2017 13:25:41 BST Rajesh Jayaprakash wrote:
> Dear TinyCC developers,
Sorry for the late reply.
> Apologies if this query doesn't belong here.
> I use tcc for compiling the C code generated at runtime in my application (
> github.com/shikantaza/pLisp). I build the application by linking to the tcc
> static library, and package it into a deb file using dpkg-deb. tcc is
> mentioned as a dependency for the deb.
If you want to make a deb file, why not have a Debian source package and make
it build depend on libtcc-dev as well? If that is too much hassle, you should
at least link against the libtcc.a file provided by libtcc-dev (see below).
> When some users install the application and attempt to run it, they get the
> error "tcc: error: file '/usr/local/lib/tcc/libtcc1.a' not found". This
> file is actually found in /usr/lib/x86_64-linux-gnu/tcc in their machine.
Doing the above should fix the issue as the libtcc.a in libtcc-dev will expect
libtcc1.a in the same path as the path for libtcc1.a in the tcc package.
> Am I missing something in building the deb package (i.e., is the location
> reference to libtcc1.a incorrectly hardwired into my application, since
> /usr/local/lib is the location of the tcc library in the machine where the
> dpgk-deb command was run)?
I'd rather say it's incorrectly hardwired in the libtcc you built.
Alternatively the deb you provide could include the libtcc1.a in the path it
expects it to be but the solution above is much better.
Description: This is a digitally signed message part.
- Re: [Tinycc-devel] Location of libtcc1.a referred to in application deb file,
Thomas Preud'homme <=