miabuild suppress warnings during compile

Got a problem you cannot solve? Try here.
Post Reply
gduke
Posts: 9
Joined: Mon Feb 23, 2009 5:22 pm

miabuild suppress warnings during compile

Post by gduke »

I am running miabuild from the command line and get multiple warnings:

"No Files Matching wildcard pattern"

I could care less that I have no matches and want to suppress these warning so I can have MSBUILD script run miabuild and not be prompted.

Any suggestions on how to suppress these messages?


Thanks,
George
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

These actually indicate an error condition and will break your builds in future iterations of the plug-in. If you don't care, define compiler variables that exclude these file bags and set those variables at build time.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
gduke
Posts: 9
Joined: Mon Feb 23, 2009 5:22 pm

Post by gduke »

I am new to Installaware obviously. I am basically taking an existing project created by someone else and using it. We have moved our source control from VSS to TFS and our build is now creating a slightly different deploy directory I have made all of the necessary changes, I believe. I am not copying debugging symbols to the deploy directory therefore I do not need to ignore them as the script is doing. I removed the exclude statement however I am still getting these warnings/errors and I do not know where they are coming from. If I click ok the build continues and runs just fine. I tried to debug but it says I need to make a debug build of my project before running it in the IDE.

Please point me in the right direction. Thanks
bokkie
Posts: 767
Joined: Sun Feb 08, 2009 6:30 am

Post by bokkie »

gduke wrote:If I click ok the build continues and runs just fine. I tried to debug but it says I need to make a debug build of my project before running it in the IDE.

Please point me in the right direction. Thanks
I've had this as well. I generally find building using CD or DVD first and then building my Single File prevents this error occurring. I'm not sure if this is the only solution but it seems to fix it for me. As for the other questions, I'm not sure.
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
gduke
Posts: 9
Joined: Mon Feb 23, 2009 5:22 pm

Post by gduke »

I guess the compiler variables are causing the problem for me debugging.
I found this thread:

http://www.installaware.com/forum/viewt ... p?=&p=4887
bokkie
Posts: 767
Joined: Sun Feb 08, 2009 6:30 am

Post by bokkie »

gduke wrote:I guess the compiler variables are causing the problem for me debugging.
I found this thread:

http://www.installaware.com/forum/viewt ... p?=&p=4887
I'd be interested to know more. I've had compiler variables in use when I've debugged before because I was testing those concepts in IA.

This thread http://www.installaware.com/forums/viewtopic.php?t=4327 shows what I had in my code and the message boxes worked as expected when I debugged. Have I misunderstood your question about them?
Peter. Smartly dressed, he still resembles an unmade bed.
InstallAware MVP
gduke
Posts: 9
Joined: Mon Feb 23, 2009 5:22 pm

Post by gduke »

I removed the compiler variables but I still get the error about debugging. Ahhh! Frustration. Help
gduke
Posts: 9
Joined: Mon Feb 23, 2009 5:22 pm

Post by gduke »

I need to locate where these wildcard pattern mismatches are. can anyone help me do this? I don't see anywhere in the script where they would be missing.
Post Reply