Hi Martin,
On Wed, Feb 16, 2000 at 04:19:41PM -0500, Martin Proulx wrote:
> I simply manually edited the resulting libtool file. This isn't the
> correct thing to do, but this will allow me to correctly build my c++
> shared libs on solaris. I've attached the original, unmodified libtool
> created after appending the CXX tag. In it, I've simply edited line 5337
> to be like line 212.
>
> It seems that the decision on how to set this variable is always taken
> within aclocal's libtool.m4, according to the platform only.
>
> The obvious problem is that the CXX tag's deplibs_check_methods
> (and maybe other configurations) seem to end-up with default values,
> rather than values derived from the C configurations, or derived from
> their language's lt-cf???.sh script.
That shouldn't happen. I never redefine deplibs_check_method. In
fact, it should just use whichever one was found during the libtool C
compiler checks.
> I've checked on a linux box as well, and it gets the same problem, so
> you might be able to reproduce it. Generate a libtool, append a CXX
> tag, and check that for the appended tag, at least deplibs_check_methods
> is set to unknown.
I just tried this on my linux box with the tagdemo. Both of the
deplibs_check_method variables were the same, i.e. pass_all. I'm not
sure why you had different results. Weird. I'll look into it.
> If you want more details, feel free to ask.
Will do. :)
> Now I have a few questionsthat came to mind since I've started using the
> multi-language libtool.
>
> 1-) Why do we have to respecify the able/disable static-shared flags
> when appending a new tag? I wish the new language would simply use C's
> defaults if not specified, rather than using the defaults which are to
> generate both shared and static libs. Is this meant to be, or is this
> related to the above problem I encountered?
I'm not sure if we should inherit default settings from the C
configuration. Does anyone have any thoughts on this?
BTW, are you using the AC_LIBTOOL_CXX macro, or are you appending
manually? It looks like you're appending manually. I bet that's why
the deplibs_check_method wasn't set properly for you. Sorry, I didn't
document AC_LIBTOOL_CXX yet.
> 2-) If libtool will indeed be able to generate different mixed
> static/shared configurations for every language. How will the
> automake/autoconf integration will
> work. Will there be "--enable-LANG-shared" and so on flags to
> autoconf? Will there be AC_ENABLE_LANG_SHARED macros to be used in
> autoconf.in ?
I haven't thought this far ahead. :-)
I just wanted to get multi-language support working, and then tweak
stuff afterwards.
> 3-) Will the AC_PROG_LIBTOOL macro be intelligent enough to discover all
> the languages used in the project, and create automatically a libtool
> that supports all these languages?
Wow, good question. This is again something I didn't think about but
it seems like it might be useful. I won't have to look at
implementing such a feature for a while, however. Does anyone have
any thoughts on this?
-Ossama
--
Ossama Othman <[EMAIL PROTECTED]>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8
