Re: [AD] library dependencies...

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


I had the same output as Thomas until I compiled allegro with the
following flags:
./configure --enable-xwin-dga=no --enable-xwin-dga2=no
--enable-xwin-vidmode-no

On a side note, but maybe relevant, where does makefile.in come from? My
understanding of the build process was you needed configure.in and
makefile.am. aclocal will generate some m4 macros, autoconf will
generate configure, automake will generate makefile.in, and configure
will generate all the makefiles. It would be much simpler to change the
linking of X extensions by editing Makefile.am instead of makefile.in(
btw, many unix people refer to makefile's with a capital M ). 

Basically Im wondering where did makefile.in come from and can we switch
to makefile.am?

On Sun, 4 Jan 2004 12:35:15 +0100
Grzegorz Adam Hankiewicz <gradha@xxxxxxxxxx> wrote:

> On 2004-01-04, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > Ok, I have a quite recent CVS version of allegro installed... (fyi)
> > 
> > And I was under the impression that the dynamic loading of "drivers"
> > fixed apps getting linked to libraries like libXxf86dga.so.1 and
> > ibXxf86vm.so.1...
> > 
> > yet heres a ldd of an allegro app:
> > 
> > moose@xxxxxxxxxx strangegame $ ldd sg
> >         liballeg.so.4.1 => /usr/local/lib/liballeg.so.4.1
> >         (0x4002b000) libc.so.6 => /lib/libc.so.6 (0x400f3000)
> >         libm.so.6 => /lib/libm.so.6 (0x4021c000)
> >         libpthread.so.0 => /lib/libpthread.so.0 (0x4023e000)
> >         libXxf86dga.so.1 => /usr/X11R6/lib/libXxf86dga.so.1
> >         (0x4028e000) libXxf86vm.so.1 =>
> >         /usr/X11R6/lib/libXxf86vm.so.1 (0x40294000) libXext.so.6 =>
> >         /usr/X11R6/lib/libXext.so.6 (0x4029b000) libX11.so.6 =>
> >         /usr/X11R6/lib/libX11.so.6 (0x402ab000) libdl.so.2 =>
> >         /lib/libdl.so.2 (0x4038b000)/lib/ld-linux.so.2 =>
> >         /lib/ld-linux.so.2 (0x40000000)
> > 
> > I assumed the driver .so files are linked to the X and other libs...
> 
> My linker options seem different.
> 
> $ ldd examples/exhello
>         liballeg.so.4.1 => /usr/local/lib/liballeg.so.4.1 (0x40023000)
>         libm.so.6 => /lib/libm.so.6 (0x400ef000)
>         libc.so.6 => /lib/libc.so.6 (0x40112000)
>         libpthread.so.0 => /lib/libpthread.so.0 (0x40244000)
>         libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40295000)
>         libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x402a3000)
>         libdl.so.2 => /lib/libdl.so.2 (0x4036a000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> $ make info
>  Some drivers will be built as dynamic modules.
>  Enabled modules: dga2 svgalib fbcon vbeaf vga ossmidi ossdigi
>  Disabled modules: sgialdigi artsdigi esddigi alsamidi alsadigi
>  Generated code: multithreaded, little endian, i386 asm, MMX, SSE
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for
> IBM's Free Linux Tutorials.  Learn everything from the bash shell to
> sys admin. Click now!
> http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> -- 
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
> 




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/