Hi,
Am 23.11.2009 um 18:56 schrieb Philip Brown:
On Mon, Nov 23, 2009 at 4:41 AM, Maciej (Matchek) Blizinski
<[email protected]> wrote:
I'm working on a library package with the *.so files in
/opt/csw/lib/foo. The package will have 64-bit support, so the
shared
objects will be:
/opt/csw/lib/foo/*.so
/opt/csw/lib/foo/sparcv9/*.so
/opt/csw/lib/foo/amd64/*.so
I've noticed that CSWcommon provides a symlink: /opt/csw/lib/64. It
points to amd64 or sparcv9 depending on the host architecture. This
link is needed to provide a architecture independent -L flag for
64-bit builds: /opt/csw/lib/foo/64.
I guess that something along the lines of ln -s sparcv9
/opt/csw/lib/foo/64, or amd64, depending on the architecture. What's
the right GAR idiom for it? Should it be a post-merge target?
Eh, that's just a convention. If the library (or packages USING the
library) work as-is, there's no need for you to be making those
symlinks.
If you need to include the library in any other package it is
mandatory to have these links as linking is GAR goes per default
against the /64 directory.
Best regards
-- Dago
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
