Michael Russell wrote:
> Hi all,
>
> Sorry for the repost, but I never received any response when I first
> asked this a few weeks ago. I would really appreciate some feedback
> on this, it's driving me nuts...
>
> I'm beginning the process of moving some projects from VS.Net 7 to
> VS2005. I'm having problems getting a Custom Build Step to work.
>
> In the dialog for the header file I want to perform the custom step
> on, I copy and paste the command line:
> $(QTDIR)\bin\moc.exe "..\Messenger.h" -o ".\moc_Messenger.cpp"
>
> I also set description, outputs, additional dependencies
> ($(QTDIR)\bin\moc.exe), and click Ok. I can open the dialog up again,
> and see all the options as I set them.
>
> However, when I do a build, it fails, with moc.exe complaining of
> invalid arguments. When I check the Command Line entry in the Custom
> Build Step properties again, it now contains:
> $(QTDIR)\bin\moc.exe -DQT_NO_DEBUG -D_WINDOWS -DUNICODE -DWIN32
> -DQT_DLL -DQT_THREAD_SUPPORT -I"$(QTDIR)\include" -I"."
> -I"d:\Qt\3.3.2\mkspecs\win32-msvc.net" "..\Messenger.h" -o
> ".\moc_Messenger.cpp".
>
> I can remove the '-DQT_NO_DEBUG -D_WINDOWS -DUNICODE -DWIN32 -DQT_DLL
> -DQT_THREAD_SUPPORT -I"$(QTDIR)\include" -I"."
> -I"d:\Qt\3.3.2\mkspecs\win32-msvc.net', compile, get the error, repeat
> ad naseum.
>
> Is there some option somewhere in VS2005 that is causing it to add the
> defines and includes to the command line for a CBS? I never
> experienced this in VS 7.