Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MPC, Visual Studio, Debug and Release builds

8 views
Skip to first unread message

Andrew

unread,
Nov 11, 2009, 7:10:14 AM11/11/09
to
I would like debug and release DLLs to go into separate directories
and be able to pick up the right ones when I build an app that links
with those DLLs (actually, their associated .libs). I don't know how
to make MPC do this. So, for the time being, my mpc files set lib_path
values wrt the Debug directory. Yuck. Can someone give me some help
please? I am using MPC version 3.7.0 on Windoze XP with Visual Studio
2005 (i.e. vc8).

Regards,

Andrew Marlow

Andrew

unread,
Nov 13, 2009, 9:36:51 AM11/13/09
to

Just to make it clear what the problem is. The release libs get the
name I expect but the debug libs get 'd' added just before the suffix.
They all get put in the same dir. This is not what I expect or want. I
expected the leafnames to be the same for release and debug but for
them to be put into Debug and Release dirs. Now to build in debug I
have to put a 'd' onto the end of all my libs names in my 'mpc' file.
This seems wrong to me. Maybe I am doing something wrong.

Andrew

unread,
Dec 31, 2009, 2:58:38 AM12/31/09
to

Just to clarify the problem: I am ok with 'd' being added for my own
libs. I simply say libs += whatever and MPC takes care of whether or
not to add the 'd'. The problem is with third party libs. Some of them
have 'd' when in debug, and others dont. I would like to be able to
say in my mpc file that the 'd' one is for when I am building in debug
mode.

-Andrew M

0 new messages