I wish people would trim their reply to lists I keep getting duplicates
from a lot of people. Uhhh.
On Mon, 31 Jan 2000, Arnd Hanses wrote:
> On Sun, 30 Jan 2000 23:06:39 -0800, Karl Nelson wrote:
>
> >One last suggestion is to rename sigc++config.h sigc++/config.h
> >in all the headers so tha
On Sun, 30 Jan 2000 23:06:39 -0800, Karl Nelson wrote:
>One last suggestion is to rename sigc++config.h sigc++/config.h
>in all the headers so that you don't need to include sigc++
>in your include paths. (and of course make the corresponding
>rename in the configure.in.)
Hi,
once again I'
> Karl,
> the sigc++ acconfig.in patch needed to get things to compile correctly on NT,
> did that go into CVS?
> Allan could you please include that?
Yep, the change is in. Since Allan is building from a CVS, it
should be in when he builds it with the most recent makeLyx script.
--Karl
Karl,
the sigc++ acconfig.in patch needed to get things to compile correctly on NT,
did that go into CVS?
Allan could you please include that?
Background: libsigc++-0.8.6 does not compile out of the box on cygnus-b20
because there are little issues with the configuration. Karl send me a patch
th
>
> Compile speed and saving a few extra bytes in the distribution. It is
> also a heavy handed way of forcing everyone to think carefully about why
> they want more than 2 parameters.
I have ways of vastly reducing the number of templates involved
but they are much to space hungry (involve cha
On Sun, 30 Jan 2000, Karl Nelson wrote:
> Okay, I will poke at it a bit. You really don't want to
> generate the *.h files in the src_dir though as it can mess some
> things up. Not a problem, I will just add $(builddir) to the include
> path as well to fix that.
You're right. I was in a hurr
> >
> > You likely need to add a "-I $(top_srcdir)/sigc++/macros" or something
> > to that effect in the Makefile.am.
>
> That will make m4 find the template.macros.m4 however the bigger problem
> is that the generated headers are put into:
> obj-libsigc++/sigc++/
> instead of
> lib
Okay, I will poke at it a bit. You really don't want to
generate the *.h files in the src_dir though as it can mess some
things up. Not a problem, I will just add $(builddir) to the include
path as well to fix that.
BTW, just curious why you are truncating the signal system numbers down?
Those
On Sun, 30 Jan 2000, Karl Nelson wrote:
> >
> > An extremely annoying thing about libsigc++ is that is doesn't support
> > VPATH compiles. So it has broken those for LyX unless you use an external
> > library.
>
> Not sure what a VPATH compile is. Care to clue me in?
> (I know autoconf well,
>
> An extremely annoying thing about libsigc++ is that is doesn't support
> VPATH compiles. So it has broken those for LyX unless you use an external
> library.
Not sure what a VPATH compile is. Care to clue me in?
(I know autoconf well, automake poorly, and rpm/deb not at all.)
> So if you
An extremely annoying thing about libsigc++ is that is doesn't support
VPATH compiles. So it has broken those for LyX unless you use an external
library.
So if you try this and it fails don't blame me blame Karl. Then get a cvs
copy of libsigc++ and fix it for Karl (and us). We could probably
11 matches
Mail list logo
