Markus Gothe wrote:
I think we are using the wrong approach here Rob. Do we really want to
*LINK* against boost when building from source. All the the code is in
the headers afaik. I think we should look at other projects using boost
on this issue, which needs further investigation.
I'm
Markus Gothe wrote:
Looking at pkgsrc, they have splitted the boost-pkg so you can choose
just to install the headers (which is actually what I did on IRIX alas
compilation fails due to TU-smart pointers)...
If you don't link in the boost_thread library, you get undefines from
using the
strk wrote:
On Fri, Oct 06, 2006 at 09:38:50AM +0200, Hannes Mayr wrote:
Another point might be to only check for libraries/headers which are
really used and to make the checks dependend from the choosen renderer
and gui (why check for X11,SDL,GTK2,KDE/QT if the user has choosen AGG
as
...
You can do this by configuring with --disable-shared. Right now the
plugin has zero dependencies on any other Gnash libraries, and the
plugin *must* be dynamically linked anyway so the browser can load it.
Why not just use the shared libraries ? For Gnash, it probably doesn't
matter
Markus Gothe wrote:
Ahh, yes --disable-shared is good. Then we can see unused linkage etc by
the binary. Only makes sense for that kind of tasks (and speeding up
You can also run ldd on the executable (in */.libs) to see what it
actually uses. The main advantage to using static libraries is
Hi,
does Gnash contain / is it planned that Gnash will detect the screen
region (upper-left and lower-right coordinates) where characters did
change visible?
Currently Gnash seems to redraw each frame from ground up even if just
a small portion of the screen did change and even if there was no
On Fri, Oct 06, 2006 at 09:37:48AM -0600, Rob Savoye wrote:
I'm still curious why we'd want to do this. If it's a debugging
problem, I use libtool --mode=execute gdb gnash, which sets up your
debugging environment correctly to find all the right libs.
I just see this as a management thing,
strk wrote:
I just see this as a management thing, if we don't intend to maintain
a public API or a versioning scheme for binary compatibility let's just
NOT install the 'helper' libraries...
Not that anybody seems to notice the libraries, but I can agree to
this idea. I don't think we want
8 matches
Mail list logo
