cuneiform team mailing list archive

["dma_k@xxxxxxx" <652883@xxxxxxxxxxxxxxxxxx>]

JussiP, thank you for comments.

1) Having one .a per library (e.g. per .so) is also fine.
2) I don't think the compiler will issue any errors, unless these globals are referred from the code (and they can't to to well-defined public API).

Would would be nice to see is a make rule, that recompiles all objects
without -fPIC/-shared and puts all .o files into one "cuneiform.a" file
with "ar". When the target program will be linked, compiler will take
only those object files from .a, which are actually referred (I used
this as a reference: http://stackoverflow.com/questions/1804606/static-
initialization-and-destruction-of-a-static-librarys-globals-not-
happening).

You don't need to refactor the code. If I am wrong, please, correct me.

-- 
Generate all-in-one .a archive for static linking
https://bugs.launchpad.net/bugs/652883
You received this bug notification because you are a member of Cuneiform
Linux, which is the registrant for Cuneiform for Linux.

Status in Linux port of Cuneiform: Won't Fix

Bug description:
Dear Cuneiform Developers,

It would be nice to have .a library for static linking against Cuneiform.

Relevant request in Debian bugtracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598616