Close Topic Options

Hi akyprian,

Thanks for clarifying the window message thing - doh!

I'm still left with the above problem, maybe I need to explain it better. I'm already checking which build is selected and then setting it to debug before building. Everything is working fine except when an /out parameter is specified as below:

- Project name is "Hello", no built files exist yet
- Release is selected and release /out string contains "test.exe"
- Debug /out string is empty
- My addin sets build type to debug, and builds "Hello.exe" as expected
- My addin sets build type back to release and returns 0 for IDM_MAKE_DEBUG
- MiniDBG reports "The system cannot find the file specified." as it is looking for "test.exe", the file specified for a release build.

Obviously I need MiniDBG to be looking at the debug build settings.

If a release build exists then MiniDBG will start ok but will use the release build that has no debug info.

Doesn't it make sense that MiniDBG should always retrieve the debug build settings??

Thanks, Jamie.

Hi,

It DOES make sense! At 5, you set build to release. It is obvious that at 6 MiniDBG will look for relase build arguments. What if you interchange steps 5 & 6?

Yes and No! One might want to debug the release build as it might behave a little bit differently!

Regards,

Antonis

I can't see all values.

Attached Image

This is what happens when one tries to save some space! I 'll fix it. What is your display resolution?

Thanks,
Antonis

That would work great but can you explain how it can be done as we've already established the WAE_COMMANDFINISHED message won't be sent for IDM_MAKE_DEBUG - hence my original question.

Would it be possible for MiniDBG to send a custom message when it has finished?

Edit: Realising this is a problem even when using OllyDbg etc. I've altered my code to swap steps 5 and 6 using WAE_COMMANDFINISHED and it works great. I just need a message or something from MiniDBG now...

I knew you were going to say that!

Edit: As the behaviour is the same when CTRL+F9 is used without MiniDBG it would probably cause problems for some users to change it now anyway.

Btw, I'm also the developer of a popular program which has it's own forum so I know what it can be like! I'm only asking for help because I've hit a dead end which I've been unable to work around and don't want my addin to cause confusion for any user that has a different output path for the debug/release build.

Cheers, Jamie