Re: [AL] differences between...

[Matthew S. <ma...@th...>]

VC usually keeps 2 parallel projects called Release and Debug and
 you select which one you build via a box on the menu bar.

In the project--> settings are seperate lists of lib files for the two
builds
you should put alld.lib on the debug one and alleg.lib on the release one.
allp.lib is a special version for profiling (working out where your program
spends it's time) which I haven't used but I think you use it in the Debug
build.

the static librarys are for when you compile for use *WITHOUT* the DLLs


----- Original Message -----
From: Karthik <ma...@vs...>
To: <al...@ca...>
Sent: Tuesday, October 31, 2000 1:31 PM
Subject: Re: [AL] differences between...


> alleg.lib is the optimized Allegro library which you should use when you
are
> compiling for a release
> alld.lib will add extra debug info into your programs - useful to find out
> where your program crashed or simply to debug it ( names of functions are
> seen). Useful while developing a program
> allp.lib is used when you want to profile your program - i.e. measure the
> speeds of various function calls
>
> I haven't used alld.lib and allp.lib under Windows , but I guess it holds
> good for Vc 6 ..
> btw, if you want to use the *.dll , you must link with the static library
> (s_alleg.lib - I'm not sure of the exact filename) and not alleg.lib
> hth,
> Karthik
> ----- Original Message -----
> From: "Frédéric Drouillon" <fd...@fr...>
> To: <al...@ca...>
> Sent: Tuesday, October 31, 2000 6:12 PM
> Subject: [AL] differences between...
>
>
> >
> > hello,
> > what are the different use between alld.lib alleg.lib allp.lib (allegro
> 3932
> > compiled) ?
> > I use alleg.lib because "all3932.dll" is smaller.
> >  i work with VC 6 so may be i could use the others for good reasons.
> >
> > Could somebody explain me what are the differences between them under
VC6
> ?
> >
> > Thank
> > frédéric
> >
> >
>
>