MSBuild Unable to Locate Include Files When Run Through QB #1766

cfarver · 1 decade ago

I'm running into trouble compiling/building a project using MSBuild. I've verified that I can build the project when I run MSBuild via the commandline, but whenever it's run via QuickBuild I get the following error:
fatal error C1083: Cannot open include file: 'includefile.h': No such file or directory [D:\quickbuild-4.0.5\workspace\root\project\project.sln]

I feel I've gone at this issue from every possible angle, but haven't been able to solve it. My only conclusion at this point is that since it runs fine via the commandline, that QuickBuild must not have access to some environment variables that the commandline does? Has anyone seen this and found a way around the issue?

I've tried using the environment variables in the Step properties as well as using an NAnt build file and using setenv, but nothing seems to work..

Any ideas?

replies 10
views 3876
stars 0

robinshen ADMIN · 1 decade ago

Please run the build in debug logging mode (configuration general setting->build log level), and QB will print the command to call MSBuild together with the working directory information in build log, then please run that command from command line within the same working directory to see if it makes any difference.

cfarver · 1 decade ago

Thanks for the reply.

I've run both MSBuild and my NAnt build file (which calls MSBuild) in QuickBuild with debug on. I then took those exact commands that I saw listed and copied them over to the command line, and ran them in the same working directory that was listed. I'm still running into the same issues with not being able to find the include files. I actually saw MSBuild link up to the missing files with no issues on the command line.

Is there anything else I can do to fix this?

steveluo ADMIN · 1 decade ago

Hi,

It seems you are running QuickBuild 4.0.5, right? In previous version, QuickBuild has a bug on computing working directory and project file, I'm not sure if it is the problem. So please upgrade to the latest QuickBuild first, then in project file field for MSBuild step, specify a relative path to the configuration workspace directory, and also leave working directory blank (we will remove it soon as it makes no sense, QuickBuild will always use projectFile's parent directory as working directory).

Hope this can help you resolve the problem.

steveluo ADMIN · 1 decade ago

By the way, in the first post, you said you can run msbuild to compile your program, but in your next post, you said, you can't run those commands taken from QuickBuild debug log, is there any difference between them?

cfarver · 1 decade ago

Ah sorry my second post was a little confusing.

What I meant is that I compared the two working directories/commands and lined them up, but still no issues via the command line.

I'm upgrading QuickBuild now, and will try your tips to see if I get a change.

cfarver · 1 decade ago

I'm getting the same issue for both MSBuild and NAnt after upgrading to the latest version and removing the working directory setting in the Step <img src="{SMILIES_PATH}/icon_sad.gif" alt=":(" title="Sad" />

robinshen ADMIN · 1 decade ago

If command line builds get through with exactly the same command and working directory as in QB, I guess the most probable reason is different environments between the user running the command line and the user running QB process. Please stop QB on the machine, and start it directly from the same command line by running this:
<QB install dir>/bin/server console
Then run the build again in QB again to see if it can succeed.

If still no luck, please create a simple test case demonstrating the problem and send us relevant files (MSBuild project file as well as QB backup) and we will test to see what might be the problem.

cfarver · 1 decade ago

Just ran my build after starting QB as you requested, and it worked. So it does seem to be an environment issue between the command line and QB running as a service?

It's a relief that the build now works, but is there a way to fix this environment issue so I don't have to run QB through the console?

#10

robinshen ADMIN · 1 decade ago

You may compare environments in two modes to see if there are any difference: to print environments from within QB, run a command build step executing this command:
cmd /c set

#11

cfarver · 1 decade ago

Thanks for the tip. I did notice a few changes between the two environments, and then checked the service and saw it wasn't running under my account. Changed that and now it seems to be working without running it with the console flag.

Thanks for all the help!