At 8:55 PM -0700 5/23/04, Steve Fink wrote:
On May-15, Jeff Clites wrote:
When linking against (using) a static library version of ICU, we need
a C++-aware linker (because ICU contains C++ code); with a
dynamic-library version of ICU presumably we wouldn't.
I don't know if this applies here,
On May-15, Jeff Clites wrote:
When linking against (using) a static library version of ICU, we need
a C++-aware linker (because ICU contains C++ code); with a
dynamic-library version of ICU presumably we wouldn't.
I don't know if this applies here, but there is a good reason to use a
On Fri, 14 May 2004, Ron Blaschke wrote:
IMHO, we are currently talking C only, so that shouldn't be a problem. I
hope anybody tells me if I'm wrong.
Still, I am curious. Why would the linker need to know about C or C++?
I thought ICU contained some C++ files. As to why we care, you might
On May 14, 2004, at 3:30 PM, Ron Blaschke wrote:
Friday, May 14, 2004, 11:48:00 PM, Andy Dougherty wrote:
IMHO, we are currently talking C only, so that shouldn't be a
problem. I
hope anybody tells me if I'm wrong.
Still, I am curious. Why would the linker need to know about C or
C++?
I
Saturday, May 15, 2004, 6:02:57 PM, Jeff Clites wrote:
Of course, to build ICU the flags would be necessary, but we're not
building it directly - we are asking it to build itself, and then we
just link to the resulting library, which shouldn't need anything
special. Am I getting things wrong
Dan Sugalski wrote:
At 5:23 PM -0700 5/13/04, Jeff Clites wrote:
[Most commentary snipped, as it's dead-on]
- When building / using a shared parrot the compiler macro
PARROT_LIB_DYNAMIC will be defined, for static PARROT_LIB_STATIC
What will these be used for? Traditionally, there aren't
On Wed, 12 May 2004, Ron Blaschke wrote:
I have finally sorted out the details of the flags stuff, which I will
present below. Any comments are highly appreciated. Be warned: I am going
to implements this if there are no objections. ;-)
You might want to review the patch I submitted about a
On Thu, 13 May 2004 10:00:53 -0400 (EDT), Andrew Dougherty wrote:
You might want to review the patch I submitted about a year and a half ago
-- it's # 18319, and it included some (but certainly not all) of your good
ideas.
Thanks, I'll do that.
I gather parrot's now trying to include stuff
On Thu, 13 May 2004 17:23:18 -0700, Jeff Clites wrote:
xxx_STATIC_BUILDcflags and ldflags to build static parrot
We should make it clear that we are talking about building a static lib
(to distinguish from what the next macro is intended for)--so how
about:
xxx_STATIC_LIB_BUILD or
On Fri, 14 May 2004 09:11:32 +0200, Bernhard Schmalhofer wrote:
I have little expertise in building libraries on many platforms. But
aren't these issues all addressed by GNU's 'libtool'. Is there a
licensing reason for not using that?
autoconf, automake and libtool address the issues we are
Friday, May 14, 2004, 11:48:00 PM, Andy Dougherty wrote:
IMHO, we are currently talking C only, so that shouldn't be a problem. I
hope anybody tells me if I'm wrong.
Still, I am curious. Why would the linker need to know about C or C++?
I thought ICU contained some C++ files. As to why we
On May 12, 2004, at 1:26 PM, Ron Blaschke wrote:
I have finally sorted out the details of the flags stuff, which I will
present below. Any comments are highly appreciated. Be warned: I am
going
to implements this if there are no objections. ;-)
- Targets shared and static are provided, to
Jeff Clites wrote:
Alternatively, we could just parse embed.h -- all and only symbols
defined there should be exported. (I believe that's the plan.)
Nope. Any symbol in a file included from embed.h and outside of an #if
defined(PARROT_IN_CORE) is fair game for embedders. See interpreter.h
for
On Thu, 13 May 2004, Jeff Clites wrote:
- When building / using a shared parrot the compiler macro
PARROT_LIB_DYNAMIC will be defined, for static PARROT_LIB_STATIC
What will these be used for? Traditionally, there aren't compile-time
difference when building a static v. dynamic library, I
At 5:47 PM -0700 5/13/04, Brent 'Dax' Royal-Gordon wrote:
Jeff Clites wrote:
Alternatively, we could just parse embed.h -- all and only symbols
defined there should be exported. (I believe that's the plan.)
Nope. Any symbol in a file included from embed.h and outside of an
#if
At 5:23 PM -0700 5/13/04, Jeff Clites wrote:
[Most commentary snipped, as it's dead-on]
- When building / using a shared parrot the compiler macro
PARROT_LIB_DYNAMIC will be defined, for static PARROT_LIB_STATIC
What will these be used for? Traditionally, there aren't
compile-time difference when
I have finally sorted out the details of the flags stuff, which I will
present below. Any comments are highly appreciated. Be warned: I am going
to implements this if there are no objections. ;-)
- Targets shared and static are provided, to build a shared or static
parrot library.
- The
17 matches
Mail list logo
