Allan Rae <[EMAIL PROTECTED]> writes:
| (Will code LyX for food and a few square metres of floor to sleep on)
That can be arranged.
| > | So, even if you don't want this applied to the repository any potential
| > | gui-indep people are likely to need it. Roland are you still keen?
| >
| > I am not going to apply this patch to old lyx cvs module, but it is
| > nice to know that it is so easy to make the switch (basically add a
| > return type to the signal declaration.)
|
| Okay, I'll make it available from my website instead then.
|
| > I think we will check in configure if there is a libsigc++ installed
| > and if so use that otherwise we will use the one that we provide with
| > LyX. (much in the same way as we do with gettext now)
| > It is a pity that libsigc++ distribution is so large...
|
| Have you or Karl come up with a cutdown version yet? I haven't seen
| anything in the libsigc++ repository to indicate anythings been done in
| that regard yet.
I thought I should begin looking on that when I try to include it in
the lyx dist. A cursory glance shows that there is not a lot that can
be removed.
| I guess all we need are the generated signal/slot code
| and can hopefully skip all the Handles and so on. That should reduce
| things a little. Have you looked into this yet or shall I -- since I
| could then argue that I wasn't working on LyX but libsigc++ ;-)
mmm... not sure... My guess is that we should have to full lib and not
just a part of it.
Sure go ahead. The first goal is to include it in the lyx dist so that
the lyx-build goes ok. and we can use the resulting lib. I think
libtool should be used for that...it seems that it already does... I
think all we have to do is to make sure that the configure gets called
with approp options. (--disable-shared)
Lgb
