Ticket #3 (closed defect: fixed)

Bug contains 18 commit(s) | SVN Diffs for #3

 

Opened 9 years ago

Last modified 2 years ago

Static libraries?

Reported by: batsatt(at)adforce.com Assigned to: yves
Priority: Milestone:
Component: unknown Version: 1.2.5
Keywords: closed Cc:
Load: Xref:
Java Version: Operating System: solaris
Project (C/J): Weeks: 0
Review: srl

Description

In our application, we require static libraries, and the ICU builds shared ones. I have hacked the mh-solaris file and successfully built the common library as needed. One or more of the higher-level libs does not link when built statically.

If possible, please add an option to the configure script to build static libraries.

Thanks!

Attachments

Change History

12/31/69 16:00:25 changed by notes

assign to: yves fixed: yes reviewer: srl target: 2000q3

12/31/69 16:00:26 changed by auditor

  • Wed Sep 29 11:59:34 1999 hshih moved from incoming to config_build
  • Wed Sep 29 12:02:12 1999 sbooth changed notes
  • Thu Feb 17 15:10:51 2000 schererm sent reply 1
  • Thu Feb 17 15:11:08 2000 schererm changed notes
  • Wed Jun 14 13:42:37 2000 srl changed notes
  • Wed Jun 14 13:43:44 2000 srl changed notes
  • Wed Jun 14 13:43:44 2000 srl moved from config_build to feature
  • Fri Oct 20 01:16:32 2000 yves changed notes
  • Fri Oct 20 01:16:32 2000 yves moved from feature to config_build
  • Fri Oct 20 03:10:49 2000 yves sent reply 2
  • Mon Dec 4 21:36:30 2000 schererm changed notes
  • 01/04/02 16:32:08 yves changed notes
  • 01/04/02 16:32:41 yves changed notes
  • 01/04/02 16:33:00 yves changed notes
  • 03/27/02 13:48:31 srl changed notes
  • 04/02/02 15:18:32 srl changed notes
  • 04/02/02 15:18:32 srl moved from config_build to fixed
  • 04/05/02 15:21:49 schererm moved from fixed to closed

02/17/00 14:10:51 changed by Markus Scherer <icu-bugs(at)www10.software.ibm.com>

It isn't possible to build two static libraries with interdependencies. We could build one static lib, though.

10/20/00 03:10:49 changed by Yves Arrouye <icu-bugs(at)oss.software.ibm.com>

Bryan,

If you are still interested... The latest unstable version of ICU will build as static libraries on Solaris with no problem. After getting the sources from CVS, simply configure with --disable-shared --enable-static and you will only get static libraries (except for libicudata.so which is loaded separately; see the help for --with-data-packaging if you do not want a shared library here).

YA

PS: if Bryan or anybody else on the list knows how to avoid always having to link with the C++ compiler (or explictely with -lstdc++ for example) when using

libicuuc.a, in order to satisfy the external references to ostream, I'd love to hear about that.

10/20/00 10:11:20 changed by Bryan Atsatt <batsatt(at)adforce.com>

This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible.

Content-Type: text/plain;

charset="iso-8859-1"

Thanks, Yves.

When we roll forward to the next release, this will be very helpful!

// Bryan

From: Yves Arrouye icu-bugs@oss.software.ibm.com Sent: Friday, October 20, 2000 12:11 AM To: batsatt@adforce.com Cc: icu@oss.software.ibm.com Subject: Re: Static libraries? (PR#3)

Bryan,

If you are still interested... The latest unstable version of ICU will build as static libraries on Solaris with no problem. After getting the sources from CVS, simply configure with --disable-shared --enable-static and you will only get

static libraries (except for libicudata.so which is loaded separately; see the help for --with-data-packaging if you do not want a shared library here).

YA

PS: if Bryan or anybody else on the list knows how to avoid always having to

link with the C++ compiler (or explictely with -lstdc++ for example) when using

libicuuc.a, in order to satisfy the external references to ostream, I'd love to hear about that.

Content-Type: text/html;

charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35"> <TITLE>RE: Static libraries? (PR#3)</TITLE> </HEAD> <BODY>

<P><FONT SIZE=2>Thanks, Yves.</FONT> </P>

<P><FONT SIZE=2>When we roll forward to the next release, this will be very helpful!</FONT> </P>

<P><FONT SIZE=2>// Bryan</FONT> </P>

<P><FONT SIZE=2>-----Original Message-----</FONT> <BR><FONT SIZE=2>From: Yves Arrouye [<A HREF="mailto:icu-bugs@oss.software.ibm.com">mailto:icu-bugs@oss.software.ibm.com</A>]</FONT> <BR><FONT SIZE=2>Sent: Friday, October 20, 2000 12:11 AM</FONT> <BR><FONT SIZE=2>To: batsatt@adforce.com</FONT> <BR><FONT SIZE=2>Cc: icu@oss.software.ibm.com</FONT> <BR><FONT SIZE=2>Subject: Re: Static libraries? (PR#3)</FONT> </P> <BR>

<P><FONT SIZE=2>Bryan,</FONT> </P>

<P><FONT SIZE=2>If you are still interested... The latest unstable version of ICU will build as</FONT> <BR><FONT SIZE=2>static </FONT> <BR><FONT SIZE=2>libraries on Solaris with no problem. After getting the sources from CVS, </FONT> <BR><FONT SIZE=2>simply configure with --disable-shared --enable-static and you will only get </FONT> <BR><FONT SIZE=2>static libraries (except for libicudata.so which is loaded separately; see the </FONT> <BR><FONT SIZE=2>help for --with-data-packaging if you do not want a shared library here).</FONT> </P>

<P><FONT SIZE=2>YA</FONT> </P>

<P><FONT SIZE=2>PS: if Bryan or anybody else on the list knows how to avoid always having to </FONT> <BR><FONT SIZE=2>link with the C++ compiler (or explictely with -lstdc++ for example) when using</FONT> </P>

<P><FONT SIZE=2>libicuuc.a, in order to satisfy the external references to ostream, I'd love to</FONT> <BR><FONT SIZE=2>hear </FONT> <BR><FONT SIZE=2>about that.</FONT> </P> <BR>

</BODY> </HTML>

01/09/07 15:07:04 changed by

  • milestone deleted.

Milestone 2000q3 deleted

Add/Change #3 (Static libraries?)




Anti spam check: